Hello there,

I am an experienced programmer. I can do C/C++/Rust/assembly/Ruby/Perl/Python/ etc… The language itself is not a barrier.

The barrier to me is that I have never coded a single web or android application. I guess it must be surprising but I am more of a low-level programmer in my job (I develop a compiler backend) and I never really had the opportunity or idea to work on an app.

What would be a good starting point for making an android application?

A quick search got me this: https://google-developer-training.github.io/android-developer-fundamentals-course-concepts-v2/unit-1-get-started/lesson-1-build-your-first-app/1-1-c-your-first-android-app/1-1-c-your-first-android-app.html

Would it be a good starting point?

Side note: my app will not have to interact with any service. If I were to code it as a command-line program, it would not take me more than a day or two. The actual app would involve (for now) no more than a text field, a button, some logic attached to it - the hard part for me being to choose a framework to build it, “upload it” to my phone and use it.

  • I’m old ahem experienced too and I went from no app development to having a basic native app on my Android phone in a few days with Flutter/dart. The language is easy to pick up, there’s plenty of documentation and it’s pretty polyvalent since it can build for mobile, desktop or web.

  • Depending upon what you are trying to do, a Progressive Web App (PWA) might be a solution if you don’t mind JavaScript. Avoids a lot of platform learning curve. (But you do end up having to learn HTML and CSS too)

  • Last android app I created for a personal project I did using Kivy which is a python application framework. I found it nice to be able to develop the app on the desktop and then run on Android. There were enough multi-platform python libraries for things like bluetooth that I was able to even develop that side of things on my desktop development environment as well. This would be the framework I recommend.

    Web Apps are also a good choice. I have a couple apps running off my homelab that are just webpages accessible from inside the network and they work well enough on mobile. If you really want to package it there are a couple ways. Not the best use case for you, but might be of interest to the others, I really love Tauri. It is an alternative to electron that focuses on binary size and security. Tauri 1.4 is great for desktop applications. The alpha version of 2.0 supports mobile, however I have yet to write anything for the 2.0 version that hasn’t involved creating a pull request to fix something so… you’ll be in for a treat if you go this route.

    As mentioned in thread, several game engines do mobile packaging fairly well. Godot’s android functionality works pretty well. Bevy has limited android support, but the web version functions well enough. I see this as more of a “If you already know a game engine, you might secretly know how to make a mobile app. Don’t learn a game engine just to make a mobile app.”

    • +1 for kivy (Actually, kivymd; love those widgets). I have also been developing a bluetooth based app on a (Windows) desktop and then packaging it for Android. It was a substantial learning curve for me, but I found the end result to be worth the effort.

  • Have you considered writing a responsive web app in JavaScript that can be hosted by GitHub Pages? Depending on what exactly you need to write and what you need the program to do, that may not be the best option, but it is simple, you don’t need to worry about hosting the site, and it allows you to rapidly deploy your application and make it accessible anywhere through a web browser. You just write the HTML, CSS (if you wanna be f a n c y), and JS. No shortage of tutorials on those 3 languages.

    Here’s a few examples I’ve written:

    https://github.com/mpm11011/hanafuda-react

    https://mpm11011.github.io/spirit-island-tracker/

  • You can build it in Godot and export it to your android. Alternatively, you could build a webpage and access it via your phone browser.

    Godot is how I’d do it. I’ve done something similar before.

  • If you want to use python, you could try Flet. I’ve been using it for some projects at work and it’s dead simple to create an acceptable UI and the docs are very easy to read through with frequent examples. In July they added support for Android and iOS via progressive web apps, I haven’t tried it out yet, but it seems interesting so I might start a project in it soon…

    I’ve been having fun with it, if that’s worth anything!

    Otherwise, depending on your phone I’d just do native code with Kotlin + jetpack compose for Android or Swift + swiftUI for Apple. I always greatly preferred android development in school but once jetpack compose and swiftUI came out I find them both to be about the same level of enjoyment.

    All three of those options are all declarative (describe how you want it to look in code) and I find it much easier to deal with than iOS storyboards or Android xmls.

  • That doesn’t seem like a bad start to me, but I haven’t read it thoroughly. I also recommend checking out the official Android Studio beginner’s guide: https://developer.android.com/get-started/overview

    Alternatively, you can use wrappers like Flutter, React Native, or the Ionic framework if you think you might want cross-platform or web capability later, though that adds a lot of overhead that isn’t always the best choice.

  • I’ve been using flutter + android studio and I’m enjoying it (as much as you can while making a mobile app). Android studio is a lot but it includes android emulators which is nice to test stuff on if you don’t feel like getting your phone.

    You’ll need to install flutter (works on windows, mac, and linux), android studio (I think vscode also works?), and you can download a sample project, open it, build it, and run it. It’s a great way to see how it works. Then you can create your own project and go from there. Flutter has a lot of packages which I would recommend at looking through (if your app is simple you might not need any of these though).

    Once you build and run the app on your android phone, it’s there and you can use it. You don’t need to upload it to google play or anything else (unless you want to share it).

  • React native is pretty simple to get started. I built my first android app with it a few months back. Also cool that you basically get both the android and iOS apps done at the same time.

  • I am an experienced programmer. I can do C/C++/Rust/assembly/Ruby/Perl/Python/ etc… The language itself is not a barrier.

    Well, first of all, don’t try to use any of those languages and recognise that the language is a barrier. Choosing the right tool for the job is critical. Those are great languages… but as far as I know there are precisely zero good user interface frameworks available in those languages.

    Just like a good function starts by picking a good name and argument list, a good user interface has to start with a good user interface design. Unfortunately user interfaces are complex beasts and it’s virtually impossible to get them right the first time. You absolutely must pick a user interface tool/language/etc which allows you to make major changes (including scrapping the whole thing and stating over) in a short amount of time (minutes, preferably).

    The best user interface languages are declarative ones. You should be describing the structure of your interface, largely ignoring the functionality - that’s something which can either be done for you by the framework or done yourself as a completely separate task, in a different file, maybe even a different git repository, and probably a different programming language.

    It should be possible to get a rough interactive version of your app up and running very quickly, so you can test it, learn what works/doesn’t work, show it to other people, and you need to be able to rewrite entire sections of the interface by simply rewriting two or three lines of source code.

    I recommend HTML/CSS as a good starting point. After you’ve got your head around that first (it won’t take long, it’s relatively simple). After that look into more modern tools like React Native. Learn to crawl before trying to walk.

    The article you linked to is just wrong. It suggests this process:

    1. Define a layout for each screen that has UI elements.
    2. Create source code for all of the app’s components.
    3. Build and run the app on real and virtual devices.
    4. Test and debug the app’s logic and UI.
    5. Publish the app

    Step 4 needs to be tightly integrated into Step 1. Start working on step 2 after you have finished step 4 (and then, after you’ve done steps 2 and 3, you will need to repeat step 4).

    I encourage you to read less articles, they’re often giving really bad advice and without experience it’s impossible to know which ones are good advice. Instead pay for ChatGPT Plus and just ask it questions. “How do I make a button in HTML/CSS” or “how do I make it execute code when the user clicks it” or “how can I deploy a HTML/CSS/JavaScript app on Android”.