MaxArt
MaxArt
Jul 27, 2017 · 2 min read

The reason why native apps won’t disappear any time soon is because of either performance-critic tasks (a well optimized game, for example) or because it has to access to device specific features that can’t be included in the sandboxed environment of web applications, like shared disk space or fingerprint sensors or whatever. For the rest, a web application can be ok.

What you’re missing here is that a lot of apps in the store are hybrid already, which means they’re based on web technologies anyway, in particular for the layout and visual rendering part. So, visually, you’re seeing a web page. Sure, a good part of the application is still native, but it’s working behind the scenes.

The least meaningful point that you’re trying to make is about battery consumption. That’s not really a concern, to be real. It’s not like your battery gets drained when you’re just surfing the web. In fact, most of the battery consumption comes from background processes and (above all) merely from the display being lit. You’re not saving the Earth by just creating native apps.

PWAs aren’t in a lot of developers’ and companies’ wish list because it’s pushed by Google. It’s because they streamline app development with well-known, open and shared technologies from the largest and most vibrant community ever. Focusing on just web technologies leaves more time making a better product. Maybe even more energy efficient.

No, companies don’t always “have so much to spend”: more often they work with limited time and resources. Sharing dev expertise between two starkly different worlds (Android and iOS) is detrimental to the development process, but it’s what we’re forced to do. And thanks for insulting a lot of hard working developers and companies.

AMPs are a totally different thing, as they’re aimed to serve contentful, mostly static pages. A news article isn’t a web application. You’re just mixing things up.

Seriously.

    MaxArt

    Written by

    MaxArt