#firstpost

Voila a blog about my experience writing my first serious (/ever) website and Android app. I'm hoping these posts will be motivational and documentational*, and at this point I'm willing to take the risk of them inspiring a lawsuit when the app inevitably makes me a billionaire CTO.

So far, I'm blown away by the number of choices I need to research and make before I can even get to designing / planning code.

• What language should I use? (Apparently this is no longer just a Java or fuck off situation like it was in Android university assignments.)
• What frameworks should it use?
• How would I implement a database, and where would I get storage? Is there free storage? (If you are reading this, feel free to give me free storage tymv.)
• I want a web interface as well, does that affect the choices I should make for the above questions?

As a millennial, my first instinct was to read every 'Top [#] Common Android Mistakes' listicle that exists. None of these included things like 'failing to consider Kivy and Ruboto', so I consider them votes for standard Java by omission.

However, it does seem like the wellest-trodden road is to start by making a website and connect that to Mobileland later.

*When I come back to this in a year, having made zero progress on it.