mobile · flutter, ios, android, riverpod, offline-first
Flutter developer for iOS and Android apps, from the first screen to the stores.
I built a reservation app in Flutter on my own, in five months, from the first screen to the App Store and Google Play. More than 100 restaurants use it today. I can build your app the same way, or join your Flutter team.
- Platforms
- iOS and Android, phone and tablet
- Around it
- Riverpod, WebSockets, Fastlane
- In production
- 100+ restaurants, 6 languages
- Engagement
- As a project or in your team
- Working hours
- Mon–Fri 04:00–18:00 Buenos Aires 09:00–23:00 Berlin 03:00–17:00 New York
- Available from
- Q4 '26
What I build with Flutter
- Apps for iOS and Android from one codebase, with their own layouts for phones and tablets.
- Apps that work offline: a local cache and a queue for changes, so a bad connection doesn’t lose anything.
- Live data: changes pushed over WebSockets, so every device shows the same state.
- Releases through a pipeline: signed builds to TestFlight and Google Play with Fastlane, and automated tests on every pull request.
A reservation app for more than 100 restaurants
A restaurant-tech provider needed an app for the staff who run service. I built it on my own: a floor plan where reservations are dragged onto real tables, a timeline of the evening and a kanban board. Changes reach every other device over WebSockets. When the Wi-Fi fails, changes are queued and sent once the connection is back, and every change carries an ID, so no booking is created twice. About 1,200 automated tests run on every pull request, and the app speaks six languages. Read the case study.
Your existing backend is fine
The reservation app didn’t need a new backend: it works with the Node.js backend the provider already ran. If you don’t have one yet, I build it with NestJS and Postgres.
Many apps from one codebase
When every client needs an app in its own branding, building each one by hand doesn’t scale. For the same provider I built a white-label app generator, in Ionic, that turns a configuration into signed apps in both stores in about two hours instead of several weeks.
How we can work together
- App development: a written scope with timeline and price, a demo every week, 4 to 12 weeks for a typical MVP.
- Staff augmentation: I join your Flutter team, part-time or full-time, from three months.
- Advisory: a review of your app’s architecture, or help with a Flutter codebase that has become hard to change.
Questions
Why Flutter instead of two native apps?
One codebase for iOS and Android means one set of features, one set of tests and releases that reach both platforms at the same time. For most business apps that's faster and cheaper than building everything twice.
How long does a Flutter app take?
A typical MVP takes 4 to 12 weeks. The reservation app, with three views of the evening, offline mode and six languages, took five months from the first screen to both stores.
Do you take care of the App Store and Google Play releases?
Yes. Builds are signed and uploaded to TestFlight and Google Play by a Fastlane pipeline, not by hand.
Who owns the code?
You do. All rights transfer to you, and after the handover you get the code, the documentation and 30 days of support.