vwiki

User Tools

Site Tools

Trace: • iot • old_projects • active_directory • continuous_integration • art • ai
ai

Artificial Intelligence

  • We Don't Need Designers Anymore by Philipp Lackner
    • This video explores using AI to generate editable mobile app designs in Figma by reversing traditional workflows. Witness how AI-driven development compares to human-created assets for a multi-milestone app project.

Using AI For Android Development

  • I Use Gemini Every Day as an Android Developer -Here Are My Favorite Tips and Tricks by Akshay Nandwana
    • 1. Agent Mode handles a lot of my first draft
      • Instead of asking Gemini for one function, copying it into my project, fixing the imports, creating another file, and repeating the process, I can give Agent Mode a larger task.
        • For example: Create a settings screen using Jetpack Compose with three sections: account, notifications, and appearance. Use a ViewModel for the state and add previews for the screen.
    • 2. I ask Gemini about errors before leaving Android Studio
      • For build and sync errors, Gemini can help diagnose what went wrong. For runtime errors, you can use Ask Gemini directly from Logcat to get an explanation and possible next steps.
    • 3. Prompt Library means I don’t keep writing the same prompts
      • You can save prompts you use frequently and recall them directly from the IDE. Prompts can exist at the IDE level or project level, and templates can even reference selected code or files.
      • One particularly useful detail is project-level prompts. They’re stored with the project, which means a team can maintain useful AI prompts alongside the codebase.
    • 4. Parallel Agent conversations are surprisingly useful
      • Android Studio supports running multiple Agent Mode conversations in parallel.
    • 5. I occasionally check the metrics to see whether AI is actually helping
      • …
    • 6. Starting a project with AI removes the least interesting part
      • …
    • 7. Gems are useful when I want the same Gemini “developer” again
      • Gems are customized versions of Gemini that you can configure for recurring tasks or areas of expertise. Think of it as saving more than a prompt.
      • For example, you could create an Android Code Reviewer Gem and tell it:
        • prefer Kotlin
        • follow modern Android architecture guidance
        • prefer Jetpack Compose
        • check state hoisting
        • look for lifecycle problems
        • flag unnecessary recompositions
        • check accessibility
        • explain recommendations before rewriting code
    • 8. Gemini Notebook has become my second brain for technical research
      • …
    • 9. Journeys with Gemini changes how I think about UI testing
      • Journeys with Gemini lets you describe an end-to-end test using natural language. Gemini then converts those steps into actions it performs against your app. Instead of beginning with test implementation details, you can describe the user journey.
        • For example:
          • Launch the app.
          • Tap “Sign in.”
          • Enter a valid email and password.
          • Tap Continue.
          • Verify that the Home screen appears.
          • Open Settings.
          • Verify that the signed-in user’s email is displayed.
    • One more thing: use /plan before large changes
      • For example the prompt looks like:
        • /plan Migrate this screen from LiveData + XML to StateFlow + Jetpack Compose. Preserve the existing ViewModel behavior and don’t change the repository API.
    • The bigger shift
      • My Android workflow is increasingly becoming:
        • Idea → Agent Mode
        • Large change → Planning Mode
        • Repeated instruction → Prompt Library / Rules
        • Error → Gemini inside Build or Logcat
        • Research → Gemini Notebook
        • Specialized recurring task → Gem
        • User flow testing → Journeys
ai.txt · Last modified: by kalaschnikow