4 ms·
> Interestingly, Microsoft added a similar feature to IE4, and deprecated it as of IE9. The idea didn’t catch on because back then nobody wanted to emulate nati
by ForHackernews 11y ago
> Interestingly, Microsoft added a similar feature to IE4, and deprecated it as of IE9. The idea didn’t catch on because back then nobody wanted to emulate native apps (which didn’t exist), and therefore nobody particularly cared if the users had to briefly wait for the next page.
> native apps (which didn’t exist)
Does this writer believe that nobody installed software on their computers before the iOS app store opened in 2008?
- scholia 11y agoThe usual meaning is "native apps" for smartphones, as opposed to traditional programs like PhotoShop and AutoCAD. It's a broadbrush description but almost everybody gets it. Would you like to offer a simpler, shorter and more accurate way of making this distinction?
- ForHackernews 11y agoI think it's a silly distinction to make. Native applications (meaning software running on a computer, outside a browser sandbox) have always offered a smoother, more comprehensive user experience. That doesn't mean users get no value from the web, or that they're so spoiled by fast transitions in Microsoft Word that they won't want to use a website.
- scholia 11y agoI agree, but that's not the point. The point is that some -- perhaps many -- people want to distinguish between smartphone apps and traditional programs, and that's one way to do it. It would be nice if there was a better way, but I don't know of one. Incidentally, it's a distinction that people also make between "universal apps" (written for Windows Runtime) and desktop programs (written to the Win32 API) even when they do the same job on the same Windows 8 or Windows 10 PC.
- bztzt 11y agoThe meaningful difference is whether there are isolation and distribution/update mechanisms so that users can install and maintain apps with less risk and hassle. This doesn't have much to do with (in-app) UI per se, though.