Ha, if it makes you feel better I was up until 3am last night getting the package ready for public release!
To answer the questions…
The easy and simple answer is ‘yes’ this is for native only. Only use this component if the intention is for native. This is not an Adalo thing, it is a tech giant thing. Stop reading the rest for sanity if you don’t want the spiel!
I might be a little dated with my information, but as far as I know a custom uri like adalo://myapp only works on iOS and Android for native apps. I believe it is currently in the proposal stage of adapting it for the internet, unless you are a trillion dollar company. So for PWAs you can only use http(s) for deep linking. With that said, this component will work for PWAs, or at least using the component should not stop a PWA from working.
A little more complicated answer is that this would be the wrong tool for deep linking in a PWA as a PWA already has their own deep linking mechanism without custom uri schemes This would work, but it is more complex than direct links (using bit.ly to shorten adalo PWA urls). You could certainly have a user click an http link that goes to the home page, then the home page redirects the user to a specific page in a PWA, but if that is the case, just give a direct link to the page and skip the component.
The 14 year saga answer would be… it’s complicated! If a PWA is installed by Google then Google, being Google, will honor the links associated with the PWA and redirect the user to the right spot in the PWA. By contrast, Apple being Apple figures if you have a PWA and a user clicks a link, the experience of seeing the PWA in Safari is a better experience than a PWA in app mode, so let’s open a PWA link in Safari. This means that true deep linking in PWAs is an experience that the devs don’t have control over.
I hope this helps!