DEV Community

Discussion on: PWAs are our future

Collapse
 
kobbyknight profile image
KobbyKnight

My point of view comes mainly from working in a young Startup, and our system contains 2 web based frontends, one of which is stand-alone, and not fed by an online server. Thinking of adding 2 native apps to this architecture would kill us. So PWA's are just awesome, not to forget Web Assemblies when it's about higher workload.

Yes I do share a similar view, being also in a young start up. PWA's cut down extra development time by a huge margin when the development commences on a web app basis. However, I do prefer native. The only reason PWA's are a go to for most young startups has to do with the workload and human resource available.

Anyway, the part I most like in PWA's is the first word - progressive. To reach a full fledged native app, you need to invest much more than when you can start with a pure web app at first, closing the circle to the user early, adapt the design .. and let it grow step by step into a offline supporting app.

Yes, that may be so, but so is any development life cycle progressive. Developing natively can take a progressive approach. Identifying and aligning the right requirements to start with can help make native feel as progressive as well. All apps have room to improve overtime.