Consulting
Native App Development — iOS, Android & Flutter
Twelve years of shipping native mobile apps to the App Store and Google Play. I build in Swift and SwiftUI on iOS, Kotlin and Java on Android, and Flutter when a single codebase is the right call — with the architecture, offline handling and performance work that keeps an app healthy long after launch.
What you get
- iOS apps in Swift and SwiftUI, built to current platform standards.
- Android apps in Kotlin and Java, or Flutter when one codebase makes sense.
- Architecture that holds up: clean layers, offline support and predictable state.
- Performance work — smooth scrolling, fast startup, sensible memory use.
- App Store and Play releases handled, including review submissions and rejections.
How it works
- Shape it Agree scope, platforms and architecture before writing feature code.
- Build Implement in focused iterations with working builds you can try.
- Harden Offline, edge cases, performance and accessibility passes.
- Release Ship to the App Store and Play, and handle the review back-and-forth.
A good fit if
- You need a real native app, not a wrapped website.
- You want one engineer who can take iOS and Android from architecture to store.
- You've been burned by an app that shipped fast and aged badly.
FAQ
iOS, Android, or both?
Either or both. Native per platform when it matters, Flutter when a shared codebase saves time without hurting the experience — we decide together.
Can you take over an existing app?
Yes. I'll usually run a short audit first so I understand the codebase before changing it — see the auditing service.
Do you handle store submissions?
Yes — build, signing, submission and the review process, including handling rejections when they come.
Contact
Discuss Native app development
Tell me what you're building. Remote-first from Barcelona — we start with a short intro call.