5 ms·
This is well done, but it proves to me that we are not there yet with javascript really replacing mobile apps, even on a such a simple app: When you click on a
by csantini 10y ago
This is well done, but it proves to me that we are not there yet with javascript really replacing mobile apps, even on a such a simple app:
When you click on a news and then you go back to the ng2 app it takes more than a second to load back the js code when compared to any native HN app.
This is a big limitation for a news reader: of course the javascript app cannot stay in memory when you leave the page and then come back to it.
- grav 10y agoWhy can't it? What's keeping the browser from caching it?
- codingdave 10y agoThat sounds more like a UX flaw in the app than something wrong with JS. Why would a newsreader close itself when you actually read the news? It makes more sense to open articles in a new tab (or whatever your specific device does), and leave the reader open, avoiding this problem. That is a fairly universal mechanism anymore when working from a page/app acting as a content hub.