upvote
> We take tech literacy for granted, because it's like a dozen levels down fundamental to our entire field. But the tech illiterati exist, and they love apps.

They "love apps" because apple and android have spent billions to break their mental models and convince them that "you use apps to do things on your phone". Literally. That's the extent of most people's understanding.

So, sure, they "want" apps in the same sense that early internet users "wanted" AOL because in their minds AOL and the internet were indistinguishable. But actual free choice requires an understanding of the choices.

reply
This doesn’t really make sense. Apps were pretty popular immediately after decades of web usage. There are many reasons to prefer an app. Even on desktop; if I’m using a service enough throughout the day, I want a native app, not a website.
reply
There are many reasons to prefer an app, most of which are ways OS makers have crippled web apps for reasons that TOTALLY HAVE NOTHING TO DO with the fact that they get a 30% cut if the user chooses the native app.
reply
Web sites optimized for mobile weren't really a thing when the iPhone launched. That's why apps shined on smart phones. Web designers did eventually catch up with the <meta-viewport> hack but the trend towards apps was already too established at that point and people thought that you need an app to use a service.
reply
That is a great analogy! I still remember the day my cousin explained that there was a whole internet outside of AOL…
reply
When I say I want an app that implies a few things:

- this isn't a one-off use, I don't want an app to pay parking meter once and never use it again.

- it's an app and not a WebView pretending to be native

- it's native and not react-wanna-be-native

- you know how to make an app

I have to use this app to open a parcel locker and every time I launch it I have to wait for "downloading bundle". It's probably the easiest kind of app to make and yet somehow they made it worse then a website.

reply
End users don't care about if it's an app or not.

What they care about:

- Does it do what I need it to

- Can I access it easily

- Is it easy to navigate

- Does it work or is it buggy

- Is it slow

- Does it abuse notifications

- Is it prompting me to log in all the time

- Are there too many ads

- Can I use it on any device I have

- Does it complain about updating constantly

I don't think any of those actually has to do with being a website. The problem is that web browsers and websites didn't get a not-stupid UI for phones faster than the phone vendors could funnel everyone into their walled garden. Remember "click here for mobile" and having to develop two web interfaces? And half the time functions would be missing on one side?

reply
That sounds less like wanting apps, than simply having no idea what's going on.
reply
Most of the users of phones seem to operate on the no idea what's going on model. It's on developers to meet them where they are at, and if that's the app store you better be there for them.
reply
Agreed, you never insult or complain about the customer you only address their issues
reply
Honestly, they probably would have been perfectly happy with a bookmark on their home screen, but have you ever tried walking someone who doesn't know how to enter a url into their browser through the process of making a home page bookmark on their phone?

Ultimately I ended up making a PWA that does nothing except act as a bookmark. Which was way more of a PITA than it should have been.

reply
>Ultimately I ended up making a PWA that does nothing except act as a bookmark.

Which is exactly what I was going to reply to your original post.

I am willing to bet 80-90% of user don't want / need / care if it is an Native app. They simply want the website / PWA bookmark icon on their App Screen selection.

The problem right now is the experienced of getting a PWA on to an App screen is not user friendly or in someway user hostile because it goes against the fundamental service revenue of their App Store model.

reply
Sounds like what could be a useful built-in OS feature. Along the lines of:

"Aim camera at QR code to put "open-link" icon on your home screen"

Does something like that not exist?

reply
It could, right? But let me tell you a secret: Apple doesn't want PWAs/web apps and actively limits Safari to force developers to build apps.
reply
Devs can pretty easily implement this on their site using the BeforeInstallPromptEvent.prompt method.

https://developer.mozilla.org/en-US/docs/Web/Progressive_web...

Though of course...

> This is not supported on iOS.

reply
I really wish PWAs were more well-known among average users. If people knew and expected they could install certain websites as apps, that would simplify things so much and really balance the power of the app stores.
reply
My problem with PWA, is that it usually completely ruins the multiple tabs/windows of the same app/data
reply
On desktop or on mobile?

On mobile it's rare for apps other than web browsers to allow multiple tabs/windows and the ones that do (Ex: Gmail allows a draft to be a second window) have many multi window related bugs.

reply
It's not well known because it's annoying to install ... and it's annoying to install because the stores are huge cash printing machines so that's not going to change.
reply
It's not that hard to install. The website can just have a button you click to trigger an install prompt: https://developer.mozilla.org/en-US/docs/Web/Progressive_web...

But of course...

> This is not supported on iOS.

reply
Unfortunately apple accomplished their goal of killing that entire idea. The time for it to take off was 10 years ago. They begrudgingly support it now but it's too late. gg
reply
If pinning website bookmarks was more prominently advertised in the UI, they would be fine with it I guess. Though it would need some more changes.

Why do people like apps? Because they can put it on their home screen, they can open the app list and pick from there, they are searchable in a canonical repository, which is kind of like googling for the website but still.

Login flows are simpler and persist better, with local storage etc.

Multiple apps can be switched between by just moving between the currently opened apps, while website tabs appear inside the browser only and are mixed with many other unrelated browsing tabs, making it harder to find.

I guess fundamentally all of these could be supported with browsers. But in the end, Google and Apple don't want to make bookmarks and independent persistent "browser windows" easier.

reply
I think you're right, but I think it's also because the industry trained everyone on this model. I remember ~ 2010-2012 there was a big push to make everything an app. As far as I can tell the only benefit to users is a nice icon on the home page, and the benefit for the company is.. exfiltrating data from the users phone?
reply
As not a web dev, out of curiosity: What would be the drawback or problem with showing a header or pop-up on mobile browsers, offering to install them as (web)app? Then using the PWA functionality of the browser to do it.

I'm not a heavy user of those but the result of PWAs has always been an icon that's handled by the OS like if it was any other native app, and when opened it just behaves like the web browser in kiosk mode just for that website.

reply
FTA

> I can’t understand how we got to this place with “app culture”

> Nobody here is talking about the fact that a significant number of users want apps, too.

End users, for the most part don't know what they want. They take when makes sense to them. To end users apps are easy. To us, a URL is easy.

> But the tech illiterati exist, and they love apps.

Yup!! And we get sucked into this vortex at times. Good post btw.

reply
If the app store allowed you to install bookmarks, I doubt most people would notice.
reply
The Google Play store did (maybe still does?) allow installing some PWAs advertised as light versions of the apps.
reply
It does. It's called a PWA.
reply
That is not an App Store functionality, that is a Safari functionality
reply
When I announced the update, the number of people who asked me variations of "how to get website on phone if website on computer" or requested I make the damn thing an app was outrageous.

I had a similar experience. It was mostly lower- and middle-managers who needed to put their mark on something visible.

I responded with, "Tell me what features you want the app to have that the web site doesn't; or is this a vanity project?" The "vanity project" line is what made people re-think what they were asking.

When that didn't work, I pointed out that they'd have to hire an entire new team to do the app, and gave them a high six-figure number to accomplish what they wanted.† That always worked.

† For a number of regulatory and political reasons, we cannot offshore for cheap.

reply
On iOS, I think the only two reasons to have an app are: notifications and access to contacts.
reply
Rich widgets on the Home Screen are valuable too. As a web developer, I wish I were able to make widgets for people to put on their Home Screen to perform certain actions in less clicks, or have information from my (web) apps easily viewable at a glance. Which I know they would want. Right now, as far as I’m aware, for me to do that in iOS (and possibly Android) is to build those in native land.
reply
Okay I guess? So then you politely answer to them the “app” is their web browser of choice! Problem solved
reply