Win a copy of Succeeding with AI this week in the Artificial Intelligence and Machine Learning forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
  • Junilu Lacar
Sheriffs:
  • Tim Cooke
  • Jeanne Boyarsky
  • Knute Snortum
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Piet Souris
Bartenders:
  • salvin francis
  • fred rosenberger
  • Frits Walraven

Learning Progressive Web Apps: Performance vs Native and Web apps

 
Ranch Hand
Posts: 41
jQuery Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi John,

I am curious how PWAs compare to Native and Web apps in terms of responsiveness and device resource utilization (CPU/memory/battery)? What are the bottlenecks? What are the best practices, things to watch out for?

Thanks!
Alec
 
Author
Posts: 15
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't have any solid comparison data, although I'm sure there are studies out there.  I'm curious, why are you worried about this? I can write a native app that performs poorly or a web app that performs crazy fast. It's the developer and the developer's skill that matters here IMHO.

PWAs actually give developers the ability to improve performance, especially load time, using the Service Worker to cache resources (assets). Don't forget, that the JavaScript focus of so many web development frameworks means that we web is more solidly running on JavaScript anyway, and the browser vendors know this and have tuned JavaScript performance accordingly.
 
Alec Swan
Ranch Hand
Posts: 41
jQuery Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The reason why I am worried about performance is that any comparison between alternative technologies is incomplete if it only compares their capabilities and not performance, security, maintenance, cost, etc.
I do realize that this may be beyond the scope of your book but, in general, all of those would play a role in my decision on whether or not adopting PWAs is the right thing for my product.
I agree that JavaScript has been getting a lot of love from browser vendors, esp. Google, which is a good thing. So, if performance considerations for PWAs are similar to those of Web and Native JavaScript apps, then it answers my question.

Thanks!
Alec
 
John Wargo
Author
Posts: 15
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes to similar as web apps since a PWA is just a web app with some extra JavaScript code in it.
 
Check your pockets for water buffalo. You might need to use this tiny ad until locate a water buffalo:
Two software engineers solve most of the world's problems in one K&R sized book
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
    Bookmark Topic Watch Topic
  • New Topic