this post was submitted on 20 Apr 2024
7 points (66.7% liked)
Learn Programming
1655 readers
1 users here now
Posting Etiquette
-
Ask the main part of your question in the title. This should be concise but informative.
-
Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.
-
Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.
-
Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/
Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
No. There are a lot of small frustrations that add up to a sense of futility. These frustrations can only be addressed one at a time and are annoyingly orthogonal to the task you're trying to complete.
Even more frustrating is that the people who write tutorials are typically well past that early stage of learning and have forgotten about many of the little details they no longer need to think through and are unconscious of the knowledge they are leveraging gained from their early stage of learning. So you can find a lot of tutorials that simply don't address the issues you are likely to run into. Which is understandable to not want to include every possible issue in a focused tutorial, but there are often no hints or resources linked to help someone with the unstated prerequisite knowledge.
Also, you seem to be using Linux and that tutorial has a bunch of screenshots examples for MacOS. This is another annoying trend from the silicon valley based developers of assuming that everyone outside of their bubble is using the same technology stack as they are and often the newest and most expensive hardware options. (Which I suspect is a big influence on Android Studio being as resource heavy as it is.)
You don't need to use Android Studio for Android development, but it's probably the path with the least friction for getting started.
But there are a few non-Kotlin options for Android development, Flutter and Progressive Web Applications (PWAs) are two different pathways for Android development which don't require Kotlin.
Ultimately, I suggest that you stick with Android Studio and learn the annoying details that it requires to be used effectively. You'll feel like you're moving much slower than you want to at first but you'll get up to speed eventually. And you can ask here or on forums or chat rooms for help as you're figuring out the details of Android Studio.