>>1539115
I hurried with the reply because it was on page 11 but the basics are:
You declare your layouts in xml, much like html works for the web, then you add your java backend, you put all of that + any other resource you need into a .zip with a special file inside (androidmanifest.xml iirc) that tells you the zip is actually an apk, you then take that zip and use it with the android SDK which transpiles it to android bytecode, which the phone interprets later
>then it's a encapsulated and limited miniweb?
not quite, they use a somewhat similar system to how browsers display stuff but that's != to the web, and webpages are limited, with apps the sky(or well, whatever goygle wants to impose)'s the limit
>either the apk's or other thins inside android does not use some libraries like the gtk/tcl/nexstep/mfc?
if I understood your question right then no; the rendering is done with xml (and that's sufficient for simple apps), or at least it's intended to be done that way, obviously retards try to hack in and force ...
>All that is javascript/electron/whatever slop?
... into their apps for no reason at all other than doing useless shit the apk system already handles natively
