3 ms·
I agree with you, particularly when the stuff could just be a simple HTML page or collection of pages (e.g. transportation schedules: those were just sheets of
by zeveb 11y ago
I agree with you, particularly when the stuff could just be a simple HTML page or collection of pages (e.g. transportation schedules: those were just sheets of paper recently: why should I need a mobile app or a webapp to read a schedule?).
But I also hate when something which should be a native app is instead a JavaScriptified webapp.
- TeMPOraL 11y agoThere are things that should be apps, and things that shouldn't. The line is blurry, but there are few rules of thumb: - If it can be done off-line, it should be done off-line; hence, an app. Example: public transportation: you shouldn't need an Internet connection to check bus schedules or find a route through your city. Transportation schedules update infrequently, so they should be cached. - If it's just browsing on-line content, it probably should be a website. - If performance matters, it should be native (unless you're writing a game or specialized software, performance probably doesn't matter). - If you're just repackaging your website as an app because apps are hot, please don't do it at all. Sadly, IT reached the state where customer's interest and company's interest are seriously at odds with each other, and so we have a proliferation of bullshit apps that exist only to destroy the interoperable nature of technology in order to capture ad money.
- taf2 11y agoThe articles point to your first point is the web and the browser platform provides the tools you should need but apple is not implementing the features into safari required - service workers - webrtc - app manifest