DEV Community

Discussion on: PWAs are our future

Collapse
 
vuild profile image
Vuild

To take a counter point.

The purpose of native apps is to supplement the slow progress & feature lacking options of web/pwa etc.

Access to the latest APIs & features, extra testing, robustness, security, performance come from being full native. For most basic data apps, PWA is good & cheaper from a dev standpoint but native is native (different OS handle different rendering/animation etc). The gap is smaller but still there.

In the end, they want thin client but I want thick. I will always buy thick so I think both will exist (my data, my device, my rules, my lockout vs their control). We are already seeing a shift back towards individual control.

Collapse
 
stefandorresteijn profile image
Stefan Dorresteijn

Thanks for your comment!

I think this is true at the current time. PWAs are being supported, but features tend to come later to them. However, as more, larger companies start using them (as Uber, Spotify and AirBnB already are), they'll be prioritized when it comes to rolling out new features as well.

When it comes to individual control, I don't think there's an actual difference between running a PWA or running a native app. Both contain code you have no control over, both do things with your data you're unable to see and both have to ask for permission to use your native functionality. I believe a majority of app users won't even be able to spot the difference between a PWA and a native app, let alone decide not to use something because it's web-based.

Collapse
 
vuild profile image
Vuild

This is it. If you are sending a bunch of listings & a couple of clicks, then PWA can do.

But if you want an AR with Facescan Siri video morph that has pencil support, PWAs always lag (browser/spec/companies etc). Unity/Unreal/3D worlds/sensor access are more reasons.

For me, it is the same as it as always been (built a lot of apps since store launch)... use the right tech for the job you need. Native, webview, hybrids, pwas, voice, framework whatever. I don't really care for trying to define it with words & just try to pick the right one. It's all just 0101010s.

PWAs have a big future. Native has extra/leading edge. Stadia & Arcade are coming for extra considerations.

Thread Thread
 
stefandorresteijn profile image
Stefan Dorresteijn

Oh I completely agree that PWAs are not going to be competing with the significantly more advanced apps out there. Use the right tools for the job, but I think a lot of apps out there that are currently native could easily be PWAs and would actually improve if they were written as PWAs.

Thread Thread
 
vuild profile image
Vuild

That is 100% true, with better resource allocation, speed, progress etc. Almost all listing apps can be PWA, many will be better faster. This applies to the web even more so. A million frameworks of thousands of lines to deliver 400 words, a couple of pics & btns.

Big tech politics plays various roles too.

Native is basically the default 'never wrong' right now (PWA & break your business vs "I did it the traditional way, it's not our fault") plays in too.

I like competition so I like all options. Be nice if there were more mobile operating systems, browsers, datasets, UIs, methods etc.

80% sounds about right, I'll make some of those. And some of the 20% too. 😃