Build it once. We’ll look after every screen it lands on.
Mobile, web, and desktop apps from one Flutter codebase, so a feature ships to every platform on the same day instead of drifting apart between two teams.
A 30-minute conversation about your product.
-
iOS Release 3
-
Android Release 3
-
Web Release 3
-
Desktop Release 3
Build it. Run it. Grow it.
Three stages of an app’s life, one team for all of them. Every topic links to work you can read on this site.
-
Build
The foundation every release stands on, set up so the app stays easy to change.
50% lower cost than native for MarketWatch’s game on iOS and Android, from one codebase Dow Jones -
Operate
The app your customers open every day, kept fast, stable and up to date after launch.
2x users year over year on Berkheimer’s E-File app, which we still look after H.A. Berkheimer -
Grow
The features that make the app earn, from the first purchase to the tenth visit.
2x revenue year over year, after six apps became one with RevenueCat behind every subscription V1 Sports- In-app purchases
- Subscriptions
- Personalization
- Loyalty programs
- Localization
- Experimentation
- Analytics
Some teams start with one of these before the build.
We stay with you from the first workshop to the next release.
You see a working slice of the app before full production code, so the expensive decisions are made on evidence.
-
Workshops with your stakeholders to set goals, map existing systems, and agree what success looks like.
-
A working slice of the app in front of real users before the full build, so assumptions get tested early.
-
iOS, Android, web, and more at once, wired into auth, payments, analytics, and your APIs.
-
Store and web deployment, performance monitoring, and support through rollout.
-
Usage data drives the next release, whether that means new platforms, users, or features.
Hamilton. Betterment. Scooter’s.
The first commercial Flutter app outside Google
- app installs
- 3.5M+
- peak monthly active users
- 500K+
- lottery entries
- 100M+
Betterment: two native codebases into one
- Betterment accounts
- 775K+
- in assets, March 2023
- $32B
- Flutter developers trained
- 20+
Two native apps into one, with zero downtime
- native apps into one codebase
- 2
- downtime
- 0
- feature parity
- 100%
Before you hand over the repo.
Short answers from apps in production. Anything else, bring it to the first call.
01 Can you build native apps instead of Flutter?
Yes. We build cross-platform in Flutter or native for iOS, Android, and web. Choose Flutter when you want one codebase, so a feature ships to every platform on the same day.
02 Can you take over an app another team built?
Yes. We build from scratch or from what you inherited. The work can open with a code assessment, so your team knows what to fix before anything changes.
03 Will users notice when we move to Flutter?
Not on Scooter’s. Its two revenue-critical native apps moved into one Flutter codebase with no downtime and full feature parity.
04 Who looks after the app after launch if we have no mobile team?
We can. Berkheimer has no in-house mobile team, so VGV monitors its E-File app, applies updates, fixes bugs, and adds features as its requirements grow.
05 Where does the code live while you build?
In your repo, from the first commit. You own the code and the IP, and the work stays maintainable after we leave.
06 What happens on the first call?
It is 30 minutes with Laura or Greg. Bring the app or the idea, and the repo if you can share it. Afterwards you get a written summary of what we would do first, and How we work shows how the first weeks run.
We’ll care about your success as much as you do.
Our unicorns read every message and reply, usually the same day.
Start the conversationA 30-minute call about what you’re building.