Which platforms and frameworks do you build with?

We build native iOS (Swift), native Android (Kotlin), and cross-platform apps in Flutter or React Native. The right path depends on your audience, budget, timeline and how much native depth the product needs — each has its own dedicated page.

Service · Mobile App Development

Mobile app development for focused MVPs and product companions.

99 Francs® develops lean mobile app experiences for startups, SaaS products, AI tools and mobile-first workflows when the goal is a clear first release, not an endless product platform.

Mobile app development from $8,000 (cross-platform MVP).

Discuss app development→See design path

150+

shipped projects

$32M+

raised by clients

9,000+

tasks delivered

Direct answer

99 Francs provides mobile app development services for focused apps that need to ship cleanly.

The service covers app scoping, native iOS (Swift) and Android (Kotlin) builds, cross-platform development in Flutter or React Native, core flows, responsive states, integration assumptions, QA notes, App Store and Google Play submission, and a PWA path where a lightweight web app fits.

Build paths

Choose native or cross-platform by audience, budget and timeline.

Each page answers one build question directly — iOS, Android, Flutter or React Native — and routes into a scoped mobile development plan.

iOS App Development

Native iPhone and iPad apps in Swift, built to Apple's guidelines and ready for the App Store.

Build for iOS

iPhone Duo App Adaptation

Get an existing iOS app ready for Apple's foldable: audit, 7.6-inch layouts and SwiftUI or UIKit changes.

Adapt for iPhone Duo

Android App Development

Native Android apps in Kotlin, built to Material conventions and ready for Google Play.

Build for Android

Flutter App Development

One Dart codebase shipping to iOS and Android with a near-native feel — fast and cost-efficient.

Build with Flutter

React Native Development

One JavaScript/TypeScript codebase for iOS and Android — fast iteration on a familiar React stack.

Build with React Native

What we build

Mobile development with product scope discipline.

The strongest mobile builds do not start with every possible feature. They start with the app surface that proves the product can be useful, trusted and used repeatedly.

Mobile app scope

We reduce the app to the smallest useful release: core flows, roles, data needs, integrations, platform choices and launch constraints.

Cross-platform build

We can build focused mobile apps in React Native or Flutter when one codebase is the practical path to iOS and Android.

Native app execution

When the product needs native behavior, we can scope Swift-based iOS work or platform-specific implementation around the critical flows.

Release-ready product surface

The build includes responsive states, forms, navigation, API handoff assumptions, QA notes and App Store preparation where needed.

Best fit

Use mobile app development when the app scope is focused enough to become a real release.

You need a focused app MVP

We build when the first version has a clear purpose: validate a workflow, support a web product, launch a companion app or prove a mobile-first idea.

The app should not become a huge platform

We keep the scope tight: fewer features, cleaner architecture, clearer flows and a build plan that prioritizes what users actually need first.

The design already exists

If you already have Figma screens, prototypes or a product design system, we can turn that into a working mobile app surface.

The app still needs product judgment

Development stays close to UX. We flag unclear flows, missing states and risky assumptions before they become expensive implementation problems.

Process

From app scope to working mobile product.

We keep the implementation tied to the intended product behavior: clear navigation, reliable states, practical integrations and a first version that can be tested.

Scope the first release

We review the product goal, design maturity, APIs, accounts, content, integrations, analytics, platform needs and App Store constraints.

Plan the app architecture

We define the mobile stack, data flow, navigation, state model, component structure and the parts that should stay out of v1.

Build the core flows

We implement the screens, navigation, forms, states, integrations and app behavior needed for a credible mobile MVP or companion app.

Test and prepare launch

We review responsive behavior, device states, bugs, content, analytics events, store assets and what the team needs after handoff.

Related work

Native apps we built, shipped and still run ourselves.

Swift and SwiftUI on iPhone, Kotlin and Compose on Android, with the backends, subscriptions and widgets behind them. Our own products, so every decision in them is ours to explain.

iOS App · Widgets

My Chess Rating our own iOS app

Our own iPhone app and home-screen widget that puts Chess.com and Lichess ratings in one place and explains why they move: tilt check, best hours, openings that cost points, goals and a Sunday report. SwiftUI, WidgetKit and StoreKit 2 on a Node and Postgres backend, designed, shipped and run by 99 Francs.

Android App · VPN

SimpleV VPN our own Android app

Our own one-tap VPN for Android: no account to start, no traffic logs, WireGuard or Xray Reality to get through networks that block VPNs. A Kotlin and Compose app, an Express and Postgres control plane on Railway and exit nodes on Vultr that start on demand, live on Google Play about two weeks after active work began, plus a Chrome extension that protects the browser on the same accounts.

Mobile App · iOS, Android, Mac, Watch

Timeslide our own world clock

Our own world clock where every city is a card: drag one sideways and a single shared time moves across all of them, with the weather for that hour. Built natively for iPhone, Android, Mac and Apple Watch, with widgets, GPU weather shaders and 8 languages. On the App Store and Google Play.

Guides

Questions teams ask before building a mobile app.

Browse services→Ask about app development→

99 Francs develops focused mobile app MVPs, SaaS companion apps, AI app surfaces, internal tools and cross-platform mobile experiences when the scope is lean, product-led and realistic to ship.

Yes. If the app UX or UI is not ready, the project should start with mobile app design before development begins.

Not as the default offer. This service is best for focused MVPs, product companions, startup apps, AI app interfaces and lean mobile products where the first useful release matters most.

We build native iOS (Swift), Android (Kotlin), and cross-platform apps in Flutter or React Native. Each has its own page.

Mobile app development starts at $8,000 for a cross-platform MVP. What moves the price is platform choice (native vs. cross-platform), integrations, backend complexity and app-store submission needs. Every build runs in fixed-price phases with no upfront payment — see how we work.

Yes. We prepare the build configuration, store listing assets and screenshots, help with review and policy preparation, and support the submission so the app reaches users on the App Store and Google Play — not just an internal test build.

Sometimes a Progressive Web App (PWA) is the right call — when reach, instant access and a single web codebase matter more than native device features or app-store presence. We scope a PWA when it genuinely fits, and recommend native or cross-platform when the product needs store distribution or deeper device capabilities.

No. Like every 99 Francs project, mobile app development runs in fixed-price phases with no deposit — you pay only once a phase is built and working. See the full breakdown of how we work.