Package bread bucket as a mobile application

[jjohnson338]

I've been using this site personally and I keep thinking, for my purposes, it would be better to have a mobile app. Instead of going out to the internet, the app could interface with a local .buckets file perhaps tracked by a file syncing application (nextcloud for my purposes) and that would handle the syncing.

I've spent a bit of time doing just that. In this PR, you'll find the addition of a MobileDockerfile that scripts out the process of setting up the build env and "packaging" the flask app as an Android application. For the Android app, you don't really need some of the functionality built into the current web-app, such as authentication, and limiting, so I've introduced environment sniffing and some branching code depending on the context in which the application is running.

This PR is a rough-in of the Android packaging. Currently there are some caveats including:

• The app assumes a db.buckets file to exist at /storage/emulated/0/Documents on the device. Ideally the user would be prompted for a file location at first run, and this would be stored for subsequent runs
• There is no fancy app icon, the default for python-for-android is used
• Many of the commands I've included in the package.json assume things such as the Android SDK installed in a specific location, an AVD is created with a specific name, and adb is present in the path

I wanted to create this as a Draft PR so that we can have a discussion on where this should exist. Should it be merged in? If so, I've structured the code in such as way, that the "Android" bits are easily distinguishable. Should this exist as a separate project? Let's discuss.

I've included some images of the app running for your viewing pleasure below:

[cmeury]

Interesting! I am not actively using the app currently due to #2, and also not generally putting in work here. You could either fork it, or I could add you as a maintainer and help out with reviews, build setup, etc.

[jjohnson338]

Let's go the maintainer route, if that's okay. I may take a swing at #2 shortly as well so that this app is more useful for other people.

What are your thoughts on including the android packaging in this repo?

[cmeury]

That's pretty nifty. I think you either leave the "dual mode" in this repo, or maybe take everything and create a new fork that is a dedicated mobile app?

[jjohnson338]

Unfortunately Github won't let a user fork a repo twice and still keep upstream pointed to the original repo in both. I think I'll keep working on this in this branch as a draft PR for now. If I get to a state that I'm happy with, maybe we can think about merging it then.