Automation index
How much of a Mobile developer’s job can AI already do?
A layout and a store listing come earlier. It not crashing on a real phone do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Mobile developer
28%
AI can already do 28% of this job.
#92 / 623
View rankingMobile developer
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Screens, API and offline state.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Store review, crashlytics and ANRs.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Real device, the notch and fragmented Android.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
CI, tests and the week's release.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the redesign and not breaking what people use.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it does not crash, and not ignoring the one-star.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- build apps
- ship to stores
- crashlytics
- offline state
- ANRs
- mobile tests
- fragmented Android
- store review
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2514
IS WORK OVER?
Valet
19%
#536 / 623
View rankingValet
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Tag, keys and the bay map.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Drive someone else’s, the tight car park and not marking it.EstimateNo public source provides a precise figure. This is our estimate. | 22% | 8% | +1.8 |
The client already out and the car still downstairs.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Insurance, the knock and who pays.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The event, the rain and not losing a key.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
No mark, and the car on time.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 12% | +1.7 |
| Total | 100% | 19% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- keep keys
- park others’ cars
- bay map
- not mark
- valet events
- knock insurance
- tight car park
- return on time
Sources for this job· O*NET 53-6021.00· ESCO/ISCO 8322