Wall & Fifth

iOS and Android App Development UK: Both Platforms Without Doubling Cost

Should UK founders build for iOS, Android, or both? Why the UK platform split changes everything, and how React Native ships to both stores without doubling your budget.

By William · Updated 1 November 2026 · 11 min read

For UK founders the iOS versus Android decision is more nuanced than global data suggests. Globally, Android holds a substantial majority of smartphone usage, but the UK market is split far more evenly between the two platforms — meaning that building for one store alone means excluding a large portion of your reachable audience before you have written a line of code. The good news is that modern cross-platform tooling, particularly React Native, means you no longer have to choose between the two stores at double the cost. The decision is now less about which platform and more about which build approach, and getting that right from the start avoids expensive rework later. For a full picture of the decisions that shape any mobile build, the guide to custom app development decisions covers platform, stack, ownership, and team seniority.

The UK platform split and why it changes the calculus

Most global discussions about mobile platforms assume Android dominance, and globally that picture holds. In the UK, the balance is considerably closer. Check a current source such as Statcounter for the latest UK-specific figures, but the practical implication for most product decisions is that neither platform commands a comfortable lead.

This near-equal split has a direct implication for product decisions. A consumer app, a marketplace, or a B2C SaaS product that launches on iOS only is unavailable to a very large share of its potential UK user base. The mirror problem applies to Android-only builds. In practice, many British mobile publishers end up releasing on both stores precisely because the UK market does not give either platform a comfortable lead.

There are cases where a single platform makes sense at launch, particularly if your audience skews strongly one way. A B2B tool where every user is on a company-issued handset of a known type is a legitimate reason to go single-platform first. But these are specific decisions that should follow audience research, not assumptions imported from US or global market data.

Native versus cross-platform: what the trade-off looks like in 2026

Once you have decided your target platforms, you face a second, equally important question: build natively on each platform, or use a cross-platform framework that compiles to both?

Native development

Building natively means Swift for iOS and Kotlin for Android — separate codebases, separate developers, separate release cycles. The upside is maximum access to platform-specific APIs, the tightest possible integration with OS-level features, and no abstraction layer sitting between your code and the device.

The downside for most early-stage products is significant: two builds to maintain, two sprint cycles to coordinate, and broadly double the engineering cost for the same feature set. Native is the right call when your app depends on hardware capabilities that cross-platform tools handle poorly — advanced camera pipelines, Bluetooth Low Energy peripherals, real-time audio processing — or when you are handling data sensitive enough that any abstraction layer introduces meaningful risk.

React Native and Expo

React Native, Meta's cross-platform framework, allows a team to build a single JavaScript codebase that compiles to genuinely native UI components on both iOS and Android. This is not a web view wrapped in a shell — the output is native rendering on each platform, which means the app feels and performs like a platform-native product to end users.

The practical benefit for most founders is a single team working on one codebase that ships to both stores. Platform-specific work — push notification configuration, navigation gestures, platform-specific UI patterns — sits at the edges, while the core product logic is shared. Expo, the tooling layer that sits on top of React Native, further reduces configuration overhead and simplifies the App Store and Google Play submission process.

Wall & Fifth builds mobile products in React Native and Expo. The MVP mobile app development service covers how this approach ships to both stores from a single codebase, including handling the submission process as part of the project.

One caveat worth understanding: React Native's abstraction layer can introduce a short lag when Apple or Google make significant changes to core OS APIs. In practice this means updating your React Native version and Expo SDK after major OS releases — routine maintenance rather than a structural problem, but one to account for in your ongoing support budget.

What the App Store and Google Play submission process actually requires

Many founders underestimate the submission requirements for both stores. Building for compliance from the start rather than retrofitting it saves real time and money.

