Seriously. I don’t want to install something on my phone when the dev is just using a WebView, if that’s what it’s called. When the app is basically just a website with the browser hidden.
What’s the reason for that? To attach the customer? To sell the app for money? Is there more ad revenue that way? Do you reach more people?
(Are there any good reasons for it, too? Security, maybe?)
You must log in or register to comment.
deleted by creator
Firefox Focus on Android sounds right up your alley.
If they have an app they can gather far more personal data from you (and your device) that they can then turn around and sell
And far fewer people have adblockers that block ads in apps.
This exactly. Just ask for some location rights in the app and get access to wifi also.
Most users don’t mind giving an app a large amount of access and in doing so, a lot of personal information gets exposed.
If you have a choice, use a website.
Also it adds a link to their website right on your phone.
This is why I love kbin. No nonsense apps just a PWA that works splendidly. Now I don’t need a mastodon or lemmy app! It’s all here!
FWIW, I’ve been using lemmy in a browser exclusively, not even a PWA and it works fine.
I’m not aware of a PWA implementation that supports multiple tabs either.
Besides the other mentioned reasons: exposure through the app store can be a motivator too.
Some people are missing the forest for the trees here
Having a businesses app on your phone is better regular advertising than anything they could ever pay for.
They just want an excuse to make you look at their logo and think about their business as regularly as possible
This is true
people tend to develop liking or disliking for things merely because they are familiar with them
and it’s amazing that basic psychological principles have been decoupled from mainstream awareness of marketing tactics (obviously intentionally).
The infamous manipulation trick when you ask someone for the time then you ask them what you really wanted
I’m sure there are some “data harvesting” reasons, but honestly, the simplest is likely the truest:
Most people aren’t computer-savvy, and having an app is much easier for most users than going to a website (either directly or through a bookmark that they probably won’t ever be able to find again).
One must remember, always and forever: most people aren’t us/you. Just because something is easy for you to do doesn’t mean it’s easy for everyone else.
Is it dumb for me that T-Mobile has an app that just goes to a webview that I could get through my phone browser? Yes. Is it dumb for my parents? Absolutely ten thousand percent no.
The value (in terms of money made/saved/protected) that a company gets from having an app instead of a website only is probably ranked in this order:
1 - ease of use for the majority of customers, reducing tech and customer support calls, angry customers, lost goodwill, bad reputation
2-99 - same as #1
100 - data harvestingI want apps to be apps again.
On my desktop I have browser tabs for WhatsApp, messenger, Skype, gMailChatTalkHangouts and slack. I know slack’s app was ass but I miss the rest.
I want a discrete app that doesn’t crash with chrome and which sits in my tooltray so I don’t have to fucking search for it whenever something makes a noise (ctrl-alt-a). I want to see it from the blink in the corner and not by scanning 31 windows of 7 groups of 12 tabs each.
Often times I just give up and hope it also makes my phone spork too so I can grab it there.
Progressive Web Apps were supposed to marry these schools of thought, but maybe we hoped for too much because it’s still
garbageChromium under the hood.Just make everything for maximum interoperability I guess? I recently saw and forgot the name of a system for creating and displaying Github-like pull requests and associated discussions that are sent in via email. A very simple web interface displaying plain-text that could reasonably have been extended any way you like. I am beginning to see the appeal of the plain-text revolution.
I would say in some cases, people are conditioned now to expect an app, even if it’s basically a website. I think in a mobile context, most non-techy people don’t normally think to open up a browser and say, browse Amazon or something. Instead they go for the Amazon app on their phone, and browse/shop/whatever there.
I wouldn’t say this is exclusive to phones either. I once worked on a product that was essentially web-native, but they had to ship a desktop app because their market expected it, even though it was only a web-view wrapper to the website. No offline storage, no difference in behaviour, or need for some specific API; nothing. I guess you try explaining to boomers that a web-view desktop app is unnecessary.
The data vacuuming and additional marketing are just added benefits for the app developer, if they go down that path (they usually do).
I always assumed the reason was to get more tendrils into your phone for that sweet sweet data $$$ and allowing themselves more control over shoving notifications in your face.
Do I sound bitter?
because ios severly limits what you can do with websites and pwas like notifications…
We had a project once that ran completely fine as a website except for the ability to scan bar codes. That one thing forced us to create an app and the rest of the app was just showing the website.
Ad revenue. It is harder to block ads on mobile than it is on desktop.
So they can make your phone go bingedybeep and show you more adverts, while slurping up any data the browser doesn’t usually let them access.
I built an app like that. It uses a WebView, although all the HTML is self-contained and it only accesses the internet to make API calls.
Mobile app development really sucks, as a developer. The frameworks, the build tools, the specialised languages that can’t be used anywhere else - it’s a hot mess. Making an ‘app’ using that method is much quicker and easier for me because I get to use HTML, CSS and JavaScript, which I already know and have the tools for.
But why make it at all? If you want to use HTML, CSS and JavaScript you can do that, and not even have to build and deliver the pointless box that you put the content in, because everybody has Safari, Chrome, or another browser on their device.
Yes, I have built it as a website app also and that is the primary UI. The mobile app is just a read-only viewer for quick access to the information people need on the go. It’s not entirely pointless.
A lot of people don’t know how to install a PWA (which I also provide, if they want it) and have never done so. They also just expect there to be an app in the app store and when they hear about a tool someone else is using that’s their first port of call.
This is definitely part of it. The company I work for sells a service to companies, that their employees need to use. We built a web app, it works perfectly fine. However, people ask for ‘an app’ because they want to install it from their phone’s app store instead of opening the website once through a link in their email and creating a bookmark.
So we added a PWA manifest and clear instructions on how to ‘install’ our web app (it’s literally the same thing otherwise, no added functionality). Yet the users still complain that they want an app…
