>>106035824
>I never did anything for android
then you definitely should not do any game right away. Stick to a game engine.
Unity and Godot have the best support for Android platform among the major game engines. Unreal bloats the shit out of the game by default. Making it not generate a bloated apk is a huge pain not worth bother unless there is a strong reason to use unreal.
>Some pointer for what technologies I should use
First, understand how to use android studio. There are plenty of tutorials on youtube and official getting started examples which are good enough imo. Create a few projects and figure out how to deal with Activities and Fragments. Its important to understand their life life cycles when writing android application. Java or Kotlin are your language of choice here so ditch Java. Even google is trying its best to do that.
As for graphics API, go for Vulkan if possible. OpenGL ES 2 will also work but remember that it'll also be limiting.
You need to deal with android NDK shit and dynamic or statically linking C++ code while building with gradle or cmake for this(there are other ways to package an apk as well). Your C++ code has to be called by Java/Kotlin code from within the activity at appropriate times or else your app will crash. All's simple if you only render to the screen. Complexity hits hard if you need to do anything more, like copy text from clipboard and shit like that.
