Cross-platform development is easier to understand when app counts are treated as evidence of incentives, not merely as a scoreboard of technical effort.
This archive note examines the installable applications made by three major platform companies for the major mobile and desktop operating systems of its period. The comparison excludes applications bundled with devices, and it uses app counts as an illustrative measure rather than a complete account of a company’s software presence.
The central pattern was clear: each company’s distribution choices reflected the way it made money. Hardware-led businesses concentrated on their own ecosystems; advertising-led services followed reachable audiences; and a company rebuilding its services strategy had reason to be present almost everywhere.
Start with the overall pattern
The original comparison grouped applications by the company that made them and the operating system on which they were available. Mobile and desktop systems were separated because the development and commercial choices were materially different. A web service could often reach a desktop browser without a dedicated native application, while mobile platforms increasingly depended on dedicated apps.
| Company | Primary incentive | Typical distribution pattern |
|---|---|---|
| Apple | Device and ecosystem value | Strong concentration on its own platforms, with selected support for Windows users. |
| Service reach and advertising audience | Broad availability where large user audiences could be reached. | |
| Microsoft | Software, services, and enterprise reach | Significant development on its own systems and expanding availability on rival mobile platforms. |
Apple: selective distribution
Apple’s approach was consistent with a device-centered ecosystem. Its applications were concentrated on Apple platforms, while the limited Windows selection supported services important to people who used an iPhone or iPad alongside a PC. Media playback, device synchronization, and cloud access created practical reasons for those exceptions.
The key point is not that cross-platform work was absent. Rather, it was usually justified by its ability to improve the value of Apple devices and services. This helped explain why Apple had comparatively little reason to build broad application portfolios for competing mobile platforms.
Google: reach the largest audiences
Google’s incentives were different. Its major services benefited from being used widely, so access to large audiences mattered more than maintaining platform exclusivity. That made iOS an important destination for Google applications even though it was operated by a direct platform rival.
Desktop support followed a different pattern. Many Google services worked effectively in the browser, reducing the case for native desktop applications. Where native software appeared, it tended to support specific workflows such as storage, imagery, or mapping rather than create a complete desktop app catalogue.
What an app count cannot tell you
Counts do not measure quality, engagement, maintenance costs, browser alternatives, or the commercial importance of a particular service. They are best read as a directional clue alongside each company’s broader product and revenue strategy.
Microsoft: a broader cross-platform push
Microsoft showed the broadest distribution pattern in this comparison. It maintained extensive portfolios for its own platforms while expanding applications and services on iOS and Android. Productivity tools, information services, and consumer applications increasingly had reasons to meet users on the devices they had already chosen.
That shift did not begin in a single moment, but the pace and visibility of new releases made the strategy more apparent. A cross-platform presence could extend the reach of Office and other services even when it did not directly strengthen the position of Windows or Windows Phone.
Why the least-served platforms mattered
The comparison also showed how difficult it was for smaller platforms to attract third-party investment. A platform with a limited installed base had to overcome the engineering cost of development, ongoing support, testing, distribution, and the opportunity cost of not investing in a larger audience.
For companies whose services depended on scale, the decision often came down to the likely reach of the application. That did not make every absence a strategic signal; it was also a practical response to scarce product resources and changing user demand.
The broader lesson remains durable: when users gather on platforms controlled by others, service companies may need to follow them. Platform strategy is therefore as much a question of economics and audience access as it is of software capability.