André Cipriani Bandarra

I think an approach we can take here is to add a demo app that contains a WebView fallback. We can start with a naive implementation that will give us...

#46 kicked off a demo implementation. It's a naive implementation for now and more work is needed for it to be a good fallback implementation.

Yes, that's why we haven't added it as a default to the library yet. We haven't been able to come back to this yet. Any contributions to improve the WebView...

What does the issue you are experience looks like? One thing to keep in mind is that the WebView fallback will probably work on a best-effort to support PWA features...

@strygo Implemented most of the missing things. Not sure about this one though: > The navigation bar color behavior doesn't seem right. As of now, the sample uses transparent, which...

@naveedahmed1 Right now, the best source of information is the demo itself. We will move the fallback into the support library, which should make things easier. We probably won't enable...

It will be integrated into [`llama-pack`](https://github.com/GoogleChromeLabs/llama-pack)

I've just added support for earlier APIs on the last PR. Regarding Fire TV / Android TV, my guess is that developers should probably use store targeting to deploy a...

@Andrew67 thanks for catching this #191 adds a trailing slash to the WebView fallback. The trailing slash helps differentiate `android-app://com.example/` from `android-app://com.example.subdomain`, so user-agents should add it.

You web application should have a Service Worker that is installed on the first run and will manage offline access after that. Check [this article](https://web.dev/offline-fallback-page/) on how to implement this...