While a lot can be done in kivy, I foolishly decided to try it out with absolutely no primer on java, android or native development in general.<p>It was ok, everything felt like it had to be hacked together, and for some reason the only working version I could get stuff to compile in was like android SDK 19 and ndk 14b I think? (you literally had to thread the needle with your envs) At the time I don't know if they actually had a working buildozer env for 64-bit ARM.(could be wrong on that) Compiling took forever, especially the first time, which 99% of the time I couldn't get any 64-bit version of anything to compile so nothing was cached. I'd change one config wait 10 minutes come back not ideal.<p>Again I was probably super naive in my approach, but overall it felt very constraining and not the java is a peach but I was much more comfortable learning java (from scratch) and android than wading through kivy.<p>I appreciate the developers contributions, and I'm probably at fault, but I'm just saying its worth noting it wasn't any easier getting an app running if you know just python with kivy. I've also come to realize gradle and android are just a huge bloated mess in general lol.<p>As a side note cross compiling packages in go for use on android does work really good for stuff like daemons.