About a year ago, I created an Android game app for studying and published it on Google Play, but I didn't advertise it in particular, so it was a shame that the number of installations was 1. I've forgotten the specifications for a long time, but I think it's an app that I can enjoy for the first 5 minutes without getting bored, so I wrote an article with the intention of recording it as much as I can remember.
It is a brain training & reflex nerve application that quickly taps numbers from 1 to 32 in order. When the time is less than 20 seconds, it is S rank, and when it is less than 15 seconds, it is SS rank.
The trick is not to look only for the next number, but to get a bird's-eye view of the numbers, grasp the numbers, and assemble the tap order with your head.
By the way, my best is S rank, and I have never issued SS rank. I set it properly, so unless I'm a superhuman, I don't think it will last 15 seconds ...
Is it roughly divided into the following four? I have a lot to study and it's a tough job.
Java Logic part of the game
Android SDK Android-specific events and parts, etc.
Android Studio App coding and building
Google Play Console Publishing the app
To be honest, there was no book that said, "This book is insanely easy to understand!" Also, since Android Studio and Android SDK are updated frequently, the contents of the description become older and older, so I have the impression that some problems must be self-solving.
However, in Android development, I think that there is a limit to the information on the web, so I think it is better to buy some books. I used the following two books. Recently, I think that newer books are coming out than the following books, so I think it is better to buy new books as much as possible.
――I was confused because I had hardly used a statically typed language, but once I got used to it, there seems to be no problem. --I still don't fully understand the access modifiers. --I forgot the signature key, I couldn't remember it after all, changed the package name and republished it. It's too painful. --There is a lot of information on the WEB because it is HTML + CSS + JS, but there is little information about the View of the Android application. It seems to be painful if you can't read English. ――I changed the CPU from AMD to Intel for the Android emulator ... That's why I felt like I had to create one app.