Each skill is a few short lessons, then practice. You rate yourself at the start and again at the end.
Core to the job
Chapter 2
Android apps
Trace what an app screen must save when it closes
What you'll learn
Activity lifecycle
Compose state
Gradle build variants
Release signing
Practice
Trace the Android Activity Lifecycle15 min
Chapter 2
Building for phones
Plan how apps survive interruptions, lost signal and refused permissions
What you'll learn
Screen lifecycle
Work off screen
Asking permission
Working offline
Devices differ
Practice
Lay out one screen for three devices and a bigger text size30 min
Say what four interruptions do to one screen25 min
Decide what the platform will still run once the app is closed25 min
Chapter 4
Code quality
Review code for unclear names, then tidy a messy function
What you'll learn
Clear names
Single responsibility
Review the risk
Explain the reason
Proportionate change
Practice
Review Code for Quality Issues15 min
Chapter 4
Writing tests
Write tests for small functions, including odd and wrong inputs
What you'll learn
Testing pyramid
Behaviour test
Test isolation
Regression test
Practice
Write Test Cases for a Tip Calculator20 min
Chapter 4
Debugging
Use error messages to find bugs and explain your fixes
What you'll learn
Hypothesis before keyboard
Reliable reproduction
Root cause, not symptom
Narrow it down
Reading a stack trace
Practice
Find the Bug Using an Error Message10 min
Triage Five Bug Reports by Severity10 min
Chapter 6
Git
Save clear changes to a project's history and request review
What you'll learn
Change states
Short-lived branches
Merge conflict
Useful commit message
Pull request review
Practice
Rewrite 5 bad git commit messages15 min
6 more in the plan
App frameworksBuild and launch a small feature with an error screenCh 2
What you'll learn
Framework conventions
Component boundaries
State flow
Framework migration
Shared or native
Practice
Audit a mobile app for navigation patterns20 min
APIsCheck requests and replies between programs, and design clear onesCh 6
What you'll learn
API resource
HTTP status codes
API contract
Idempotent request
API style choice
Practice
Decide what the app does when the network drops20 min
CommunicationRewrite an update for two different readers, cutting extra linesCh 7
What you'll learn
Lead with the point
Match detail to the reader
Said versus heard
Specific feedback
Practice
Ask the Right Questions Before Estimating15 min
Working with othersContribute to group work, ask for help and credit teammatesCh 7
What you'll learn
Early team friction
Clear ownership
Challenge ideas, not people
Lead or follow
Practice
Navigate a Disagreement Without Damaging the Relationship20 min
Problem solvingTest each possible cause of a problem instead of guessingCh 8
What you'll learn
Problem vs symptom
Clean problem splits
Root cause
Deciding under uncertainty
Practice
Separate the Problem from the Symptom10 min
Adapting to changeTry a new tool and describe how you handled changeCh 8
What you'll learn
Change vs your response
The messy in-between
Not there yet
Real change vs a feeling
Your plan
Chapter by chapter.
12 chapters, in this order. Chapter 1 is free.
1~2 wks
See the work of an Android Developer
StartFree
2~2 wks
Build and ship Android apps
Skills
3~2 wks
Write up a system you built
Project
4~2 wks
Write tested readable code and fix bugs
Skills
51–2 wks
Talk to two working Android developers
People
6~2 wks
Connect software through APIs and track changes
Skills
7~2 wks
Make yourself understood across a team
Skills
8~2 wks
Solve problems when plans change
Skills
9~2 wks
Capstone: ship a feature by directing AI agents
Project
101–2 wks
Answer the questions interviewers ask
Interview
111–2 wks
Decide how you will get in
Decide
12on your timeline
Send your first applications
Apply
The job
What a Android Developer does
Builds and improves apps for Android phones, tablets, and watches so users get fast, reliable screens that follow Google's design and store rules. Focuses on one platform in depth, unlike a general mobile developer who splits time across both Android and Apple devices.
The work
Build app screens and flows with Jetpack Compose, Google's modern Android user interface (UI) toolkit
Write features in Kotlin using the Android software development kit (SDK)
Connect apps to web services and local storage to load and save data
Test on many Android phones and screen sizes to catch crashes and bugs
Profile memory, battery, and start-up time to keep the app smooth
Configure Gradle build files, app signing, and version settings for releases
Submit and update builds on the Google Play store and read crash reports
Work with designers and product teammates to plan and estimate features
A typical day
Check messages and crash reports, then plan a small set of tasks
Build a feature in Android Studio and run it on an emulator
Test the same screen on several real devices to spot layout issues
Join a short team sync to unblock work and confirm requirements
Review a teammate code change and update yours from the feedback
Prepare a signed build and push a release to Google Play
Tools
Languages: Kotlin, JavaUser interface toolkit: Jetpack Compose, Android Views, Material DesignFrameworks: Android SDK, Jetpack librariesIDE and build: Android Studio, GradleVersion control: Git, GitHub, GitLabTesting: JUnit, Espresso, emulatorsRelease and store: Google Play Console, FastlaneAnalytics and crash reports: Firebase Analytics, Crashlytics
Ways in
There is more than one route.
Ways to study
Computer science or software engineering degree or diploma
Android or mobile development bootcamp or intensive short course
Self-taught path using online Android courses plus a published-app portfolio
Apprenticeship or vocational program focused on software development
How people get their first job
Build and publish 1 to 2 Android apps to Google Play with clean code and a README portfolio
Apply for Android or mobile development internships and trainee roles
Start in software engineer roles and take Android-focused tasks
Contribute bug fixes to open source Android apps or Jetpack libraries
Complete a recognised Android developer course and ship a Kotlin project
How long does it take to become a android developer with Welica?
The plan is 12 chapters, 4–5 months at 15 to 30 minutes a day. You can go faster or slower; the plan moves with you.
Do I need a degree?
Not always. Common routes are computer science or software engineering degree or diploma, android or mobile development bootcamp or intensive short course, self-taught path using online Android courses plus a published-app portfolio, or apprenticeship or vocational program focused on software development.
What is free?
Chapter 1, See the work of an Android Developer, is free for good. Premium unlocks the rest of the plan.