NOtherDev

Yes, this is also the process we're taking on and it seems pretty complex for me. But anyway, flatfile.io is probably answering my all question best. Thanks for sharing!

This is a great article focusing on the same new possibilities I wanted to cover creating What Web Can Do Today (https://whatwebcando.today). The gap between native apps and the web exists and probably will exist, especially until Apple's strategy doesn't change dramatically, but that's quite unlikely now.

The set of APIs available is quite broad, though, not limited to what was mentioned here, and growing quickly. The hybrid apps are the option, but I find it a bit half-arsed workaround with all the cons of the installed apps and all the cons of the web. Investing in the web is the way to go!

The issue when JavaScript is disabled is now fixed, thanks for pointing this out!

For me, the role of the best place to go for all the Web Platform things is MDN. It's far from being perfect, but it's the only place that looks like is following what the growing web has to offer and is comprehensive enough to be treated as a some form of digestive documentation.

I, as a full stack guy leaning more toward front-end stuff, was personally unaware of the majority of the new HTML5 APIs available or coming to the web soon. I was repeating the cliche that there is a broad set of functionality that is available only for native platforms.

When I learned that is no longer true, I decided to put something from me to promote that. That's how What Web Can Do was created: https://whatwebcando.today. This is a small interactive overview of the device integration APIs available on the Web Platform today or tomorrow. Most of them were - or still are - tagged as "native only". I hope we can remove that label soon.