4 ms·

> Companies are seeing this switch, so they adapt. You’re confusing cause and effect here. Companies are pushing apps very hard because it gives them a lot mo

by jmull 6mo ago

> Companies are seeing this switch, so they adapt. You’re confusing cause and effect here. Companies are pushing apps very hard because it gives them a lot more ability to wield their various revenue enhancing dark patterns. That kids see apps as the primary option is a corporate success metric, not an organic choice. Anyway, the premise that “phone screen ==> native app not web app” is rather faulty, is it not?

Klonoar 6mo ago
They’re not confusing anything, you’re just sticking your head in the sand. The modern entry path to “computing” is small screen devices (phones). Their point of newcomers not having our same entry path is accurate. This is organic, however much we don’t like it. Anything past that is just market skating where the puck is.
- aziaziazi 6mo ago
  I think they mean that a webapp is necessary desktop-first. Many websites/webapps are mobile-first. It resonate with me as I’m used to try new services on a (mobile) browser if available and switch to an app only if necessary. > the premise that “phone screen ==> native app not web app” is rather faulty, is it not?
- array_key_first 6mo ago
  Okay but that's not what he's arguing, you're missing the point. There's nothing stopping a website from being usable on a smartphone. In fact, almost all of these apps are just websites in disguise! They use web views to render. The reason it's an app and not a website isn't because apps are better for smartphones. It's because apps are native code running. It's also a choice that websites cannot present as apps (PWAs). Apple and Google purposefully did that so they can push users to apps instead of websites, for data farming purposes.
- jmull 6mo ago
  We're talking about web app vs native app here, not big screen vs small screen. Obviously, you can have either kind of app on either size of screen, so small screen first doesn't mean native apps. It's enshitification that's driving native adoption, not small screens.

by jmull 6mo ago

Klonoar 6mo ago

They’re not confusing anything, you’re just sticking your head in the sand. The modern entry path to “computing” is small screen devices (phones). Their point of newcomers not having our same entry path is accurate. This is organic, however much we don’t like it. Anything past that is just market skating where the puck is.

aziaziazi 6mo ago
I think they mean that a webapp is necessary desktop-first. Many websites/webapps are mobile-first. It resonate with me as I’m used to try new services on a (mobile) browser if available and switch to an app only if necessary. > the premise that “phone screen ==> native app not web app” is rather faulty, is it not?
array_key_first 6mo ago
Okay but that's not what he's arguing, you're missing the point. There's nothing stopping a website from being usable on a smartphone. In fact, almost all of these apps are just websites in disguise! They use web views to render. The reason it's an app and not a website isn't because apps are better for smartphones. It's because apps are native code running. It's also a choice that websites cannot present as apps (PWAs). Apple and Google purposefully did that so they can push users to apps instead of websites, for data farming purposes.
jmull 6mo ago
We're talking about web app vs native app here, not big screen vs small screen. Obviously, you can have either kind of app on either size of screen, so small screen first doesn't mean native apps. It's enshitification that's driving native adoption, not small screens.