7
Can I learn android development in a non-javscript IDE? DAE find electron/javascript IDEs confusing? (discuss.tchncs.de)
submitted 6 months ago* (last edited 6 months ago) by linuxPIPEpower@discuss.tchncs.de to c/learn_programming@programming.dev
15 comments fedilink hide all child comments

Does anyone else find javascript/electron-based code editors confusing? I can never understand the organization/hierarchies of menus, buttons, windows, tabs. All my time is spent hunting through the interface. My kingdom for a normal dialogue box!

I've tried and failed to use VSCodium on a bunch of occasions for this reason. And a couple other ones. It's like the UI got left in the InstaPot waaaay too long and now it's just a soggy stewy mess.

Today I finally thought I'd take the first step toward android development. Completing a very simple hello world tutorial is proving to be challenging just because the window I see doesn't precisely correspond to the screenshots. Trying to find the buttons/menus/tools is very slow as I am constantly getting lost. I only ever have this in applications with javascript-based UIs

Questions:

  1. Am I the only one who faces this challenge?

  2. Do I have to use Android Studio or it there some kind of native linux alternative?

edited to reflect correction that Android Studio is not electron

you are viewing a single comment's thread
view the rest of the comments
[-] dbx12@programming.dev 1 points 6 months ago

Since some folks already suggested Android studio, I want to throw the "new UI" vs "old UI" on JetBrains products into the ring. I'm not sure if it already arrived in Android studio s well, but the new UI sucks in a similar vscode sucks, so maybe that (turning off new UI) is an angle you can investigate.

this post was submitted on 20 Apr 2024
7 points (66.7% 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