Design
Weeks 1 to 2
We agree on scope, architecture and the data model, and prove the risky parts first with a short spike.
- Scope and milestones in writing
- Architecture and data model
- Risky parts proven first
Native Android and iOS apps, built by senior engineers.
We build mobile apps with each platform's own tools: Kotlin and Jetpack Compose for Android, Swift and SwiftUI for iOS. The result feels right in the hand, passes store review and is easy to maintain for years.
What we build
From a single feature to the full app.
More than ten years of shipped mobile apps go into each project. We can build a new app from zero, take over an existing one or add one hard feature to your team's code.
Android apps
Kotlin, Jetpack Compose and coroutines, with a clear architecture and tests. Phones, tablets and foldables.
iOS apps
Swift and SwiftUI, with UIKit where it is the better tool. Built to Apple's Human Interface Guidelines.
Flutter apps
One Dart codebase for both platforms when time and budget matter more than deep platform features.
Voice and VoIP
Calling and real-time audio with WebRTC and SIP, including push wake-up, background work and call-screen integration.
AI inside the app
Assistants, search and summaries in your app, connected to an agent or RAG backend, or run on the device.
Store release
Signing, Play Store and App Store listings, review, staged rollout and crash monitoring. We take the app all the way to users.
How a project runs
Working builds from the first weeks.
You do not wait months for a first look. A build you can install arrives early, and a new one arrives every week.
Build
Every week
Features arrive in weekly builds on TestFlight and Play internal testing, with a short written update.
- Weekly installable build
- Automated tests and CI
- No surprises on the invoice
Release
Launch and after
Accessibility, performance and security checks, then store review and staged rollout. Handover or ongoing support.
- Accessibility and performance checks
- Store review handled
- Handover or support
FAQ
Questions about mobile apps.
Do you build native or cross-platform apps?
Both. We build native apps in Kotlin and Jetpack Compose for Android, and Swift and SwiftUI for iOS and macOS. When one shared codebase is the better trade-off, we use Flutter.
When is native the better choice?
When the app depends on platform features such as background work, audio, Bluetooth, widgets or the newest system APIs, or when performance and platform feel are important. For content and form-based apps on a tight budget, Flutter is often enough.
Can you take over an existing app?
Yes. We start with a code audit that lists risks, outdated dependencies and quick wins. After that we can stabilize the app, move it to a modern architecture step by step, or add the features you need.
Who owns the code and the store accounts?
You do. Source code, the Apple Developer and Google Play accounts, cloud accounts and documentation are yours from day one.
Do you also build the backend?
Yes. We build APIs, databases and CI/CD on AWS, Google Cloud or Azure, so the app and its backend come from one team.
Related
Related work and services.
Oh My Android
A Mac control panel for the Android Emulator, built from our own daily Android work.
macOS apps
Native Mac apps and menu-bar utilities, signed and notarized under Royan AB's Developer ID.
Code audit
A fixed-scope Android or iOS code audit before a rewrite, a takeover or a big release.