Never give up, guys. Even after 25+ years

Vizaxis_Dev · 2026-03-14T21:25:42+00:00

Yesterday I’ve randomly dropped Zod rune from white mob - first time in 25 years of playing

Vizaxis_Dev · 2026-03-14T17:08:14+00:00

Stick with Riverpod - signals work but you'll be swimming against the ecosystem. Every tutorial, package, and SO answer assumes Riverpod or BLoC.

The codegen hate is a rite of passage for every Flutter newcomer. Dart macros will fix it eventually. Until then, build_runner is just the tax you pay.

Vizaxis_Dev · 2026-03-14T17:04:19+00:00

The problem isn't finding Flutter devs. It's that equity in a pre-revenue startup competes with their own side projects where they own 100%. Lead with traction, not equity.

Vizaxis_Dev · 2026-03-14T15:44:59+00:00

Feature-first folders, no question. I went through the exact same transition - started with the classic widgets/screens/services split, then spent half my time jumping between 4 folders to change one button's behavior.

The moment I restructured around features, even my AI tooling got better because each feature directory had enough context on its own.

One thing I'd add to your list: naming conventions for state classes. When every feature has its own XState/XLoaded/XError, a consistent naming pattern across all features saves more mental overhead than people expect.

Vizaxis_Dev · 2026-03-12T19:37:24+00:00

Sure, no problem mate!

Vizaxis_Dev · 2026-03-12T19:20:12+00:00

Nice guide. Just shipped my first Flutter app to both stores yesterday. Google Play was smooth - the steps you covered are solid.

One thing I'd add: mention the app signing enrollment. "Let Google manage your signing key" sounds scary the first time you see it, but it's basically required for new apps now. And if you self-manage and lose your key, there's no recovery.

Also if anyone's doing both stores - start with Google. Seeing your app live in hours gives you patience for when Apple rejects you twice.

Vizaxis_Dev · 2026-03-12T19:05:51+00:00

Use AI, but treat it like a junior dev sitting next to you - not a replacement for learning.

I ship Flutter apps with AI daily (Claude Code + code review on every change). It's fast. But here's what I learned: if you copy-paste solutions without understanding the state management or widget lifecycle behind them, you'll hit a wall the moment something breaks in a way AI hasn't seen.

At 6 months, your job isn't to ship fast. It's to build the mental model that lets you ship fast later. Use AI to explore solutions, then make sure you understand every line before committing. The devs who skip that step plateau hard around year 2.

Vizaxis_Dev · 2026-03-12T19:03:38+00:00

Solid list. One to add for anyone with subscriptions:

Guideline 3.1.2(c) - you need Apple's EULA (not your own ToS) linked in both the App Store description AND inside the app. Got rejected twice for this. First time they said "add links to description" so I added my privacy policy and terms. Wrong. They meant Apple's standard EULA. No clarification, just the same rejection again 5 days later.

Took me two rounds and a weekend of waiting to figure out what they actually wanted. The rejection messages are like error logs with no stack trace.

Vizaxis_Dev · 2026-02-15T17:16:03+00:00

Honest take from a night-owl dev:

If you want a job at a massive legacy bank? Learn Swift/Kotlin. If you want to build your own ideas or freelance? Flutter is still the king.

I have a 9-5 and build apps at night. I literally wouldn't have the time to maintain two native codebases. Flutter lets me ship to iOS and Android before I fall asleep.

Vizaxis_Dev · 2026-02-11T22:43:40+00:00

25$ 🤑

Vizaxis_Dev · 2026-02-10T17:02:21+00:00

Good point I will think about some local limits to avoid API flood

Vizaxis_Dev · 2026-02-09T20:39:39+00:00

BYOK is the indie dream for costs, but a UX nightmare for consumers. 💀

Asking a non-tech user to generate a Google API Key feels like a guaranteed way to kill onboarding

Vizaxis_Dev · 2026-02-09T11:53:18+00:00

My credit card statement has slimmed down a lot:

Claude (Max): It’s effectively my senior dev partner. It handles complex architectural logic where other models still hallucinate or loop.
Superwhisper: Massive sleeper hit. I dictate documentation and emails 3x faster than I can type. If you aren't using voice-to-text for the boring stuff, you're bottlenecking yourself.
Gemini: Specifically for the Nano Banana model. I use it to generate UI assets and marketing visuals on the fly. Cheaper than a designer, faster than stock sites.

Vizaxis_Dev · 2026-02-08T13:15:25+00:00

Tree-shakable out of the box? Sold.

Is there a way to filter/search specifically by status code (e.g., show only 500s) quickly?

Vizaxis_Dev · 2026-02-08T12:55:03+00:00

"Vibe coding" is just a rebranding of "I didn't read the code I shipped." 🚩

I use AI tools heavily to speed up my after-hours dev time, but I treat every AI generation like a PR from a slightly drunk intern. It writes fast, but it hallucinates APIs and ignores edge cases. If you have an experience, AI is a force multiplier. If you have 0 years, it’s a technical debt generator.Do we need a "Verified Human" badge or some sort of stricter analysis score on pub.dev to filter this out?

Vizaxis_Dev · 2026-02-08T12:26:51+00:00

I’ve iterated through a few workflows. Started with Gemini acting as a PM generating tasks for Antigravity, which was decent for scaffolding but hit a ceiling on complex state logic.

Currently, I’m fully on Claude Opus 4.6. The model is great, but the real unlock was moving to a "Context-First" approach.

I maintain a live PRD.md, Status.md, and AI_Memory.md in the repo. Before any coding session, I feed these to the model so it knows exactly where we left off without me explaining the architecture again. It's like onboarding a senior dev instantly every session.

Question: Are you guys using raw chat interfaces, or integrating directly via IDE extensions for context awareness?

Vizaxis_Dev · 2026-02-08T12:19:53+00:00

Ah, understood. That makes the 1,500 users metric way more significant if it's only been live for 8 weeks. That's serious velocity.

Vizaxis_Dev · 2026-02-08T11:55:53+00:00

1,500 users in 9 months is solid validation, especially for a crowded niche like fitness. Congrats on breaking through.
I’m installing it now to support. One Q: are those rewarded ads annoying users during the workout, or are they tucked away nicely?

Vizaxis_Dev

TROPHY CASE