So Android allows alternative rendering engines besides Chrome for PWA? If you install Firefox it uses Gecko but still has native app look feel? I honestly don't know but would be surprised if they did.
I tested just now in Firefox with an app from https://appsco.pe and it does indeed work!
I can do the same with the Android version of Brave.
> If you install Firefox it uses Gecko but still has native app look feel?
That depends on your definition. Making an app _feel_ native is a matter of implementation. But the opposite is also true: A native app is free to feel non-native if the app creator makes it that way.
The app does show as a distinct entry in the app switcher, but still has a Firefox icon when I tested it just now.
I don't know what your setup is, but it did work for me, creating an app that shows as its own icon on the homescreen, without FF chrome, with a separate app-switcher entry. Using a S24 Ultra with whatever the current OneUI is.
Ok so I guess Android has some sort of API for allowing an app to install additional icons on the desktop with specific parameters like a shortcut and it shows the icon with a little icon representing the parent app, makes sense.
So if you install a PWA from Firefox it runs in Firefox and from Chrome it runs in Chrome similar to desktops. Looking at it this way I could see Apple doing something similar with less effort than trying to standardize a web view API and have PWA use the "system default browser".
Installing a PWA on Firefox for Android adds the icon to the homescreen with a tiny Firefox icon at the bottom. The look and feel is Android, there's no obvious bits that would look either Firefox or Chrome.
The look and feel of the app itself is a CSS issue. There are web app frameworks that specifically offer themes matching style guides provided by Apple and Google. Framework7 is an example: the demo app on the home page is styled using iOS UI elements, and there is an option for more Android style designs as well.
