When we use a normal web app in a mobile browser we see it just like a browser page in the browser tab. The url bar will be visible. For a normal website its good for the user because it's convenient to change the url at any time.
When we see a Progressive Web App (AKA PWA) in a mobile/tablet/phablet device, it will give experience just like an installed app in the device. But we have to open the web app with its shortcut to get this experience. When we first open the PWA in a chrome browser, it will suggest you to add a shortcut icon to the home screen. If we are opening by this shortcut icon, then we will get an app like experience, i.e. the url bar will be invisible, we can see a custom color for the url bar, the shortcut icon will be a custom icon built by the PWA creator, there will be a splash screen and it can also work in offline.
Web Firm Framework web site is a good example for PWA. Once you opened the page, try it also in offline mode you can see the page still loads from the cache.
These are the pros of a PWA.
A real-time example will be: I have an inventory app, which lists the sale invoices. If you see the old data instead of the new data but shows just like the updated data then it may affect to the business.
For the marketing of some frameworks and technologies, some framework/technology providers advertise as if a technology/framework is required to build a PWA. However, we found Web Firm Framework as the best java framework for web app development.
Also read what is not possible with PWA.
When we see a Progressive Web App (AKA PWA) in a mobile/tablet/phablet device, it will give experience just like an installed app in the device. But we have to open the web app with its shortcut to get this experience. When we first open the PWA in a chrome browser, it will suggest you to add a shortcut icon to the home screen. If we are opening by this shortcut icon, then we will get an app like experience, i.e. the url bar will be invisible, we can see a custom color for the url bar, the shortcut icon will be a custom icon built by the PWA creator, there will be a splash screen and it can also work in offline.
Web Firm Framework web site is a good example for PWA. Once you opened the page, try it also in offline mode you can see the page still loads from the cache.
These are the pros of a PWA.
There is a major disadvantage for PWA.
That is its ability to work offline because it will not show updated data while offline and the user may misunderstand it's updated data even if it is not.A real-time example will be: I have an inventory app, which lists the sale invoices. If you see the old data instead of the new data but shows just like the updated data then it may affect to the business.
Should we use any particular framework to develop PWA?
No, it's not required. It does not depend on any framework it depends on how you build your app and whether it satisfies the checklist published by google. We can use any MVC + REST to build PWA, it all depends on how we use the framework.For the marketing of some frameworks and technologies, some framework/technology providers advertise as if a technology/framework is required to build a PWA. However, we found Web Firm Framework as the best java framework for web app development.
How PWA achieves app like user experience?
The browser must support PWA functionalities otherwise it will work just like a normal web app. The latest version of Chrome supports PWA.Also read what is not possible with PWA.
No comments:
Post a Comment
Have you used java webfirmframework?