I’m not sure there’s any explanation other than more ad/data revenue.
Are there apps that give superior experience than web sites nowadays? Even not accounting for privacy, the apps are generally just shittier with less functionality.
I used to give the Google apps as examples of apps being better, but the gmail app is more buggy than just using gmail in a mobile browser, not to mention the integrated phone mail app.
Similar, there’s quite a few chat/video apps and games where apps make sense. And none of them prompted me to download the app or show lies like “better in our app” crap.
If you can simulate 5 different phones it won`t matter if someone gets their spyware onto one of them.
But it is always better to address the root cause of the problem. This often means a policy or legal issue rather than a technical, but has the advantage of not becoming a whack-a-mole technical race.
The IMDB app is far better (to me) than the dumpster-fire that has become their website. Other than that, I agree with the sentiment that most apps for websites are not worthwhile to install.
Funny, to me the IMDB app is the perfect example of a dumpster-fire app, with every 3rd tap/action resulting in an “invitation” to sign up for an account.
I use a text-only browser and write simple command line "apps" (scripts) to retrieve text from sites like IMDB. It works very well. Opening pages on these sites in a "modern" web browser is an entirely different experience. We cannot ignore the complicity of the "modern" web browser in degrading the "user experience" in cases like this one.
I can see why GPS based apps, or camera apps with filters, or networking apps 'need' to be installed apps (I don't know if an easy way to do GPS through a browser; speed and fast access to storage) ... but Amazon, Reddit, newspapers, ... what am I gaining?
Genuine question as a one time web dev I've always considered web sites written as an app, shipped with a browser, to be a negative. What am I missing out on?
For example, I worked on a rich text editor, and we wanted to put a bar with text formatting tools above the touch keyboard. This is not possible in the browser: your webapp cannot measure the keyboard or the remaining available viewport (and the keyboard's size depends on the input method and the iPhone model).
Another example I experienced is when we wanted to have full-screen dialogs with buttons at the bottom. If you do that, then the users have to tap your buttons twice, because the first tap only expands Safari's browser UI, and your buttons near the bottom of the screen only work while that UI is expanded.
I haven't made an app (don't know how!) and I definitely wouldn't add a "download our app or else!" banner/wall, but I've been extremely surprised from the other side of the table to see just how many users seemingly just want an app for an app's sake, even if it's functionally no different from a responsive mobile view.
Freelancers are cheap if you hire from poor countries.
Things like weather (with or without current coarse location), sports scores, headline news benefit from up to the minute data fetches, but older data is still useful.
For communication apps, often people would like notifications on inbound messages, so that can fit with web push apis to get data; but if you don't want notifications, you can't consistently make messages available to read offline.
1) Shortcut on the homescreen by simply tapping 1 button(install) instead of hoping that the user will somehow remember you. WebApp shortcuts are quite involved.
2) Sign in once with a forever session. I hate apps where I need to sign in again because having an App is a great opportunity to have one time sign in that runs through generations of phone upgrades. Even better, the sign in doesn't have to involve the user, the data will be there and not accidentally deleted which means that the presence of the app is as good as username and password.
3) Immersive experience means better user experience. The UI becomes part of the Phone's UI instead of another App's UI's sub UI. A well designed app is very effective. I haven't seen a well designed mobile Web App, Web is great for websites and "possible to do" Mobile Web Apps.
4) Smaller download sizes, faster launches. A website would usually download a few MB of scripts and images, an App without bloated frameworks would be easily around that size and will download it only once. It will be ready to use in less than 0.5s every time.
5) Any advanced stuff is done much better natively even if it is possible to do through the browser. This is because the browser put extra boundaries around the boundaries that has due to the OS boundaries.
I am as cynical about forcing apps down user's throats as anyone (Reddit, I'm looking at you), but the downvotes are a bit too much when this is a perfectly reasonable point, no?
Some cases for apps are perfectly legitimate, maybe the access to the phone APIs and the native experience is much better for a given product or service. I'm a firm believer in PWAs but as it stands I really prefer Uber or delivery apps to be native.
I really hope the people downvoting the parent comment are not the same people who are staunchly against web apps, though I suspect there will be some intersection. We can't have web apps, but we can't have native apps either... What can we have then, Geocities and MySpace?
The expectation is 'everyone wants you to use their app so they can track and advertise better' and the parent basically said 'nuh-uh'. We need more to be able to consider it substantive and benefiting the conversation, IMO.
and it is possible to do it with apps if we shift to apps being a service for the user, rather than a service for the developers sponsors
