Earlier quoted context omitted.
Choosing the mobile website over the app is one way of keeping the relationship from going any further. A website can't ask you for your contact list like an app can.
http://www.w3.org/TR/contacts-api/ - but I get your point.
Goodbye, Native Mobile Apps
41–50 of 131 posts
Re: Goodbye, Native Mobile Apps
#42Earlier quoted context omitted.
While apps have more capability, the web can do pretty much anything you need with content and data. The only time you really need an app is for CPU-intensive work or accessing hardware.
> The only time you really need an app is for CPU-intensive work or accessing hardware. Or when you want to own your own data, or work offline…
Re: Goodbye, Native Mobile Apps
#43Earlier quoted context omitted.
The fact that you can choose no is precisely what makes the Web so good. The fact that you can block ads at all, that you can disable JS, that the Tor Browser bundle can be so simple to use, that you can easily get URLs to things, that you can copy text, are all huge benefits of the Web. Ever tried getting a URL to some Facebook content on mobile? The only way that I've found is to "Send as Message" (Facebook for And…
You can turn off push notifications for normal apps on Android, too.
Re: Goodbye, Native Mobile Apps
#44Icon on the home screen and finding the "app" on the store is what most users need (basically bookmarks).
Re: Goodbye, Native Mobile Apps
#45Re: Goodbye, Native Mobile Apps
#46I'd add that if you intend to maintain a web site then adding support for apps (presumably multiple since cross-platform is still hard) then you are throttling your bandwidth to actually improve features and stability. I'm thinking of certain food delivery app that had enough bugs on their Android app, then I fell back to their mobile site and haven't looked back. They could have saved themselves probably a few milli…
Re: Goodbye, Native Mobile Apps
#47Earlier quoted context omitted.
http://www.w3.org/TR/contacts-api/ - but I get your point.
That feature was designed but never built, so his point still stands. In my ideal world sites can do that stuff, they just have to ask, and users can always say no.
Re: Goodbye, Native Mobile Apps
#48The web is a great publishing medium for magazines and news outlets. Apps are for doing stuff beyond passive browsing.
While apps have more capability, the web can do pretty much anything you need with content and data. The only time you really need an app is for CPU-intensive work or accessing hardware.
Not on mobile. Due to serious, oft-encountered performance issues, the web remains crippled on mobile compared to native.
By "native" I'm referring to apps where the UI is rendered natively as opposed to being rendered in a `WebView`.
React Native is bending the rules here but it is important to note that it is divergent from the web platform and convergent with the native platforms.
Re: Goodbye, Native Mobile Apps
#49How do you deal with offline support? If I'm not connected and I want to read an article, where do I go? Can't open the website. Did you run metrics to find out how many people are going to miss offline?
Yes, there are a number of apps that cache some data locally, but I believe they're in the minority. Even casual games have to check in with a database and retrieve a couple datapoints about your progress, your in-app purchases, and what powerups are available to you.