Foundation
- One programming language, functions, collections, async work and Git.
- HTTP, JSON, basic data modeling and debugging.
- Choose one starting platform: Kotlin/Compose for Android, Swift/SwiftUI for Apple, or Flutter/React Native for shared UI.
Build Software · Career guide
Mobile App Development
Build apps that remain useful on real phones: small screens, unreliable networks, limited battery and interrupted sessions.
Career snapshot
A work-pressure profile, not a personality score
Three dots never means ‘better.’ It only means this dimension appears more often in the work.
Coding
Mathematics
Systems depth
Investigation
Creativity / design
Communication
Production responsibility
What would I actually do?
The work behind the title
- Design navigation, state and touch interactions for a small screen.
- Connect APIs and local storage; handle offline use and retries.
- Handle lifecycle changes, permissions and device capabilities.
- Test accessibility, performance and failures on emulators and real devices.
- Review crashes, protect user data and prepare controlled releases.
Reality check
Finishing a tutorial and owning production consequences are different skills. The point is to see the gap, not hide it with hype.
You might enjoy this if…
Signals worth noticing
- You like seeing software respond in your hand.
- You enjoy investigating bugs that only appear on some devices.
- You care about both interaction details and reliable data.
You might dislike this if…
The uncomfortable part
- Device-specific behavior and slow builds exhaust your curiosity.
- You want every user to have the same screen and network.
- You dislike maintaining released software after the demo.
A realistic day
No day is identical, but the pressure may feel like this
This is a plausible mix of recurring tasks, not a scripted career fantasy.
Reproduce a crash after the app resumes from the background.
Build an offline state and discuss its wording with design.
Review tests and check a release candidate on two screen sizes.
What should I learn?
A layered sequence, not a technology dump
Core
- State, navigation, lifecycle and accessible touch targets.
- Local persistence, loading/error/empty states and API contracts.
- Native and cross-platform are choices, not levels; check device/tooling access before choosing.
Practical
- Build a small offline reading list and restore it after restart.
- Test lost connectivity, denied permissions and interrupted sessions.
- Check screen-reader labels and larger text on a real device when available.
Later
- Performance profiling, background work and native integrations.
- Secure storage, observability and release automation.
- Learn a second platform only when a role or user need justifies it.
What not to learn yet
Not yet—because sequence matters
- Learning Kotlin, Swift, Dart and React Native simultaneously.
- A super-app, payments or a custom architecture framework for your first project.
- Buying hardware or paying store fees before checking the official tooling and distribution requirements.
Future You says
‘Later’ does not mean useless. It means you will learn it faster once you have a real problem for it.
AI & this career
Task Automation Exposure
This is not a replacement probability. Capabilities will change, so separate tasks, judgment and responsibility.
Routine screen scaffolding
AI can draft familiar layouts quickly, but may use obsolete APIs or ignore lifecycle behavior.
Student response: Read current platform docs and explain each state transition before keeping generated code.
Device and network debugging
Suggestions help, but a plausible explanation is not a reproduced crash.
Student response: Capture a minimal reproduction, logs and a regression test without exposing user data.
Release safety and user trust
Permissions, data handling and rollout decisions need accountable human judgment.
Student response: Practice permission minimization, accessible flows and a rollback plan.
Curated learning resources
Start with one platform
Resource count is not progress. Finish the recommended scope and build something.
Platform alternatives: use the reference for your chosen stack. These are not consecutive learning levels; you do not need all of them.
Android Basics with Compose
An official learning sequence that connects language basics with real app behavior and tests.
Do this much: Start with Kotlin and the first interactive app; then state and navigation. Choose this branch for Android, not alongside every other mobile stack.
Last reviewed:
Get started with React Native
Explains the supported starting workflow without pretending cross-platform removes native constraints.
Do this much: Use if you already know JavaScript/React; read the framework and environment choices, then implement one screen. Check optional service costs separately.
Last reviewed:
Flutter documentation
A maintained starting point for the Flutter branch, with platform-specific setup made explicit.
Do this much: Pick your available target device, check setup and learn Dart/widgets/state for one small app. Paid hosted tools are unnecessary for this exercise.
Last reviewed:
Develop in Swift
Official Swift and Apple-platform guidance instead of mixing outdated tutorials.
Do this much: Check tooling requirements first, then build one view and state transition. Tutorials are free; hardware and distribution may have costs.
Last reviewed:
Next choices
What evidence will you gather next?
Turn this direction into an internship or junior-role plan →
Nearby directions
From skills to a destination
Where could you take this?
The career roadmap explains what to learn. A goal guide helps you put those skills to work. Start with one—not every route at once.