I'm not sure your argument against PWAs is entirely fair. Yes, when bad people want to do shady things, they can use PWAs to do those things. You still need to give the web app the permissions it needs to use the native functionality it's asking for so you have a decent amount of control over what the app is allowed to do.
When it comes to the quality of the PWA, that's where Google's standards come in and should be followed rigorously. Scrolling should feel completely natural and feel exactly as seamless as a native app. This is an achievable standard but it takes some attention from whomever is developing the app.
If we are going to turn PWAs into another walled garden(google standards etc), dont you think native apps already are there? Im sure we can have good things with Web assembly etc, but aren't we just coming to the same concept back to a kind of containered, "controlled" experience?
Somehow I think PWAs will end up just like how apps are like now, sandboxed, monitored and walled.
Unless an average Joe can Code. Companies will always want to protect their users's experience?
Somehow we end up going up and down the same lane/cycle.
The good part is that pwas don't need to be delivered through walled garden type of environment that is Google play or app store so you've got some freedom here
I think you misunderstood me here,
PWAs can be very easily injected with scripts, which can run unauthorized code onve permissions are granted, which will create a scenario where we will revert to a "verification process" and we are back to walled gardens
Do you have the article here on dev.to ? I checked it out and have some questions. It's now 2021 do you have an update to that procedure? and can you explain how to pre-cache pages(blade.php) with regards to a Laravel PWA? or they don't need to be cached ?
Thanks for the comment!
I'm not sure your argument against PWAs is entirely fair. Yes, when bad people want to do shady things, they can use PWAs to do those things. You still need to give the web app the permissions it needs to use the native functionality it's asking for so you have a decent amount of control over what the app is allowed to do.
When it comes to the quality of the PWA, that's where Google's standards come in and should be followed rigorously. Scrolling should feel completely natural and feel exactly as seamless as a native app. This is an achievable standard but it takes some attention from whomever is developing the app.
If we are going to turn PWAs into another walled garden(google standards etc), dont you think native apps already are there? Im sure we can have good things with Web assembly etc, but aren't we just coming to the same concept back to a kind of containered, "controlled" experience?
Somehow I think PWAs will end up just like how apps are like now, sandboxed, monitored and walled.
Unless an average Joe can Code. Companies will always want to protect their users's experience?
Somehow we end up going up and down the same lane/cycle.
The good part is that pwas don't need to be delivered through walled garden type of environment that is Google play or app store so you've got some freedom here
I think you misunderstood me here,
PWAs can be very easily injected with scripts, which can run unauthorized code onve permissions are granted, which will create a scenario where we will revert to a "verification process" and we are back to walled gardens
Try injecting scripts into a HTTPS connection, which PWAs must use.
hi mao,
here I created a detailed step by step article for creation in PWA. I guess this will help
Do you have the article here on dev.to ? I checked it out and have some questions. It's now 2021 do you have an update to that procedure? and can you explain how to pre-cache pages(blade.php) with regards to a Laravel PWA? or they don't need to be cached ?
Hi selase,
i will me more than happy to help.
please DM me with all your quries.