don't be mystified. all of this comes from your lack of knowledge and experience of native development. if it works in a webview then making a 'native' app out of it is not going to be complicated - you make something with a webview and the html or whatever other source data in the package.

its not magic, its not even hard, you just happen to not know about how it works... if you are interested this is easy to fix with google and experimentation. :)

knowing about android sdk versions is something you would also know if you were an android developer. its everywhere from the first time you install an sdk or ndk - i agree that Google suck at developer tools and docs, absolutely 110%, and this is a good example of that - a lot of their tools I consider 'unshippable' they are so bug riddled and unusable - but thats a tangent.

i do wonder though why even use a native app like this? isn't a web app more friendly? you certainly won't get any of the performance benefits of native code without some real heavy lifting on the part of the framework/library/sdk. isn't a landing page asking you to download a native app just annoying? i know its popular but its just a UX fail however I look at it...