[DevFest Singapore] Getting Started with Mobile Development Using Generative AI
This is the slide, "Getting Started with Mobile Development Using Generative AI" at DevFest Singapore 2025. It's an 80-Minute Hands-On Session.
#DevFest #DevFestSG25 #DevFestSingapore2025
#GoogleForDevelopers #GDGSingapore
Generative AI ɾSimplifying debugging through conversation AI × Mobile — The New Era Begins ɾDevice and OS fragmentation ɾComplex app release workflows 🤖 AI Innovations 📱 Mobile Evolution
•Develop through dialogue, not automation •Explore how AI thinks and helps •Learn more compared to Agent-based AI •Quick to start — no setup needed $IBUCBTFE"* 💡*OUIJTXPSLTIPQ XF`MMVTF(FNJOJBTBDPOWFSTBUJPOBMDPEJOHQBSUOFS 💡*OUIF fi OBMQBSU *`MMBMTPDPWFSUIFUPQJDPGl"HFOUCBTFE"*z
ɾGenerate UI and logic automatically Learn by building from code generation to testing ɾFix build errors with AI help ɾWrite and simulate widget tests 💻 Code Generation 💻 Debugging & Testing
Browser: Cloud •DartPad •IDE: Local •Android Studio •Visual Studio Code •IntelliJ IDEA Regular Approach (for experienced devs) Flutter Development Environment
Use It: •Generate UI and code snippets •Debug and refactor through conversation •Create tests and documentation collaboratively Generative AI Environment
Evolved from waiting for prompts to acting on context •From isolated commands to continuous collaboration •From single- fi le focus to project-wide understanding •From reactive suggestions to proactive improvements
Check — context-aware, tool-using, outcome-driven Key Characteristics Context Awareness Multi ‑ step Reasoning Direct Execution Persistent State Understands codebase, dependencies, and developer intent. Plans tasks and executes across fi les/functions. Edits code, runs tests/builds, generates draft PRs. Keeps memory and artifacts across sessions.
agent in a Flutter repo. Goal: A screen scrolls slowly. Diagnose → improve → verify → open a draft PR. Proceed without approval. Guardrails: - Keep business logic & public APIs unchanged. - Limit edits to the affected screen (e.g., MyHomePage) and minimal helpers. - Keep the diff small and self-explanatory. Plan: - List 3 hypotheses for the slowdown. - Add lightweight measurements ( fi rst-frame builds, per-screen scroll rebuilds) using debug-only logs. - Start measuring immediately. Diagnose: - Run measurements ( fl utter run/test/analyze). - Output key numbers on one line and choose up to 2 approaches with a brief rationale. Act: - Apply a minimal design that reduces fi rst-frame builds and scroll rebuilds while preserving visuals/API. - Show the diff and apply it. Check: - Run analyze/test; report green/red. - Show Before → After numbers on one line each. Draft PR: - Branch: perf/scroll-optimization - Commits: perf(ui)… ; chore(debug) remove counters - Create a draft PR with problem, root cause (numbers), changes, diff size, key metrics, and checks. Start now. If anything fails, propose a fallback and continue. Plan → Diagnose → Act → Check → Draft PR
→ execute → con fi rm” remains human-driven: answers, not completion. Releases queue behind human availability. Give a goal → Agent plans → implements → tests → measures → creates a draft PR in an automated loop. Humans focus on approval. 💬 Chat-based AI 🧑💻 Human Work ⚙ CI ✅ Human Review 📝 Draft PR ✅ Approval Gate Plan Act Test Measure Loop