Mobile AI 2026: What Users Actually Want
AI features in mobile apps everywhere. But usage data tells a different story than what the hype suggests. Here's what people are actually using and paying for.
App Store policy changes. iOS privacy updates. Flutter 2.0. Three separate shifts that converge to make 2021 genuinely different for mobile development.
Abhi Asok
Founder & CEO, Arvension Technologies
I've been thinking about how to frame what happened in mobile development over 2021. The easy narrative is just technological—Flutter got better, tools improved, cross-platform development got easier. That's all true but it misses what's actually interesting.
2021 was the year that the economics of mobile app development fundamentally shifted. Not just technically. Economically. Structurally. The way we build apps, fund apps, and sustain them going forward is different from how it worked in the 2010s. That's worth unpacking before the year closes.
Apple's changes to the App Store started before 2021 but crystallized this year. The 30% revenue cut remained unchanged. That's not news. But the restrictions on how you can reach and monetize users got tighter.
Apple's privacy update in April—the App Tracking Transparency requirement—changed targeted advertising fundamentally. Apps that relied on tracking users across apps and sites for ad targeting suddenly couldn't. The impact was immediate and massive. Advertising effectiveness dropped. CPMs dropped. Companies that depended on ad-based mobile monetization got hit hard. Facebook screamed about it publicly because it directly hurt their ad business.
This sounds like a policy change, which it is. But it's actually an economic shift. The business model of "build an app, acquire users through targeted ads, monetize through ads" became way less viable overnight. That was a massive portion of the venture-backed app economy.
The companies that survive and thrive after this shift are the ones with direct revenue: subscription models, B2B applications, gaming companies with sophisticated monetization. The free-with-ads model that was dominant in the 2010s is harder now.
Google's Android changes came later but are heading in the same direction. Android is more open than iOS but Google is incrementally making it harder to track users and target ads precisely. Different timeline but same direction.
Flutter 2.0 in March wasn't the inflection point by itself. But it represented a maturity threshold. Flutter could now do web, mobile (iOS and Android), and had plans for desktop. One codebase, multiple platforms. Not perfectly—you still have platform-specific work. But the conceptual promise of "write once, run everywhere" became actually achievable for real applications.
That's different from five years ago. Five years ago, cross-platform mobile frameworks were all "write once, deal with broken everywhere." They improved gradually but they weren't compelling if you could just write native. Now they're actually compelling because the experience is comparable to native and you're saving massive development effort.
This matters economically because it reduces the cost of shipping on multiple platforms. A startup that would have needed to build a team for iOS and a separate team for Android can now do both with a single team. The unit economics of app development improved.
This also changes talent requirements. You need fewer specialists and more generalists. You need fewer people who deep-specialize in iOS. You need more people who understand Dart and Flutter and can ship multiple platforms.
Firebase became genuinely capable. Serverless backends became normal. Cloud infrastructure costs dropped. CI/CD pipelines became standard. Good analytics became cheap. These are infrastructure shifts but they affect how you build and ship mobile apps.
A team of two developers can now build and maintain an app that would have required five people in 2015. Not because they're more productive. Because the infrastructure does things for them that people used to have to build.
The quality of development tools improved. IDEs got better. Debugging got better. Testing frameworks got better. The daily experience of building a mobile app is materially better than it was three years ago.
These are small shifts individually but they compound. The friction of building a mobile app has decreased significantly.
Combine these three things—App Store economics changed, cross-platform development became viable, and development tooling improved—and you get a structural change in how mobile apps get built.
The economics that supported a massive ecosystem of venture-backed ad-supported apps broke down. The supply side responded by making it cheaper and faster to build cross-platform applications. And the tooling improved to support that lower cost structure.
What emerges is: fewer apps, better-funded apps, higher quality, focused on direct revenue models rather than ad-supported, built leaner with smaller teams, shipping across multiple platforms more efficiently.
The app studio model—small teams building multiple apps to diversify revenue—got harder. The economics don't work as well. You need more unit sales or more direct revenue to justify the time investment in an app.
There's a second-order effect here: consolidation. The companies that can maintain apps got bigger because the economics favor scale. But new app launches became harder because the bar for succeeding went up.
This has all happened before in software. The transition from boxed software to SaaS was similar. The low-friction model broke down and got replaced by something more efficient but with higher barriers to entry for new players.
B2B mobile apps are increasingly important. Remote work normalized. People expect enterprise software on their phones. That's different from the consumer app economy that was the focus of the 2010s.
Gaming remains strong because it has figured out the monetization problem. Subscription apps are growing because they've found more stable revenue than ads. Specialized verticals where mobile apps create genuine value—field service, logistics, operations management—are growing because they replace expensive inefficient processes.
What's not building momentum are casual games and ad-supported utilities. Those categories are basically done as a venture opportunity. They still exist but the economics don't work.
I think 2022 is when we fully internalize that the app economy that existed in 2015-2019 is gone. The business models that worked then don't work as well. The companies that adapted to direct revenue and specialized use cases are going to be the growth stories. The app studios and casual game companies are going to continue contracting.
Mobile development as a skill will increasingly be about building for specific business outcomes rather than trying to go viral or achieve escape velocity through ads. That's less sexy but it's actually more sustainable.
The turning point in 2021 wasn't one thing. It was three things converging: policy, technology, and tooling all shifted at the same time in directions that made mobile development both cheaper and more constrained. That creates opportunities for builders who understand the new economics and understand how to build for real outcomes instead of trying to grow-hack their way to success.
That's what actually changed.
AI features in mobile apps everywhere. But usage data tells a different story than what the hype suggests. Here's what people are actually using and paying for.
Nine years building mobile apps. The native vs cross-platform debate isn't settled by hype. Here's what the data actually shows and what it means for your next app.
On-device AI models (Apple Intelligence, Google Gemini Nano) make offline-first AI possible. Real patterns for building features that work without internet.