You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently on my machine it takes ~2s to get response to the initial GET / request, which slows down the experience.
If the App would follow the rules around PWAs and register ServiceWorker, define manifest and static resources, then the initial 2s could be completely eliminated. PWAs are using interesting set of native browser APIs and there are multiple interesting things that can be done.
saving latency and number of resources that need to be sent over wire (essentially the ServiceWorker serves as a proxy between the web app and internet - you can do various caching and background-refetching schemes)
After looking at this again, display: standalone, which is the main thing stackers claim they want when they ask for a PWA, does not allow the PWA to share state with the browser on iOS Safari, nor can you link to a PWA on iOS, so email login won't work. Also, navigation (back/reload) is lost with standalone and SN doesn't provide any navigation (wizards claim this doesn't matter but part of maintaining high wizard status is not caring about non-wizards). A middle ground: Chrome treats minimal-ui nearly the same as standalone and Safari treats minimal-ui like browser, and navigation is retained in either case, so for now we can use display: minimal-ui.
Another option is to grab the user-agent when the manifest is requested and return a different manifest depending on the browser/os.
I'm going to leave this open because it's still desirable to have an actual PWA, one that does everything a PWA can do. However IMVHO it at least requires figuring out navigation and login.
Currently on my machine it takes ~2s to get response to the initial GET / request, which slows down the experience.
If the App would follow the rules around PWAs and register ServiceWorker, define manifest and static resources, then the initial 2s could be completely eliminated. PWAs are using interesting set of native browser APIs and there are multiple interesting things that can be done.
Here are basic tutorials:
The are various benefits, e.g.
The text was updated successfully, but these errors were encountered: