Very interesting. Whosever wrote the codes and supporting this mechanism, "https://travelbound.api.vamoos.com/api/itineraries/{username...". I would run away from that person as far as I can. :)
Your 'app' could have been a webpage (so I fixed it for you)
471–480 of 571 posts
Re: Your 'app' could have been a webpage (so I fixed it for you)
#472Earlier quoted context omitted.
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.
One important which is not included: web apps are resource hogs
Electron and React apps, perhaps.
It's completely feasible to build a webapp that is lightweight. I have done it several times.
Re: Your 'app' could have been a webpage (so I fixed it for you)
#473Very interesting. Whoever wrote codes and design this mechanism, "https://travelbound.api.vamoos.com/api/itineraries/{username...". I would stay far away from that person as possible. :)
Re: Your 'app' could have been a webpage (so I fixed it for you)
#474Earlier quoted context omitted.
At this point, most of those "native" apps are actually just web apps packaged in Electron. The fact that you generally can't tell the difference is proof that there aren't any real reasons to prefer a native app. All the reasons have to do with either OS vendors trying to hobble PWAs, or web developers creating React monsters for no good reason. Web apps can actually be very performant.
The real reason is really simple tho, and we could identify it ahead of time even before apps existed: The average users sucks at managing bookmarks. Telling a user that a feature is a webpage instead of an app means that they, in their glorious tech illiterate brain, think they have to memorize the url. They don't want to do that. They want to "have it" so they don't forget it. And having it is easier in the app men…
This is trivially solvable with a good mobile OS level feature to create phone desktop icons from websites.
Of course, Apple and Google will never do such a thing when their cut of app sales is ~$100bn globally.
Re: Your 'app' could have been a webpage (so I fixed it for you)
#475Earlier quoted context omitted.
The real reason is really simple tho, and we could identify it ahead of time even before apps existed: The average users sucks at managing bookmarks. Telling a user that a feature is a webpage instead of an app means that they, in their glorious tech illiterate brain, think they have to memorize the url. They don't want to do that. They want to "have it" so they don't forget it. And having it is easier in the app men…
This is trivially solvable with a good mobile OS level feature to create phone desktop icons from websites. Of course, Apple and Google will never do such a thing when their cut of app sales is ~$100bn globally.
I just tried and it looks like I can do this in Chrome on Android relatively easily. The UI could be a lot nicer for it though.
And I did run into an issue where if the site allows me to install it as a PWA, Chrome will want to do that and won't want to bookmark a specific page on that site instead.
Also, maybe your point was that this could be done at the OS level rather than the browser, which is fair.
Re: Your 'app' could have been a webpage (so I fixed it for you)
#476Nobody here is talking about the fact that a significant number of users want apps, too. I'm responsible for an internal tool at the company I work for, hosted as a website, that handles a bunch of miscellaneous tasks that other employees need. Think reimbursements, documentation and reporting, gathering and presenting business data. That sort of thing. When I took it over, it was desktop only ( a lot of formatted pa…
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…
But take parents example. What is it you want the app version to do that a decent website can’t do?
Re: Your 'app' could have been a webpage (so I fixed it for you)
#477Nobody here is talking about the fact that a significant number of users want apps, too. I'm responsible for an internal tool at the company I work for, hosted as a website, that handles a bunch of miscellaneous tasks that other employees need. Think reimbursements, documentation and reporting, gathering and presenting business data. That sort of thing. When I took it over, it was desktop only ( a lot of formatted pa…
> 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 sen…
My take is that they love apps for the simple reason they show as easily clickable buttons to enter. Most dread having to type a Web address for something they regularly do. Few know that they can create an "app-icon" from any Web page. Should be advertised more.
Re: Your 'app' could have been a webpage (so I fixed it for you)
#478Nice. Would someone please port the Waymo and Uber apps to web sites?
And put them on F-Droid? Thank you.
Re: Your 'app' could have been a webpage (so I fixed it for you)
#479Earlier quoted context omitted.
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.
One important which is not included: web apps are resource hogs
[deleted]
Re: Your 'app' could have been a webpage (so I fixed it for you)
#480Nobody here is talking about the fact that a significant number of users want apps, too. I'm responsible for an internal tool at the company I work for, hosted as a website, that handles a bunch of miscellaneous tasks that other employees need. Think reimbursements, documentation and reporting, gathering and presenting business data. That sort of thing. When I took it over, it was desktop only ( a lot of formatted pa…
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…
[deleted]