If you want to know which Android frameworks are worth your time, job postings will tell you more than any opinion piece ever will.
That’s why I searched Google Jobs for "Android developer", went through every posting the pagination would show me (177 in all), and logged every framework or library mentioned. “Required” frameworks got tagged as required. Anything in a "preferred," "nice to have," or "bonus" section got tagged as nice to have.
What came out is a pretty clear picture of what the market actually wants in 2026. Not what Medium writers think is cool, not what conference talks are hyping, but what's sitting in real job descriptions that real companies wrote when they needed to hire someone.
Most of it confirmed what I'd expect. A few things didn't.
First, the data
Here's the full breakdown across all 177 postings. Each framework is ranked by its Demand Score, calculated as ((required mentions × 2) + (nice to have mentions × 1)) / (177 × 2), expressed as a percentage. The weighting is intentional: a framework that 20 companies require tells you more than a framework that 20 companies list as a bonus.
| Framework | Total Mentions | Required | Nice to Have | Required % | Demand Score |
|---|---|---|---|---|---|
| Room | 29 | 22 | 7 | 76% | 14.4% |
| Jetpack Compose | 26 | 22 | 4 | 85% | 13.6% |
| Coroutines | 21 | 15 | 6 | 71% | 10.2% |
| Espresso | 21 | 15 | 6 | 71% | 10.2% |
| RxJava | 18 | 17 | 1 | 94% | 9.9% |
| Android Jetpack | 18 | 16 | 2 | 89% | 9.6% |
| JUnit | 19 | 14 | 5 | 74% | 9.3% |
| Retrofit | 13 | 10 | 3 | 77% | 6.5% |
| Dagger | 11 | 9 | 2 | 82% | 5.6% |
| Hilt | 11 | 8 | 3 | 73% | 5.4% |
| Firebase | 11 | 7 | 4 | 64% | 5.1% |
| ViewModel | 10 | 8 | 2 | 80% | 5.1% |
| React Native | 9 | 8 | 1 | 89% | 4.8% |
| Flutter | 6 | 6 | 0 | 100% | 3.4% |
| LiveData | 7 | 5 | 2 | 71% | 3.4% |
| KMP | 7 | 3 | 4 | 43% | 2.8% |
| Kotlin Flow | 6 | 4 | 2 | 67% | 2.8% |
| Google Analytics | 6 | 3 | 3 | 50% | 2.5% |
| Google Play Services | 4 | 4 | 0 | 100% | 2.3% |
| Cucumber | 4 | 4 | 0 | 100% | 2.3% |
| Android Architecture Components | 4 | 3 | 1 | 75% | 2.0% |
| Xamarin | 4 | 3 | 1 | 75% | 2.0% |
| Leanback (TV) | 4 | 3 | 1 | 75% | 2.0% |
| OkHttp | 4 | 3 | 1 | 75% | 2.0% |
| Koin | 3 | 3 | 0 | 100% | 1.7% |
| Robolectric | 4 | 2 | 2 | 50% | 1.7% |
| MockK | 3 | 3 | 0 | 100% | 1.7% |
| Mockito | 3 | 2 | 1 | 67% | 1.4% |
| Gson | 3 | 2 | 1 | 67% | 1.4% |
| Appium | 3 | 2 | 1 | 67% | 1.4% |
| Dagger 2 | 3 | 1 | 2 | 33% | 1.1% |
1. The non-negotiable frameworks
These are the frameworks you need on your resumé before anything else. Not because they're the most exciting, but because their absence is a red flag.
Room topped the list with a demand score of 14.4% and appeared as required in 76% of the jobs that mentioned it. If you're storing local data and you're not using Room, interviewers will notice.
Jetpack Compose was right behind it at 13.6%, and when it appeared, 85% of jobs listed it as required. That number is the closest thing to a definitive signal in this dataset: the industry has mostly moved on from XML layouts. You don't have to love Compose (plenty of people don't), but you need to know it.
Coroutines and Espresso both landed at 10.2%. Coroutines is table stakes for anything async in modern Android. Espresso showing up this high means companies aren't just saying they care about testing, they're screening for it.
2. The differentiators
Get the non-negotiables right and you're through the door. The next frameworks are what separate a mid-level resumé from a senior one.
Retrofit appeared in 13 postings with a 77% required rate and a demand score of 6.5%. If you've built anything that talks to an API - which is basically everything - Retrofit belongs on your resumé.
Dependency injection is where it gets interesting. Dagger and Hilt appeared in 11 postings each. Dagger had a slightly higher required rate (82% vs 73%), but "Dagger 2" specifically showed only a 33% required rate, which tells you something. The explicit "Dagger 2" label is showing up mostly in older job descriptions that haven't been updated. Hilt is where the ecosystem is heading, but Dagger's fundamentals underpin it. Learn Hilt, understand Dagger, and you can speak intelligently to both.
Firebase is also worth having. It appeared in 11 postings, but only 64% listed it as required - the lowest required rate among frequently-mentioned frameworks. That puts it in "expected familiarity" territory rather than "deep expertise." You don't need to have built a production app on Firebase at scale, but you should know your way around it.
3. Read the room
Some frameworks are worth learning. Others are worth using as a filter.
RxJava is the most interesting data point in this whole dataset. It had the highest required rate of any framework: 94%. When a job lists RxJava, they really mean it. But it only appeared in 18 postings, trailing Coroutines' 21.
That gap tells a story. Greenfield projects in 2026 are overwhelmingly using Coroutines. But a large chunk of Android codebases out there were written when RxJava was the answer to everything, and those apps aren't getting rewritten anytime soon. When you see RxJava in a job description, you're almost certainly looking at a big, old, successful app - which might be exactly what you want, or might not be.
Same goes for Dagger 2, ButterKnife, and Volley. These aren't signs of a bad team. They're signs of a mature codebase with real users, technical debt, and probably a lot of institutional knowledge to absorb. If that sounds appealing, great. If you want to build on the latest stack from day one, these are useful signals to filter on.
4. The forward bets
The market isn't fully there yet, but the direction is pretty clear.
KMP (Kotlin Multiplatform) appeared in 7 postings, but only 43% listed it as required, the lowest required rate of any multiplatform tool. Compare that to Flutter (100% required when mentioned) and React Native (89%). Right now, KMP is more of a "nice if you know it" than a hard requirement.
That will change. The companies listing KMP today are the ones building the codebases that will be mainstream in a few years. Getting familiar with it now is low cost and high upside. You don't need to be an expert, but having a side project or two using KMP is worth the line on your resume.
Kotlin Flow is in a similar spot, mentioned in 6 postings, 67% required. It's the modern complement to Coroutines and will become harder to avoid as more codebases migrate away from LiveData and RxJava. If you already know Coroutines, learning Flow is a natural next step and takes maybe a weekend.
The priority list
If you were rebuilding your Android resumé from scratch today:
- Room, Jetpack Compose, Coroutines — these are must-haves
- Espresso, JUnit — add these even if the job post doesn't mention them
- Retrofit, Hilt — the differentiators that signal you've built real things
- Firebase — know it well enough to be comfortable; don't need to be an expert
- Kotlin Flow, KMP — future-proof additions worth investing a few weekends in
- RxJava — worth knowing the basics; how hard you go depends on what kind of jobs you're targeting
And once you land the job and start shipping code, you'll want good error monitoring in place. Rollbar works well for Android, catches crashes and exceptions in real time, and gives you not only the stack traces, but helps you fix the underlying issue. Worth having set up before your first production incident, not after. Sign up for free today.
