What Shaped App Development in the UK in 2026
If you asked most people what changed in app development this year, they'd say AI. And AI did change things, though not always in the way the headlines promised.
But looking back over 2026 from our studio in High Wycombe, the bigger story for UK businesses that own or commission apps was something less glamorous: the rules changed. The UK's competition regulator started enforcing new obligations on Apple and Google. Age checks stopped being a social media problem and became everybody's problem. Both app stores made maintenance compulsory. The UK's data law moved on. And the first wave of apps built entirely by AI prompts ran into some very public security trouble.
If you're a founder, an operations lead or a business owner with an app on the roadmap (or already in the store), this is our round-up of what shaped UK app development in 2026, and what we learnt along the way.
1. Apple and Google made maintenance compulsory
This was the year "we'll leave the app alone for a while" stopped being an option.
Apple: since 28 April 2026, every app submitted to the App Store has had to be built with Xcode 26 and the iOS 26 SDK. For many apps, that meant adapting to Apple's new "Liquid Glass" design language, even if nothing about the app's features had changed. iOS 27 then arrived on 14 September.
Google: from 31 August 2026, new apps and updates on Google Play must target Android 16 (API level 36). Existing apps that fall too far behind stop being shown to new users on newer phones. Android 17 also landed in June, with new limits on app memory and more privacy controls around location and contacts.
None of this is dramatic on its own. Together, it means every app now has a platform "tax": a regular, unavoidable amount of work just to stay listed, stay compatible and stay looking current.
What we learnt
The real cost of an app doesn't stop at launch, something we cover in our transparent breakdown of what it costs to build an app in the UK in 2026, and this year made that impossible to ignore. The apps that coped best this year were the ones whose owners already treated maintenance as a normal running cost. The ones that struggled had gone a year or more without an update and hit the deadlines all at once.
2. The app stores got fairer for UK businesses
For years, UK developers had little recourse when an app was rejected with a one-line explanation, or when store fees ate into margins. 2026 started to change that.
In October 2025 the Competition and Markets Authority (CMA) designated Apple and Google as having "strategic market status" in mobile platforms. From 1 April 2026, new commitments came into effect: fair and transparent app review with clear timeframes, proper reasons when an app is rejected, a route to appeal, fair search rankings, and a promise not to use developers' data to compete against them.
Then, on 30 June, Google cut its Play Store service fees (to 10% on a developer's first $1m of annual earnings, and on subscriptions) and opened the door to alternative payment options in the UK. On the same day, the CMA consulted on further rules that would let apps "steer" customers to pay outside the app stores, and would open up the iPhone's contactless (NFC) chip to other developers. Apple has pushed back hard, and at the time of writing a decision is still pending.
What we learnt
How an app takes payment has become a genuine design decision rather than a default, and UK businesses now have real leverage when an app review goes wrong. After years of being told "that's just how the app stores work", 2026 showed that the rules can change, and that the UK regulator is willing to change them.
3. Age checks became everyone's problem
In 2025, age verification felt like something for social networks and adult sites to worry about. In 2026 it spread much wider.
Apple introduced new 13+, 16+ and 18+ age ratings, and developers had to re-answer the age rating questions by 31 January.
In March, with iOS 26.4, Apple began device-level age checks for UK users, and apps can now ask Apple for a user's age band through its Declared Age Range API rather than collecting a date of birth themselves.
On 15 June, the government announced a ban on social media for under-16s, due to take effect from spring 2027. It goes further than social networks: wider services, including gaming, will need to switch off livestreaming and messaging with strangers for under-16s. Ofcom is due to report to Parliament on how reliable age checks could work by the end of October.
What we learnt
Age assurance is no longer a niche concern. Any app with chat, community or user-generated content features is now part of the conversation. We also learnt that the platforms can do much of the heavy lifting: using the tools Apple provides is usually simpler, and far better for privacy, than an app building its own ID checks.
4. UK data law got a little simpler, and a little stricter
The Data (Use and Access) Act 2025 was brought into force in stages, completing on 19 June 2026. A few changes matter directly to app owners:
Some cookies and similar technologies no longer need consent, including analytics used purely to understand and improve your service. Advertising and tracking still do.
You must make it easy for people to complain about how you use their data (for example, through an online form) and acknowledge complaints within 30 days.
Online services likely to be used by children must actively take their needs into account.
What we learnt
Many apps are still asking users for consent they no longer legally need, which adds friction for no benefit. At the same time, the new complaints duty means privacy can't just be a policy page; it has to be something a user can act on from inside the app.
5. Accessibility got teeth
The European Accessibility Act came into force in June 2025, and in 2026 we saw what enforcement looks like. On 4 June 2026, a French court ordered Carrefour to make its website and app fully accessible within six months, with a daily penalty for missing the deadline. It was the first ruling under the Act to name a mobile app specifically, and the court rejected the argument that being "mostly" compliant was good enough.
What we learnt
Being "mostly accessible" is no longer a defence, at least for anyone selling into the EU. It reinforced something we already believed: accessibility is far cheaper to design in from the start (screen reader support, text scaling, colour contrast, clear focus states) than to retrofit once a complaint arrives.
6. Vibe coding met reality
2026 was the year of "vibe coding": building apps by describing them to an AI tool and letting it write the code. It promised apps in an afternoon. For prototypes and experiments, it often delivered.
For production apps, the picture was different. In March, the chief executive of the National Cyber Security Centre, Richard Horne, warned that AI-generated code currently poses unacceptable risks for many organisations, even as he urged the industry to use the moment to make software more secure. In May, Axios reported on research that scanned around 380,000 apps built on popular AI app builders and found thousands leaking data, including a UK healthcare firm's clinical-trial information and a British retailer's customer chat logs.
The lesson isn't that AI is bad. It's that code nobody fully understands is a liability, especially once real customers and real data are involved. It's why we made the choice we explain in Proudly Human: Why We Don't Use AI in Development: every line of code we ship is written by a developer who understands it and can explain it.
What we learnt
AI app builders are a perfectly good way to test an idea quickly. The trouble starts when a prototype quietly becomes the production app and real customer data starts flowing through it. The question to ask of any app isn't "how fast was it built?" but "who understands this code, and who can explain it a year from now?"
7. AI moved inside the app
While AI-written code had a rocky year, AI features had a very good one.
At WWDC in June, Apple expanded its Foundation Models framework so apps can use on-device and cloud AI models through a single interface, added a new Core AI framework for running custom models on the device, and extended App Intents so Siri can work with content inside apps. Apple is also giving members of its Small Business Program free access to its next-generation cloud models.
In plain English: things like smart search, document scanning and summaries, personalised recommendations and natural-language features are now much cheaper to build, can often run privately on the user's phone, and are fast becoming something users simply expect.
What we learnt
The best AI features this year didn't start with "how do we add AI?". They started with a job users were already doing in the app, and made it faster. That's a very different brief, and it leads to far better products. Building AI into apps properly is work we love doing; letting AI write the app is where we draw the line.
Talk to us
At Boom Software, we design, build and support mobile and web apps for businesses across the UK, from our base in High Wycombe, Buckinghamshire. Every line of code is written by a person who understands it, and we stick around after launch to keep your app compliant, current and working.
If any of the changes above affect your app, or you're planning something new, get in touch. We'd love to hear about it.