A browser is already an app.
That obvious fact gets strangely easy to forget when a service decides the browser is no longer enough.
Facebook provided a clean example in 2016. People using Facebook’s mobile website could send and receive messages without installing Messenger. Then Facebook began disabling that capability for many mobile-web users and directing them to install the Messenger application instead.
Facebook is disabling messaging in its mobile web app to push people to Messenger
The task already worked
The important detail is not that Messenger existed.
Facebook had every reason to build a dedicated messaging app. Native applications can provide better notifications, camera integration, background behavior and richer features than a basic mobile website.
The issue is that users already had a functioning browser route.
Earlier, Facebook had removed messaging from its main iPhone and Android applications and pushed smartphone users toward Messenger. At that stage, mobile-web users were still able to message through the site.
Facebook Forces Users Worldwide To Download Messenger For Mobile Chat
By 2016, even that escape route was being narrowed. Facebook told TechCrunch that Messenger offered the “best experience,” while Messenger head David Marcus later said the company kept mobile-web messaging on some older devices with limited memory or network conditions.
Facebook isn’t entirely killing off the mobile web version of Messenger
That exception proves the burden was real enough to measure.
Installation changes the relationship
A website asks for a URL and a compatible browser.
A mandatory application can ask for storage space, operating-system compatibility, updates, permissions, notification access and a place on the device indefinitely.
For a person who uses Facebook messaging constantly, the trade may be trivial. For someone checking one message on an old phone, shared device or storage-starved handset, it is not.
The web’s great trick was supposed to be that the software could stay on the server. You did not need a separate executable for every business, newspaper, forum and conversation service you visited.
Mandatory apps partially reverse that bargain.
Better features do not require deleting the simpler path
There is a legitimate product argument for native apps. Facebook said Messenger users responded faster and the dedicated application made it easier to build a richer messaging ecosystem.
That explains why Facebook wanted people in Messenger.
It does not explain why the browser option had to disappear for capable devices.
Those are different decisions.
A service can offer a better app and let the web version remain boring. When the old path is deliberately blocked, installation stops being an upgrade choice and becomes an admission ticket.
The task did not become impossible in a browser.
The platform decided the browser was no longer where it wanted the task to happen.