--- title: "5 shifts reshaping the mobile industry right now" description: "On-device AI, apps for AI agents, subscriptions, foldable screens and smart glasses: the five big shifts in mobile right now, and what to do about each." author: "MH TOUFIK" published: 2026-11-10T03:00:00.000Z updated: 2026-11-05T17:34:51.000Z url: https://toufik.dev/blog/mobile-industry-shifts-2026 category: "Mobile Industry" tags: ["AI agents", "Foldables", "Mobile apps", "On-device AI", "Subscriptions"] --- # 5 shifts reshaping the mobile industry right now Over the last week and a bit, I've written about specific changes: Android Studio's AI agents, Xcode 27, Swift on Android, Kotlin 2.3, apps for Bangladesh. Step back a little, and they're all part of a few bigger shifts in the mobile industry. Here are the five I think matter most right now, and what each one means if you build apps or run a business that depends on one. ## 1. AI is moving onto the phone The biggest trend in almost every 2026 mobile outlook is **on-device AI**. Phone chips are now designed around running AI models locally, and both platforms give developers direct access: - Apple's **Foundation Models** framework now offers one Swift API for on-device models (which can take image input this year), larger models on Private Cloud Compute, and outside providers. - On Android, **Gemini Nano** and ML Kit bring on-device features to supported phones. **Why it matters:** on-device AI is private, works offline and costs nothing per request. Features like summarising, smart replies, translation and photo understanding are becoming normal expectations, not premium extras. **What to do:** pick one feature where AI clearly saves your users time, and try it on-device first. ## 2. Apps are being built for AI agents, too Until now, every app was designed for one user: a person tapping a screen. Now there's a second user: **the assistant**. Android's **AppFunctions** (in beta since October) and Apple's **App Intents** let assistants call your app's features directly. "Book my usual ride." "Add milk to my list." The user never opens the app. **Why it matters:** if an assistant can't use your app, it may simply pick a competitor's that it *can* use. **What to do:** expose the three to five actions your users repeat most. I wrote a [full guide to agent-ready apps](https://toufik.dev/blog/agent-ready-apps-appfunctions-app-intents) earlier this week. ## 3. Subscriptions won The money in apps has moved decisively to **subscriptions and in-app purchases**. Statista projects about **$810 billion** in total app market revenue for 2026, and only about **$4.4 billion** of that comes from paid apps. One industry analysis this year even found that **non-game apps out-earned games** in in-app spending for the first time. **Why it matters:** "pay once" is almost gone. Users pay for ongoing value: new content, sync, AI features or a service. **What to do:** if you charge, think about what keeps improving for the user every month. In markets like Bangladesh, small, flexible plans and local payment options matter more than a single global price. ## 4. Screens are getting bigger and stranger Foldables, tablets, Chromebooks, and on the iPhone side, simulators you can now resize freely in Xcode 27. Apps can't assume one portrait phone screen any more. Android is pushing hardest here: apps that target **Android 17** can **no longer opt out** of resizing and orientation changes on large screens (600dp and wider). A portrait-locked app *will* stretch and rotate on a tablet or foldable. **Why it matters:** an app that looks broken on a foldable looks broken to the people most likely to pay. **What to do:** test your main screens on a tablet and a foldable emulator, and use adaptive layouts in Compose or SwiftUI. ## 5. Glasses and wearables are coming back, quietly XR isn't mainstream yet, but this year it got more practical. At Android Dev Summit, Google showed **XREAL Aura** glasses running Android XR, and said the Jetpack XR libraries are now production-ready. Smart rings, watches and earbuds keep growing too. **Why it matters:** these devices won't replace phones soon, but they'll extend them, with quick glances, notifications and voice. **What to do:** nothing urgent. But if your app uses Jetpack Compose or SwiftUI, you're already most of the way to supporting these new screens when your users ask for it. ## The thread that ties them together Look at all five and there's one common idea: **the app is no longer a single screen in someone's hand.** It runs AI on the device, takes requests from assistants, adapts to any screen size and reaches beyond the phone. That sounds like more work, and some of it is. But the basics haven't changed: know what your users really come to do, make it fast and reliable, and respect their time, data and privacy. Get those right, and every one of these shifts becomes an opportunity, not a threat. Thanks for reading along this week. If you're planning an app and want to talk about any of this, [get in touch](https://toufik.dev/contact). I'd love to hear what you're building.