Mastodawn

I'm beginning to love 🐝 @beeware for #Python for Android development.

2 reasons.

The build process to get an Android app running from scratch is working even if you (like me) know nothing about Java and Android. There's a tutorial telling you all steps.

Interacting with Java (to access hardware features outside of the scope of #Beeware) was a pain to get working (for me), but that now it does, I'm confident that I won't be show stopped later.

See example: https://github.com/mborus/can-beeware-for-android-bridge-to-java

GitHub - mborus/can-beeware-for-android-bridge-to-java

Contribute to mborus/can-beeware-for-android-bridge-to-java development by creating an account on GitHub.

GitHub

Show thread

mborus Oct 8

Why do I want to use Python on Android anyway? Mainly because for me Android development is a side quest - I need simple forms for data entry and so some hardware stuff like scanning bar codes, getting location and network information and printing to bluetooth (the last one is not solved yet)

We used to do these on WindowsCE, but nowadays all the new hardware is Android.

Coding all screens and logic in a language that I (and the device users) already understand is a huge time saver...

Show thread

mborus

Mainly because again and again I experienced that users can't define their requirements and it's much speedier build a prototype and work from that.

I used to write mock desktop versions of apps just because deploying to WindowsCE took too long (=more than a few seconds) - Beeware's "briefcase dev" command allows me to do that and deploying to real devices is reasonably fast.

So after evaluating it for a few weeks I'm now making the jump and will attempt to use it in production.