For the past 3 months, I've been building a structured AI workflow for Flutter development.
Goal: Make AI write code you can trust.
No more vibe coding and hoping for the best. Launching next week — learn more here 👇
agentictoolkit.dev
If you haven’t tried OpenCode yet, do yourself a favor and take it for a ride!
My favorite combo:
- OpenCode + gpt-5.3 on ChatGPT Plus plan ($20/month)
My February newsletter is out, covering:
- Flutter 3.41
- GPT 5.3 Codex
- 16 Claudes building a C compiler
- The OpenClaw Security Crisis
and much more.
Read it here:
codewithandrea.com/newsletter/f...
Every year I publish a retro about my journey as an educator/content creator.
In 2025, things didn't go too well. But hey ho, learning to adapt is part of the job as an entrepreneur. 🤷♂️
Here are all the details 👇
codewithandrea.com/meta/my-2025...
My last Flutter & AI newsletter of the year is out!
📱 Flutter GenUI SDK
⚡️ Build Runner Speedups
🗓️ 2025 LLM Year in Review
📖 MCP Becomes an Open Standard
🔒 Running AI Agents safely inside a DevContainer
You can read it here:
codewithandrea.com/newsletter/d...
After a few headaches, I'm now able to run both Claude Code and Flutter within a sandboxed dev container.
This is great for both safety 🛡️ and speed 🚀
Here's a detailed guide with my complete setup (source code included) 👇
codewithandrea.com/articles/run...
My Flutter & AI newsletter is out! 📮
🐦 Flutter 3.38 & Dart 3.10
🖥️ Google's Antigravity IDE
🔥 Gemini 3 Pro, Opus 4.5, GPT 5.1
⚠️ Agentic Coding Security Risks
🤮 AI Coding Sucks (interesting take by Syntax .fm)
Read it here 👇
codewithandrea.com/newsletter/n...
Spent the whole day dockerizing my coding setup so I can safely run `claude --dangerously-skip-permissions` and mitigate damage if things go wrong.
Many gotchas along the way. I'll try to share an article once I get it working properly.
The more I use AI for coding, the more I realize how powerful it is.
But I still feel like a beginner and I now see a long road to real mastery.
My new plan:
- I'll dive deeper and aim to get really good at this
- Once I'm ready, I'll start sharing new content
Kinda wanted to have a play with Antigravity today, but...
Just managed to one-shot a video transcription CLI tool (3000+ LOC including tests).
How I did it:
- Written a detailed spec (with some help from AI)
- Used my own custom /plan and /work sub-agents
Claude code did all the work -> AI Agents are getting better!
Quick demo 👇
So much cool stuff happening in AI right now, especially for us developers!
Just tested Antigravity with Gemini 3 Pro. 💻
Very nice... but I still miss a few things from Claude Code.
Will publish a video next week!
It uses fl_chart
Preview of the charts screen on my currency converter app
Been doing some tweaks and polish on my currency converter app.
I built >90% of it with agentic AI and I'm improving my workflows as I go along.
Check it out here:
currency-converter-ab.web.app
Code it yourself, or prompt the AI? 🧐
That's a very valid question, since AI doesn't always get it right.
In my latest video, I offer insights from my experience, along with a decision matrix that will help you save time and avoid frustration.
Watch it here 👇
youtu.be/HOhYX9lA6T8
Effort to code vs Effort to Prompt: my 2x2 matrix 1. Low prompt, Low code - Small UI/animation tweaks - Pull to refresh - Codegen - Simple refactors 2. High prompt, Low code - Line-level instructions - Dense business logic - One-line bug fixes - Layout errors (overflows, unbounded heights, etc) 3. Low prompt, High code - Boilerplate (crash reporting, analytics setup) - Writing tests - Localization - Theming system - Big refactors (AI usually does this in multiple steps + run analyzer ... can be slow) 4. High prompt, High code - Offline caching + syncing - Full-stack features - Background tasks + iOS/Android specific - Complex charting solutions - IAP + entitlements For 1 and 2, use Autocomplete and IDE assists. For 3 and 4, use AI agents for planning, implement in stages, consider verification effort.
When coding with AI, I follow a fairly simple principle:
If prompting effort > coding effort, code it. 😅
Would it be useful if I made a video with examples, etc?
Really sorry for only answering now. Life's been busy these last few months, and I haven't had much free bandwidth.
When are you running your livestreams? If I can fit it in my schedule, I'll let you know.
My Flutter October newsletter is out, covering:
🧩 Flutter & Figma MCP
🧱 Wasm 3.0 release
🎥 FlutterCon EU 2025 Videos
🎧 Andrej Karpathy — AGI is still a decade away
Read on for all the details:
codewithandrea.com/newsletter/o...
Back in the day, many companies used to under-promise and over-deliver, leading to customer satisfaction and long-term business prospects.
Sad to see late-stage capitalism changed this. Now it seems to be the norm (esp. for AI companies) to trick customers and do the opposite.
The PR description includes the complete status, implementation details, testing checklist, and next steps. Ready for review! ⏵⏵ accept edits on (shift+tab to cycle) Context left until auto-compact: 0%
Here's a fun game! 🎲
Fully implement a feature, getting as close as possible to 0% context before auto-compacting.
Just published a new video about my 3 top folders for agentic AI coding in Flutter! 🚀
Inside, I cover:
⏳ Updated workflow for more consistent AI results
✅ Guidelines to ensure AI stays on track
🧭 Battle-tested patterns, commands and prompts
Watch it here 👇
youtu.be/D68mZzbs6JY
Top 3 Folders for Agentic AI coding in Flutter ai_??? ai_specs ai_docs
I'm working on a new video about essential folders I use for agentic AI coding.
I'll cover my workflow for:
1️⃣ staying organized
2️⃣ getting consistently good results
3️⃣ reducing friction when coding with AI
Should be out next week! 🗓️
Still there. But I get consistently better results with the right guardrails in place.
think-plan-build-verify-deliver
This is kinda how I build with AI these days.
Same for you?
The app still needs some tweaks, but you can try the updated web version here:
currency-converter-ab.web.app
Today I built the currency conversion charts for my new app.
Or rather, I wrote the spec, and CC Sonnet 4.5 did all the planning and implementation. 🚀
Got it all done in ~4 hours, even though I wasn't at all familiar with the fl_charts library. Very impressed!
My Flutter September newsletter is out!
- Riverpod 3.0
- The ultimate guide to migrating to Flutter
- Liquid Glass UI
- AI rules for Flutter and Dart
- Latest from the Flutter community
- Best AI Coding Agents
Read on for all the details 👇
codewithandrea.com/newsletter/s...
If you copy-paste Dart files to a new project, your imports will fail: import 'package:old_app/src/constants/layout_breakpoints.dart'; You can Find & Replace package:old_app with package:new_app to fix them (annoying and not very scalable) Alternatives Relative imports: import '../../constants/layout_breakpoints.dart'; Absolute imports: import '/src/constants/layout_breakpoints.dart'; Absolute imports are handy for files that always live in the same location across multiple projects (e.g. /src/constants) Consider this as a temporary solution. Reusable files should be moved into a common package (works best with monorepo setups).
Did you know?
You can use absolute imports for reusable Dart files that are copy-pasted across projects.
This way, they are always imported correctly (as long as they live in the same location relative to the project root).
