this post was submitted on 08 Dec 2023
6 points (87.5% liked)

Learn Programming

1625 readers
1 users here now

Posting Etiquette

  1. Ask the main part of your question in the title. This should be concise but informative.

  2. Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.

  3. Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.

  4. 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 1 year ago
MODERATORS
Ategon@programming.dev
JaumeI@programming.dev
bugsmith@programming.dev
6
Stick with kotlin? (lemmy.world)
submitted 11 months ago by Lime66@lemmy.world to c/learn_programming@programming.dev
7 comments fedilink hide all child comments
 

I decided to go for kotlin as my first language because I had ideas for a mobile app. I quickly learned that android dev isn't the best starting point, and I'm not a fan of the lack of choice I have for editors with it. I only really know some basics, I used to know some javascript but forgot it

you are viewing a single comment's thread
view the rest of the comments
[–] balder1993@programming.dev 8 points 11 months ago (1 children)

Android dev will be overwhelming for a beginner. If you’re still learning, I’d suggest starting with some command line stuff just to get the hang of the standard library, concepts etc.

You can use any IDE for simple stuff but Android Studio is tailored for Android framework complexities that added up over time.

[–] porgamrer@programming.dev 3 points 11 months ago

You are right about android dev being overwhelming, but honestly I think if OP is motivated to make an app, that's what they should do. The tools will be bizarre and confusing, but they will get something working if they keep trying.

Once they have a barebones app on the screen, every new concept learned will have clear purpose and value, in terms of how it enables a new feature for the app.