Switched from FlutterFlowThe first screens feel fast on a visual builder. Then the edge cases show up, and the weekend disappears into widgets and action flows. These teams hit that wall, moved to Newly, and told us what changed.
Testimonials
Previously on FlutterFlow
“There are just some things I couldn’t get FlutterFlow to do very well — even after spending around 100 hours building with it.”
After switching
I’m probably less than 10 hours into Newly and already farther along than I was on FlutterFlow. App store stuff and RevenueCat are all set up.
Michael — Newly Discord
Previously on FlutterFlow
“Two weekends lost to wiring up action flows for a simple streak screen.”
After switching
Rebuilt the app in Newly in an afternoon and shipped a first TestFlight build the same week.
Sarah — indie founder, habits app
Previously on FlutterFlow
“Every internal request turned into hours of widget configuration before anyone could test it.”
After switching
New feature requests now turn around in under a day. The team prompts, reviews, and ships.
James — ops lead, field ops tool
Previously on FlutterFlow
“Stuck in a Dart escape hatch we didn’t want to maintain long-term.”
After switching
Clean React Native codebase that the engineering team was willing to pick up post-launch.
Priya — PM, marketplace MVP
Previously on FlutterFlow
“Spent more time fighting calendar widgets and action flows than building the actual booking experience.”
After switching
Described the booking and reminder logic once in Newly and had a working flow live the same evening.
Micah — bootstrapper, booking app
Before / after
Time to first TestFlight build
Before
2–4 weeks of canvas work
After
Same week, from a prompt
Shipping a new screen
Before
Widget setup + action flow wiring
After
Describe it, review the diff
Onboarding a teammate
Before
Learning the builder and logic model
After
Write a prompt, read the code
Store submission
Before
Manual review prep, repeated rejections
After
Compliance checks built into the flow
Case studies
Solo founder
Before
Built a prototype in FlutterFlow that took two weekends and still felt fragile to iterate on.
After
Rebuilt the same idea in Newly in an afternoon; iterated on tone and UX over the next week.
Ops lead at a services company
Before
Every new internal request turned into widget work before anyone could use it.
After
Team now prompts changes and reviews a working build the same day.
What changed
Avg. time to working build
Down from weeks on FlutterFlow, across the switchers we talked to.
Self-reported clarity
Teams reported it was easier to reason about the app once logic lived in code.
Store submission rework
Compliance-aware checks caught review-blockers earlier in the process.
Self-reported across switchers interviewed. We’ll add more precise numbers as teams share them with permission.