You can now create PWA’s with Desktops. Would be great if Hype 4.x supports them too.
Yup! I need to investigate more, but it looks like we’ll be replacing the cache.manifest and home screen app buttons with PWA functionality for a future (post v4.0.0) release.
Perhaps this is something that be scripted, with Export Scripts.
I’m a bit skeptical of this technology though. I don’t trust Google. Are there any privacy issues here? Meanwhile, I don’t like Apple’s walled garden, so this is interesting.
It definitely could be, but will eventually be obsoleted by built-in support. Of course if there are special PWA needs that Hype’s generic version can’t solve or immediate needs then go for it .
PWAs aren’t a specific technology owned by anyone; it is a set of standardized web technologies that together can allow an OS to better present a page as a stand alone app. Hype will probably only be utilizing the offline (manifest/serviceworker) and home screen app portions to start.
Does this render apps obsolete? Does it render Wrapping obsolete?
Seems like the answer is yes.
…but it seems browser dependent. No?
I suppose then it matters which browser you choose to build the PWA, no?
This looks like a big change in the way the web works.
PWA don’t need to go necessarily through any “build” process… they are “just” a webpage with some additional Meta that allows the installation onto the home screen. Basically the feature “add to home screen” on Safari since back in the days but it has some more capabilities now (Workers etc.). Not many on iOS as Apple certainly sees this as a sort of side loading… more on Chrome/Android. But as always the smallest denominator with the biggest reach will rule the space hence Apple.
- Safari for the desktop doesn’t have a feature to convert a page to a “.app” application. Chrome 73 does though (I have not tried it yet).
- Wrapping makes an Xcode project right? In a simple case it may not be as needed, but in more complex cases where a user wants native app functionality around it or to sell via Mac App Store then Wrapping would still be useful.
Only to the same degree web pages are browser dependent.
This might be interesting for Hype…
…it leads here… https://preview.pwabuilder.com …so I chucked “Circles with Grandma” in there, to see what would happen.
Apparently, I’m missing a lot of stuff for a PWA. However, the website kinda works like a web based version of “Wrapping”. It even has the option to upload images…
…but that didn’t seem to work well for me, as not all of the images are square. But anyway, it had the option to download the project for different platforms…
This seems too complicated though. Apparently, all I need is a “manifest.json” file, a line in the HTML header and the icon image. This seems very scriptable with Hype. It seems possible that I could modify “Wrapping” to export a Hype project to PWA, but there are some problems…
…that’s a big problem. Heh, why bother working hard when Tumult is going to do the work?
Post 4.0? Interesting… that might be far away in the future enough to make the scripting project worth the effort. But then there’s this problem…
Offline mode is what I’d be looking to do. I’m not quite sure how to do this, especially since Hype is doing the “create offline application cache”. I’d kinda be fighting Hype… as I’d have to automatically edit the main HTML (kinda trivial though), prompt the user for PWA information (This is tedious, would be better if Hype had fields for this in the “Document” section and that information was available to the export script.), prompt the user for an app icon (again, would be better if part of the Hype project) and figure out the offline stuff.
I did see the “Service Worker” part on the PWA site. That seems to have something to do with setting up an offline mode.
Microsoft was nice enough to put this on GitHub… https://github.com/pwa-builder/PWABuilder …and that’s a pretty smart strategy actually. Google and Apple have a strong app store presence. If PWAs get popular enough, that could dramatically change landscape… and Hype could be a part of that.
I am never one to say don’t do something if it is an immediate need, but I would agree with the assessment that we’re the best ones to do it. The current technologies we use for home screen web apps are deprecated, so there’s not really a debate about us tackling it post 4.0.0.
Next level of PWA…