Software-development tooling is difficult to rank because “popular” can mean several different things. A developer survey might measure which platforms people build for. A technology-detection service might measure which frameworks appear on live websites. A package registry might measure downloads. Those are all useful signals, but they are not interchangeable. For the UK, the clearest current evidence is split between two types of source: a UK Government app-developer survey that shows which device and app-store platforms developers target, and current BuiltWith detections that show which web technologies appear on UK websites. Keeping those two measures separate gives a much more honest picture than trying to force them into one artificial league table.
UK mobile development is heavily centred on the two major app stores
The UK Government App Developer Survey, published in December 2024, surveyed 600 app developers, 539 of whom were UK-based. It found that 76% developed for mobile devices, while 86% developed for laptops or desktops. That already shows how common multi-platform development is: many teams are not choosing one environment exclusively.
When asked about app-store destinations, 60% reported developing for Google Play and 59% for Apple’s App Store. Those figures are almost identical, which reflects the practical reality that many commercial mobile products need both Android and iOS coverage.
Other destinations were materially smaller: Microsoft Store at 29%, Amazon Appstore at 20%, Samsung Galaxy Store at 8%, PlayStation Store at 5%, LG Content Store at 4%, Samsung TV Smart Hub at 3% and Nintendo eShop at 3%.
The advantage for software houses is clarity. A client building a mainstream consumer mobile application will usually expect Android and iOS support because those are the dominant ecosystems. The disadvantage is duplication of effort. Supporting two major mobile platforms can increase testing, release-management and compatibility work.
Cross-platform frameworks can reduce some duplication, but the survey does not measure framework preference such as Flutter or React Native. It measures where developers publish or deploy applications. That distinction matters because an article claiming “60% use Android tools” would overstate what the survey actually says.
Platform choice affects cost, testing and release management
Developing for multiple mobile platforms creates commercial benefits and technical complexity at the same time. The benefit is reach. A business that supports both Google Play and Apple’s App Store can address a much larger share of the smartphone market than one that chooses only a single ecosystem.
The drawback is that each platform has its own review process, operating-system changes, device behaviours and policy requirements. Even when teams use a shared codebase, they still need to test real platform-specific behaviour around permissions, notifications, payments, accessibility and performance.
For clients, this means the cheapest initial build is not always the cheapest long-term product. A rushed cross-platform implementation can save time early but create difficult platform-specific bugs later. A fully native build may provide strong performance but require more specialist engineering effort.
Software houses should therefore explain the trade-off rather than selling one framework as universally superior. The right choice depends on product complexity, required device features, team skills, release cadence and expected lifespan.
There is also an operational issue after launch. Mobile applications need ongoing updates because the underlying platforms continue to change. A client should budget for maintenance, testing and store-compliance work rather than treating launch as the end of development.
Current UK web technology detections show a fragmented framework market
BuiltWith’s UK technology data provides a different kind of evidence. It scans live websites and records detected technologies. In the September 2026 dataset used for this research, Svelte appeared on 88,042 UK websites, Next.js on 87,696 and Vite on 86,360.
Other detected technologies included Tailwind CSS on 27,443 websites, Express on 26,618, Nuxt.js on 25,477, Ruby on Rails on 14,096, Laravel on 10,797 and Angular on 3,166. Ionic appeared on 2,901 websites. Firebase was also present in the broader framework dataset at more than ten thousand detections, although BuiltWith category totals can differ depending on how the technology is classified.
The important wording is “detected on UK websites”. These are not counts of individual developers. One developer can work on many websites, and one website can contain multiple technologies.
The advantage of detection data is that it reflects real deployed sites rather than stated preferences. The drawback is that detection can miss technologies, count legacy implementations and include sites where a framework is present only in part of the stack.
For buyers, the data shows that the web-development market is highly diverse. There is no single framework dominating every project. That diversity creates choice but makes supplier evaluation more important because two agencies can propose completely different technology stacks for the same business problem.
Popular tools are not automatically the right tools
Technology popularity can reduce project risk because widely used tools usually have larger communities, more documentation and a broader hiring pool. A framework with strong adoption may make it easier to recruit developers or find external support later.
That is a genuine advantage, particularly for business-critical systems expected to run for years. A client does not want to discover that only one person understands an obscure framework after the original supplier leaves.
However, popularity can also become lazy decision-making. A software house may recommend the framework its team already knows rather than the one that best fits the project. Trends change quickly, and a fashionable tool can create unnecessary complexity if the application itself is simple.
For example, a highly interactive application may benefit from a modern JavaScript framework, while a straightforward content site may not need a heavy client-side architecture. Likewise, a mobile app requiring deep device integration may justify native development, while another product may be perfectly suited to a shared cross-platform approach.
The disadvantage of chasing trends is maintenance churn. Businesses can end up rewriting systems because the team wants newer technology rather than because the software stopped meeting business needs.
Good engineering therefore starts with requirements and operational constraints, not with a popularity chart.
How UK businesses should choose a development platform
The strongest approach is to use popularity data as one input rather than as the decision. Buyers should ask whether the proposed platform fits their product, whether developers with the required skills are available, how the system will be hosted, how updates will be managed and how easy it will be to support after launch.
For mobile projects, the government survey shows that Android and iOS are the mainstream targets. That means most consumer products should at least consider both. The key question is whether to build separately or use a shared framework.
For web projects, BuiltWith shows a broad ecosystem rather than one winner. That makes architectural quality and maintainability more important than following whichever framework sits highest in a current detection table.
The advantage of established platforms is ecosystem depth. The disadvantage is that large ecosystems can encourage over-engineering and frequent tooling changes. Smaller or newer tools may be elegant and productive but carry greater hiring or support risk.
For software houses, the commercial lesson is to explain technology choices in business language. Clients need to understand cost, supportability, performance, security and team availability. They do not need a lecture on framework fashion.
The UK data therefore points to a practical conclusion: mobile development is concentrated around the major app-store ecosystems, while web development remains highly fragmented across modern frameworks and tooling. The best platform is not simply the most popular one. It is the one that solves the client’s problem without creating avoidable operational debt.
Sources: UK Government App Developer Survey; BuiltWith UK framework technology detections, September 2026.