September 29, 2026 · Blogs
Discover how the UK's app economy is changing in 2026, including new CMA action involving Apple and Google, app-store rules, payments, security and opportunities for developers.
Mobile applications are now so deeply embedded in everyday life that it is easy to forget how economically significant the app ecosystem has become.
Banking, transport, retail, entertainment, food delivery, healthcare, communication and thousands of business services now operate through applications distributed primarily through two mobile ecosystems: Apple's iOS and Google's Android.
In Britain alone, the Competition and Markets Authority estimates that the app economy generates approximately 1.5% of UK GDP and supports around 400,000 jobs.
The CMA also describes the UK as Europe's largest app economy by both revenue and app developer count.
During 2025 and 2026, however, the rules underneath that economy began changing significantly.
For British founders, developers and businesses planning a mobile application, understanding what is happening now matters.
The UK's new digital markets competition regime came into force on 1 January 2025.
Under that regime, the CMA can designate companies as having Strategic Market Status, or SMS, where the relevant legal tests concerning substantial and entrenched market power and strategic significance are satisfied.
Following investigations, Apple and Google were formally designated with SMS in their respective mobile platforms on 22 October 2025.
The designation covers areas including mobile operating systems, native app distribution, mobile browsers and browser engines.
This does not mean the CMA found Apple or Google guilty of wrongdoing.
SMS designation instead gives the regulator the ability to consider targeted requirements designed to improve competition and the treatment of businesses and consumers.
Those interventions are now beginning to affect the environment in which UK applications are developed and distributed.
For an app company, being able to build a product is only part of the challenge.
It also has to reach users.
Apple's App Store and Google Play therefore perform an unusually powerful role in the commercial life of mobile applications.
Developers have historically raised concerns regarding issues including app review decisions, ranking, access to platform functionality and how platform operators use information they receive from developers.
On 1 April 2026, Apple and Google implemented commitments made voluntarily to the CMA covering aspects of these issues.
The commitments are intended to improve fairness, transparency and predictability around app review and app ranking.
The CMA has said the measures are designed to ensure reviews are carried out objectively and transparently, with clearer expectations around review times, explanations when applications are rejected, better notice when policies change and mechanisms through which developers can complain or appeal.
For businesses investing significant sums into an application, this increased certainty matters.
An app-store decision can affect an entire company's ability to reach its customers.
The Apple commitments go further in another important area: interoperability.
Third-party developers sometimes need access to operating-system features to create products capable of competing with functionality offered directly by the platform owner.
Under the commitments introduced in April 2026, developers can request interoperable access to certain features and functionality within Apple's operating systems through a more structured process.
The CMA is also examining areas including Near Field Communication access, digital wallets, connected devices and browser technology.
Its 2026 programme specifically references potential work concerning access to the NFC functionality used by digital wallets, connected-device interoperability and Apple's restriction on competing mobile browser engines.
These are technical issues, but they can have large commercial consequences.
Platform capabilities determine what third-party developers are physically able to build.
Greater interoperability can therefore create entirely new categories of applications.
Perhaps the most commercially significant issue concerns payments.
For years, app developers have had to design digital-business models around Apple and Google's platform payment rules.
The UK is now examining whether developers should have greater freedom to tell customers about ways to purchase outside the app-store payment environment — a practice generally known as steering.
On 30 June 2026, the CMA launched consultations on proposed conduct requirements for both Apple and Google.
The proposals are intended to remove restrictions that prevent or limit UK app developers from directing customers towards off-platform purchasing options. The CMA has also said that any fees imposed in connection with steering should be fair and reasonable under its proposed framework.
This point needs to be stated carefully.
As of 29 September 2026, the steering measures remain proposals in the latest CMA material available. The consultations closed on 28 July and responses were subsequently published in August. They should therefore not be treated as final rules already giving every UK developer unrestricted permission to bypass existing App Store or Google Play payment requirements.
Nevertheless, the direction of travel is important.
If final intervention materially increases developers' ability to communicate alternative payment methods, it could influence subscription models, pricing strategies, checkout design and the economics of many app businesses.
Payments should no longer be treated as something added shortly before launch.
They affect application architecture from the beginning.
A marketplace application may need split payments between customers and providers.
A subscription platform needs to understand the difference between digital purchases and payments for real-world goods or services.
A service marketplace might need to authorise a payment first and capture it later.
Some platforms need refunds, disputes or connected-account payouts.
Applications may also support Apple Pay, Google Pay and conventional cards alongside platform-specific purchasing mechanisms.
The correct approach depends on what the application sells, where the transaction occurs and which app-store rules apply.
That means commercial strategy, payment architecture and app-store compliance increasingly need to be considered together.
Another major development in app engineering has been the continued improvement of cross-platform technologies.
Businesses no longer necessarily need completely independent codebases for iPhone and Android applications.
Frameworks such as Flutter and React Native can allow significant parts of an application to be developed from a shared codebase while still delivering native mobile experiences.
That can reduce duplicated development and simplify maintenance.
It does not mean every application should automatically be cross-platform.
Applications requiring unusual hardware integrations, extremely high-performance graphics or deep operating-system functionality may benefit from more native development.
The important point is that the decision can now be made strategically rather than assuming two entirely separate applications are required from the beginning.
When people think about mobile-app development, they often picture screens.
The visible app is only one part of a modern platform.
Behind it may sit identity systems, databases, cloud infrastructure, payment providers, mapping systems, push notifications, analytics, administrative dashboards, AI services and numerous APIs.
For a transport or on-demand service application, for example, the interface may need to communicate with real-time location infrastructure.
A marketplace may require different applications or account experiences for customers and service providers.
A fintech application may need strict permissions, auditing and regulatory controls.
The quality of an application therefore depends heavily on architecture that users will never see.
Beautiful interface design cannot compensate for unreliable backend engineering.
Consumers increasingly expect applications to reflect what is happening immediately.
They expect to see a delivery moving across a map.
They expect messages to appear without refreshing.
They expect a payment status to change as soon as it is processed.
They expect notifications to arrive quickly.
They expect availability and prices to remain synchronised across devices.
Delivering this experience requires applications to move beyond the old model in which a device simply requests a static page from a server.
Modern systems may use real-time database subscriptions, WebSockets, location streams, background services, event queues and push-notification infrastructure.
These systems are significantly more powerful.
They also require considerably more careful engineering.
The next major application shift is the integration of artificial intelligence.
Instead of visiting a separate AI product, users increasingly encounter AI inside the applications they already use.
An e-commerce app can provide natural-language product discovery.
A legal or professional platform can analyse uploaded documents.
A business application can summarise activity across an account.
A support interface can understand a customer's situation before passing the conversation to a human.
Computer-vision models can interpret photographs.
Voice interfaces can turn spoken instructions into application actions.
This can make applications feel dramatically more intelligent, but it creates new requirements around data protection, model security, user permissions and the reliability of generated information.
AI therefore needs to be architected as part of the product rather than simply added as a chatbot window.
The UK Government already maintains a specific Code of Practice for app-store operators and app developers.
It establishes minimum security and privacy expectations, including the use of appropriate encryption and timely security updates. It also addresses third-party libraries and software development kits because vulnerabilities in external components can introduce vulnerabilities into applications themselves.
The wider Software Security Code of Practice adds further expectations around secure development frameworks, testing, supply-chain security and secure-by-design development.
This is particularly important for mobile applications because phones contain extraordinarily sensitive information.
Depending on permissions, an application can potentially interact with location information, photographs, contacts, cameras, microphones, payment systems and identity data.
Every permission therefore increases responsibility.
Good data protection is not simply a privacy policy placed on a website.
The software itself has to reflect the promises being made.
If an application says it collects location only during a particular process, its implementation should follow that behaviour.
If users can delete their accounts, the backend needs a genuine deletion process.
If different employee roles should see different customer information, the permission system has to enforce it technically.
If information is retained for a particular reason and period, the database architecture should support that retention policy.
This is sometimes described as privacy by design.
In practical development terms, it means legal and product requirements must eventually become code.
The modern app is increasingly not simply an app.
It can be the interface for an entire business.
Customers interact through one application.
Providers or operators may have another.
Employees manage operations through a web dashboard.
Payments move through connected financial infrastructure.
Support teams see customer activity through internal tools.
Location and events update in real time.
Notifications connect the different participants.
AI assists with repetitive operations.
Analytics help the business understand what is happening.
All of these components may ultimately belong to one digital platform.
This is why application development is moving closer to full software-platform engineering.
Britain already has one of Europe's most significant app economies.
The regulatory environment is now beginning to change around it.
Apple and Google have strategic market status. App-review and ranking commitments are already in place. Interoperability is receiving increased attention. Proposed steering requirements could affect how app businesses communicate payment options. Security expectations are becoming clearer.
At the same time, advances in AI, real-time infrastructure, cloud computing and cross-platform development are expanding what smaller teams can realistically build.
That combination creates considerable opportunity.
It also makes app development more sophisticated.
A serious mobile product now has to consider far more than how its screens look.
It requires product strategy, architecture, security, data, payments, integrations, scalability, store compliance and a clear understanding of the business operating behind the technology.
At Webmasters LDN, we approach app development as the creation of a complete digital product rather than simply a collection of mobile screens.
The applications that define the next generation of British technology companies will be those in which engineering, design and commercial strategy work together from the beginning.
And in 2026, the market around those applications is changing faster than it has in years.