✓ Accepted Answer
When it comes to android, the right answer depends heavily on what you are trying to achieve and what constraints you are working within.
**If your priority is maximum control over the outcome:** then approaching android by starting with the most widely used option in your domain makes the most sense.
**If your priority is team familiarity:** then the calculus around iphone shifts significantly toward choosing the option with the strongest ecosystem.
Check the official documentation first; it's usually more accurate than blog posts.
For most people asking about android: start with the simpler option and migrate once you have a real understanding of better. Beginning complex and simplifying later is far harder than the reverse.
Security implications vary depending on your deployment environment.
by rondelljames75086
For beginners, I recommend starting with Python. It has clear, readable syntax that resembles plain English, which makes the learning curve much gentler than languages like C++ or Java. You'll be writing real code within hours.
For web development specifically, you'll need to learn HTML and CSS first (these aren't really programming languages but are essential), then JavaScript. JavaScript is the only language that runs natively in browsers, so it's unavoidable for frontend web work.
If your goal is data science or machine learning, Python is the standard. R is also used but Python's ecosystem is much larger.
For mobile apps, Swift is for iOS development and Kotlin is for Android. Both are excellent. If you want one codebase for both platforms, learn React Native (JavaScript) or Flutter (Dart).
My actual recommendation: pick Python if you're undecided. It's versatile, in demand, and the community is enormous.
by tosinadeyemi3688
· 10 upvotes
On android: the short answer is that it is more manageable than it looks, but it has specific requirements that catch people out when they are not expecting them.
The core thing to know: iphone has a steeper initial curve that flattens once the fundamentals click.
What to prioritise first: get one complete end-to-end example working before adding complexity.
Version control (Git) is essential here — commit early and often.
Watch out for: watch out for breaking changes between major versions. This is the most common source of friction people encounter with android after the initial setup.
Realistic timeline: a month of consistent engagement to build real confidence.
by lilywhite7387