News for hackers. Stuff that matters.
Re:Chrome DevTools in 2016 and Beyond by pfooti on Friday June 10, 2016 @06:37PM (#11880680)
Generally, a "progressive web app" is something that behaves a bit like a regular native app, when the browser supports it and user allows it. This includes using serviceworkers to cache data for offline (and low bandwidth) use, making a home-screen icon that launches a standalone (from the task switcher perspective) window with no browser frame, and so on.
Re:Chrome DevTools in 2016 and Beyond by lucb1e on Friday June 10, 2016 @06:46PM (#11880746)
Pretty much what I thought, thanks!

I'm a fan of the concept, hating apps that could easily have been webpages (public transport apps are often a good example), so it sounds like a good idea to give this a name and promote it. It's too bad that this name sounds like Microsoft came up with it in the early 2000s, but oh well.

Re:Chrome DevTools in 2016 and Beyond by sotojuan on Friday June 10, 2016 @07:52PM (#11881123)
It's an awesome idea and one that is actually not too hard to implement, at least partially. Problem is browser support of the APIs, with Safari lagging behind.
Re:Chrome DevTools in 2016 and Beyond by pfooti on Friday June 10, 2016 @08:28PM (#11881280)
Yah, the tricky bit is safari access. I'd love to put a bunch of time into using service workers, push notifications, and so on to make an app-like experience for my users (it's a forum / social network thingy for teachers), but mobile safari really puts a crimp in those plans. Instead I have my own homegrown cache and other hairy tricks that are nonstandard, but work on safari.
Re:Chrome DevTools in 2016 and Beyond by woah on Saturday June 11, 2016 @04:15PM (#11885135)
It's a laundry list of enhancements that are usually not in any way critical to business and product requirements, and whose absence will likely not be noticed by many users. Great to have and I support the idea 100%, but this stuff is usually the first to get cut when launch is looming, and for good reason.