.avif)
.svg)
.svg){kind=small}
Table of Contents
Published on
4/9/26
-
5 min
Do you have an app project and feel stuck on the platform question? Discover our mobile app development services and how we address this choice right from the kickoff workshop.
It’s the first question asked in almost every scoping workshop: "Should we launch on iOS or Android first?" For ten years, answering that meant a painful trade-off between market reach and budget. That’s no longer really the case. The right question is no longer "which platform," but "which architecture allows me to avoid choosing."
Behind this question almost always lies a budget constraint. Developing natively for two platforms means funding two projects that share nothing but their specifications. Faced with this wall, many companies decided to cut their market in half—only to discover six months later that their most engaged users were on the platform they had discarded.
The reasoning needs to be flipped: start by looking at where your users are, then choose the architecture that allows you to serve them all. The question of the cost of a custom application comes after, not before.
According to StatCounter, the French mobile market was split at the beginning of 2026 with around 65% for Android and 34% for iOS. France remains one of the European markets where the iPhone is most prevalent—ahead of Germany, where iOS tops out at around 27%—but far from the parity seen in Nordic countries.
Above all, remember the scale: one-third of your potential audience is on iOS, two-thirds on Android. Ignoring one of the two platforms means depriving yourself of a major fraction of your market before you've even written a single line of code.
Market share only tells half the story. The behavioral differences between the two user bases are well-documented and stable over time.
According to Business of Apps, the App Store generated nearly $117 billion in spending in 2025, compared to $49 billion for the Google Play Store—even though nearly three times as many apps were downloaded on Android. When broken down per user, the spending gap is significant. If your model relies on subscriptions or in-app purchases, iOS carries structurally much more weight than its market share would suggest.
In France, iOS is overrepresented among executives, professionals, and urban residents aged 25-45. Android has broader coverage among 18-25 year olds, seniors, and those in suburban and rural areas. A mass-market project needs both; a B2B tool aimed at corporate management will naturally lean toward iOS.
In professional environments with managed device fleets—such as banking, healthcare, consulting, and manufacturing—iOS often makes up the majority of the hardware, due to fleet management and update cycle requirements. If you are selling a business application to large accounts, check your prospects' mobile policies before making a decision.
Android gives you volume, while iOS gives you revenue per user. In more than nine out of ten projects, the rational answer is: both. The challenge is how to fund it—and that is where technical architecture becomes a business decision.
Beyond user habits, the two ecosystems impose very different production constraints.
A point often overlooked in Anglo-Saxon comparisons: the European Digital Markets Act has changed the rules of the game for iOS within the European Union. Since January 1, 2026, Apple has implemented a unique economic model in Europe, where the former Core Technology Fee of €0.50 per annual install has been replaced by a Core Technology Commission of 5% on sales of digital goods and services. Alternative app stores and web distribution are also now permitted on iOS in the EU.
In practical terms: if your model relies on subscriptions and your market is European, the economics of iOS distribution are no longer what they were in documentation from two years ago. This factor should be calculated during the business planning phase, not discovered at launch.
Historically, covering both platforms meant running two projects in parallel: two teams, two codebases, two QA cycles, and two delivery schedules.
Doubling the initial budget is just the tip of the iceberg. Over time, it’s the recurring costs that really hurt:
For a startup or an SME, this cost structure is rarely sustainable. This is precisely what has made cross-platform approaches essential.
Modern cross-platform development is nothing like the hybrid solutions of the 2010s, which simply displayed a web page in a container. Today's frameworks compile into genuine native components. It is not a degraded compromise: Microsoft uses it for Teams, Shopify for its main application, and Discord for its user base of several hundred million.
Created by Meta, React Native allows you to write the application in TypeScript, using the same component logic as React on the web, and compile it into native iOS and Android UI components. The user perceives no difference compared to an application written in Swift or Kotlin — because the same components are displayed on screen.
Expo sits on top of React Native and removes a large part of the tooling friction. Three building blocks are real game-changers in production.
Compilation happens in the cloud. Your developers no longer need a macOS workstation to produce an iOS binary, which simplifies both team equipment and continuous integration.
Over-the-air updates allow you to deploy a fix directly to devices without submitting a new version for approval. For a blocking bug in production, you go from several days of waiting to just a few minutes.
Camera, geolocation, push notifications, Bluetooth, NFC, biometrics, payments: native APIs are exposed via maintained modules. Expo's universal routing also allows you to generate a web application from the same codebase, which opens up a "web first, mobile second" strategy.
React Native is not the only credible option. Flutter, backed by Google, offers a different approach: the framework draws the interface itself instead of relying on system components. The rendering is perfectly identical from one platform to another, at the cost of a more visible gap with the interface conventions of each OS. The choice between the two depends on your team's profile and the importance you place on adhering to native design patterns.
For a MVP of a business application, this typically means a simultaneous iOS and Android launch in two to three months. We break down the costs in our article on the real cost of building a mobile application.
In this scenario, also explore no-code approaches: they sometimes allow you to validate a hypothesis without committing to custom development.
If you answer yes to at least three of these questions, cross-platform is the rational choice.
For the vast majority of corporate projects we support, cross-platform is the best trade-off: a truly native application on both platforms, delivered faster, with a controlled budget and sustainable maintenance.
Exceptions exist and we stand by them: video games, low-level hardware access, proprietary SDKs. Outside of these cases, effort should be focused elsewhere — on design UX/UI, on the quality of functional scoping, and on the choice of partner. Our mobile projects provide a concrete overview of what this approach produces, and we have detailed our criteria in a guide on how to choose an app development agency.
Want to know how much your project will cost and how long it will take on both platforms? Describe your needs to us, and we will get back to you within 48 hours with a detailed estimate: request a quote.
