BlogMobile

Mobile App Development in 2026: What Changed and How to Build Well

Mobile development has changed a great deal since 2023. Cross-platform frameworks matured, phones now run language models locally, and court rulings and regulation rewrote the app store rules. Below is a short history, the changes of 2025 and 2026, and the practices we follow when we build and test mobile apps.

, 5 min read

How we got here

App stores created the market

Apple opened the App Store on 10 July 2008 with more than 500 native apps, and Google's Android Market followed in October 2008. One place to publish and get paid turned apps into a business, and the stores became gatekeepers for quality and security as well as distribution.

In 2025 Apple rejected more than 2 million app submissions and stopped over $2.2 billion in potentially fraudulent transactions. Google kept more than 1.75 million policy-violating apps off Google Play in the same year.

Cross-platform frameworks grew up

Early apps were written twice, once for each platform. Frameworks that share code between iOS and Android are now a mainstream choice:

  • Flutter ships several stable releases a year, most recently version 3.50 in November 2026.
  • React Native turned on its New Architecture by default in version 0.76 in October 2024, replacing the old asynchronous bridge between JavaScript and native code.
  • Kotlin Multiplatform lets teams share business logic and keep native screens, and Compose Multiplatform for iOS became stable in May 2025.
  • Microsoft ended support for Xamarin on 1 May 2024. Its successor is .NET MAUI, and apps still on Xamarin no longer receive fixes.

What changed recently

Language models run on the phone

Apple's Foundation Models framework, introduced at WWDC 2025, gives apps an on-device language model with structured output and tool calling. On Android, the ML Kit GenAI APIs run Gemini Nano on supported devices for summarization, proofreading, rewriting and image description. Processing on the device keeps user text off your servers and works offline. The model, its prompts and its output also become part of the app's attack surface, so prompt injection and data leakage belong in the test plan.

Distribution rules changed

  • In the EU, the Digital Markets Act opened iOS to alternative app marketplaces. Apple changed its EU terms again on 1 October 2026, replacing the Core Technology Fee with a 5% commission on digital sales in apps distributed outside the App Store.
  • In the United States, after the Epic v. Google case, Google has not required Google Play Billing for US users since 29 October 2025, although alternative billing and external links carry service fees from 1 October 2026. Rulings in Epic v. Apple let developers link users to outside payment, subject to ongoing litigation.
  • Android now requires every app on certified devices to come from a verified developer, wherever it is installed from. Enforcement began in Brazil, Indonesia, Singapore and Thailand on 30 September 2026, and Google plans to extend it worldwide in 2027.

For a product team this means more choice about where to sell and how to take payment. Each option has its own contract terms, fees and compliance checks.

Store requirements move every year

Since 28 April 2026, apps uploaded to App Store Connect must be built with Xcode 26 and an iOS 26 SDK. Since 31 August 2026, new apps and updates on Google Play must target Android 16 (API level 36). Since 1 May 2024, Apple has required apps to declare approved reasons for certain APIs in a privacy manifest, and commonly used third-party SDKs must ship their own signed manifest. An app nobody has touched for a year cannot ship even an urgent fix until it is rebuilt with the current tools and retargeted to the current API level.

Phishing has moved to phones

In the phishing simulations covered by Verizon's 2026 Data Breach Investigations Report, the median click rate for text message and voice lures was about 40% higher than for email. Phones hold the sessions, one-time codes and tokens that open company systems, so a compromised phone or app can open the way into the company.

Passkeys remove the password that phishing steals. Android supports them through Credential Manager, and Apple syncs them across devices through iCloud Keychain. By May 2025, the FIDO Alliance counted passkey support on 48% of the world's top 100 websites.

Accessibility is a legal requirement in the EU

The European Accessibility Act has applied since 28 June 2025 to services that include e-commerce and consumer banking, and their mobile apps are part of those services. The same work helps every user: larger touch targets, readable contrast, and labels that assistive technology can read.

Practices that still hold, updated

1. Start with the user and the rules

Define who the app is for, the one task it must do well, and how you will measure that. Check the store rules, payment model and regulations that apply before design starts, because they shape the architecture.

2. Choose native or cross-platform on purpose

Cross-platform frameworks suit most business apps, where one team ships both platforms from one codebase. Native development suits apps built on the newest platform features, heavy graphics or deep hardware access. Kotlin Multiplatform sits between the two, with shared logic and native screens.

3. Ship a small first version

A minimum viable product puts the core task in front of real users quickly. Measure usage from the first release, and declare the analytics SDK in Apple's privacy manifest and in Google Play's Data safety form.

4. Build security in from the first sprint

  • Use the OWASP MASVS (version 2.1, which added a privacy category) as the list of requirements, and the OWASP MASTG as the testing guide.
  • Keep secrets and API keys out of the app, since anything in the binary can be extracted.
  • Store tokens in the iOS Keychain or the Android Keystore, and offer passkeys where accounts allow it.
  • Enforce every authorization rule on the server. Our API security article shows what happens when an API trusts the app.

5. Test on real devices and real networks

Run functional, usability, performance and accessibility tests across a range of devices and OS versions, including slow connections and offline use. Before a major release, add a penetration test of the app and the API behind it.

6. Budget for maintenance

Plan at least one platform update cycle a year: new iOS and Android versions every autumn, new store target requirements, SDK and dependency updates, and security fixes.

Jetlink builds mobile apps together with their backends and integrations, and tests iOS and Android apps and the APIs behind them. Our penetration testing guide explains what a test of an app and its API covers.

Have a system that needs this kind of attention?

info@jetlink-s.com