The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Spent the last ~4 years building production Flutter apps - POS systems, B2B tools, consumer products. One pattern I keep seeing: teams ship an MVP fast, then hit a wall 6-12 months in because state management, offline handling, and API error cases were designed for demo day, not real usage.
If your Flutter app is starting to feel fragile under real traffic, happy to talk through what's usually worth fixing first.
This is painfully accurate. The real cost of a fast MVP often shows up later in offline flows, state edge cases, and error handling—not in the first release.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
Three years ago, we built a service provider booking app (plumbers, carpenters, electricians) from scratch, fully custom code. Took close to 4 months to get live.
Today, with AI tools like Claude and ChatGPT in the workflow, I think a comparable MVP could realistically ship in 4-6 weeks. The boilerplate and repetitive work compress fast, matching logic and payment edge cases still need real engineering judgment.
If you had to rebuild something similar today, what timeline would you expect?
Agreed. The other thing AI does not shorten is the feedback loop with real providers and payment processors, onboarding a live Stripe Connect account, waiting on payout tests, chasing a plumber to finish a test booking. That calendar time is fixed no matter how fast the code ships.
Building one app for Android + iOS — A or B?
A — Flutter
B — Native Android + iOS
If the product needs high performance, smooth animations, native capabilities and long-term scalability, which approach would you choose?
Vote A/B.
The signal is usually in the first spec. Count the features that touch the OS versus the ones that touch the network. Past three or four OS-level features, the cross-platform-with-a-few-channels plan has quietly become two native apps with a Dart layer on top, and the maintenance cost follows.
Doing a bit of portfolio housekeeping this month, so a few older projects are going up.
Youfiliate came to us with a name and PRD, and nothing else. No logo, no identity, no interface. Their product catches broken affiliate links before creators lose income from them. We did the branding and the whole product design.
It grew a lot since then, so we went back and brought the designs up to date. Smart links, analytics, dark mode, full mobile.
Another one built almost entirely through messages and Figma comments.
We did a second project with the same client too, already delivered, sharing that one soon.
Check it out 👇
