Open emilmuller opened 5 years ago
Actually, Chrome needs the existence of a service worker with "functional fetch handler" for suggesting installation, not necessarily offline functionality like analysis and puzzle. It would be enough if all the basic service worker did was to serve a offline.html page that tells the user that they are not connected to the internet. More functionality could be added later on. Example service worker: https://serviceworke.rs/offline-fallback_service-worker_doc.html Depending on how long the road to offline support is gonna be this may be a good temporary solution.
One more point: could "Maskable Icon" be added? Android uses adaptive icons and PWAs are able to serve adaptive icons. This would enhance integration on Android if installed as PWA. More info on maskable icons: https://web.dev/maskable-icon/
Regarding the fetch handler, simply adding one means that requests must now go through the service worker, adding some latency, so I am hesistant to do so without more tangible benefits. The MVP should have navigation preload and a sound update mechanism for the service worker.
Any update on this?
Here are some thoughtful PWA suggestions from the_mindset I didn't want to get lost.
Adding this to the pile...
If I could ever wish for something in the whole wide world, it would be that lichess conformed with the PWA requirements. It would be awesome to have lichess on my start menu :)