Apple App Store

  • Privacy manifest and usage descriptions: Apple requires apps to declare every API that accesses sensitive data — camera, location, contacts, health data — with a plain-language justification visible in the App Store listing. These must be configured in the app, not added as an afterthought.
  • App Review: Apple reviews every submission before it appears on the store. Review timelines vary and can be affected by the nature of the submission, any policy questions it raises, and whether rejections require substantive changes to functionality or privacy declarations. Check Apple's developer documentation for current guidance on expected timelines.
  • In-app purchase rules: If your app sells digital goods or subscriptions within the app, Apple requires use of its in-app purchase system and takes a commission. This applies to purchases made through the app itself, not to purchases made through a web-based checkout.
  • TestFlight: Apple's beta distribution tool lets you distribute pre-release builds to testers before your public submission. Using TestFlight for a real-user validation phase before your public launch is sound practice. Check Apple's current developer documentation for the latest limits on tester numbers.

Google Play

  • Target API level: Google requires apps to target a recent Android API level. Failing to keep this current can result in your app being removed from the store or becoming unavailable to new installs on newer Android versions.
  • Data safety section: Like Apple's privacy nutrition label, Google requires a declared data safety section in the Play Store listing explaining what data your app collects, whether it is shared, and whether it can be deleted on request.
  • Review timelines: Google Play's review process varies by app category. Apps in sensitive categories receive additional scrutiny and may take longer. Check Google's current Play Console documentation for up-to-date guidance on review timelines.
  • Billing API: Google has its own in-app billing requirements covering digital goods and subscriptions, analogous to Apple's rules.

Both stores require a developer account, with fees set by Apple and Google respectively — check each company's current developer programme pages for the latest registration costs. Register both accounts in your company name, not a personal account — particularly important if you intend to raise investment or transfer the product later.

Timelines and costs: dual-platform mobile versus web

A common question is whether building for both iOS and Android meaningfully increases cost and timeline compared to a web app or a single-platform mobile build. The honest answer depends on the approach you take.

Build typeRelative costIllustrative timelineKey trade-offs
Web app (responsive)Lower6–10 weeksNo App Store friction; instant updates; push notifications require additional work
React Native (iOS + Android)Moderate8–12 weeksBoth stores from one codebase; push notifications; offline support; App Store review cycle
Native iOS onlyModerate8–12 weeksMaximum iOS performance; Android excluded
Native iOS + Native AndroidHigher16–24 weeksMaximum performance on both; two codebases to maintain indefinitely

Timelines and cost bandings above are Wall & Fifth's editorial guidance for a first-version product of moderate complexity, not independently benchmarked industry figures. Actual scope — number of user roles, integrations, admin tooling, and decision speed — moves every project within and beyond these ranges.

For a detailed view of what drives price, the honest breakdown of custom app costs in the UK covers the five variables that move a quote most significantly.

A decision framework for founders choosing their first platform

Most founders arrive at this decision before they have a clear answer. The following questions give a more reliable basis for the choice than assumptions about which platform is more popular.

  1. Where does your audience actually live? If you have existing users, survey them. If you are pre-launch, look at comparable products in your category and research their platform distribution. For UK consumer apps, treat the split as close until you have data suggesting otherwise.
  2. What is the core experience? If your product's primary value requires a camera, location awareness, push notifications, or offline access, mobile is the right choice. If the core value is a dashboard, a workflow tool, or something users will primarily access at a desk, a web app may serve your first version better and with less friction.
  3. How sensitive is your monetisation model to App Store commission? If your revenue relies on in-app subscriptions or digital purchases, both Apple and Google take a share. If your business model works primarily through web-based payments, a progressive web app or web-first approach sidesteps that cost — at the expense of the native app experience.
  4. How important is App Store discoverability? App Store and Google Play have their own search ecosystems. Products in categories where people browse the stores to find solutions — productivity tools, fitness apps, games — benefit from being listed. Products where users arrive through search or word of mouth may not need that channel initially.
  5. What is the cost of excluding a large part of the market? If you are building a two-sided marketplace or a consumer social product where network effects matter, launching on one platform could meaningfully slow early growth. If you are building a focused B2B tool for a specific company, your audience may be on a single platform by policy.

A hypothetical example

Hypothetical scenario: A founder is building a UK on-demand booking platform for personal trainers and clients. The clients need to book, receive notifications, and check in on the go. The trainers need to manage their availability and see their day's schedule from their phone. Neither user type is primarily at a desk. The UK market means the client base will be split between iOS and Android. A React Native build shipping to both stores from one codebase is the natural choice: it keeps the engineering budget sensible, reaches both halves of the market, and supports the push notification and location features the product needs. Going native on iOS alone would exclude a substantial portion of the potential client user base at the point in the business when growth matters most.

When native is genuinely the better call

Cross-platform development is the right approach for most first-version products, but there are specific situations where a native build is the stronger decision.

  • Advanced hardware integration: Apps that depend on Bluetooth LE peripherals — fitness hardware, medical devices — advanced camera processing, or real-time audio engineering often need native APIs that cross-platform frameworks either do not expose or expose inconsistently across OS versions.
  • Extremely performance-sensitive UI: Products where frame rate, animation precision, and rendering performance are genuinely differentiating — advanced graphics, augmented reality, high-frequency data visualisation — are better served natively.
  • Regulatory requirements: Some regulated industries have certification requirements or data handling mandates that are more straightforward to demonstrate compliance with on a native stack where every layer is visible and auditable.
  • You have already validated one platform: If you have built a strong iOS user base through a native app and are now expanding to Android, building the Android version natively rather than migrating the whole product to React Native is sometimes the least disruptive path.

In practice, most SaaS products, marketplaces, on-demand platforms, booking tools, social apps, and productivity tools are well served by React Native. The cases that genuinely require native are narrower than many native-development advocates suggest.

Frequently asked questions

Should I build iOS first and add Android later?

In markets where iOS clearly dominates, an iOS-first strategy makes sense. In the UK, where the split is close, launching iOS-only means excluding a large share of your addressable audience from day one. If budget is the constraint, the more efficient answer for most UK founders is a React Native build that ships to both stores simultaneously, rather than a native iOS build followed by a separate Android project later. Two separate native builds done sequentially will, in most straightforward cases, cost more in total than one React Native build reaching both platforms — though actual savings depend on scope and complexity.

Is React Native good enough for a production app, or is it just for MVPs?

React Native has been used in production by large consumer apps for years, and the framework has matured substantially with architectural improvements to its rendering and module systems. The more useful question is whether it is appropriate for your specific app, based on technical requirements. For most founders building consumer apps, marketplaces, SaaS tools, and on-demand platforms, it produces a product that is indistinguishable from native for end users. It is not the right tool for apps with demanding hardware integration or extreme rendering requirements.

How long does App Store review actually take?

Apple and Google each publish guidance on their review processes, and timelines can change. In general, the duration depends on the nature of the submission and whether any policy questions arise — rejections that require substantive changes to functionality or privacy declarations can extend the process significantly. Building for review compliance from the start — correct privacy manifests, appropriate permission usage, compliant in-app purchase implementation — is far more efficient than addressing rejections after submission. Consult Apple's and Google's current developer documentation for the latest expected timelines before planning your launch.

Can I charge for my app without paying Apple or Google a commission?

Both stores require the use of their in-app purchase systems for digital goods and subscriptions sold within the app, and both take a commission. If your business model relies on subscriptions, you can offer the subscription through your website and allow users to sign in through the app without triggering the in-app purchase requirement — but the rules around pricing parity and external purchase links have evolved and continue to do so. Confirm the current requirements during your build planning rather than assuming the position from a year ago still applies.

Do I need separate developer accounts for iOS and Android?

Yes. Apple requires an Apple Developer Program membership and Google requires a Google Play Console account, each with their own registration costs — check both companies' current developer programme pages for the latest fees. Both accounts should be registered to the company, not to an individual's personal account, especially if you are building a product you intend to sell or hand over to investors later.

What happens when iOS or Android releases a major update?

Major OS releases occasionally require updates to your app to maintain store availability — particularly Apple's annual iOS releases, which sometimes deprecate APIs or introduce new requirements. With a React Native build, the response is typically an update to the React Native and Expo SDK versions and a re-submission to both stores. This is routine maintenance work rather than a rebuild. Your launch plan should include a clear answer to who handles this and what it costs.

Back to Custom App Development UK: A Senior-Led Studio That Builds the Real Thing

Work with Wall & Fifth

Have something to build? Let’s talk it through.

Start a conversationSee our work