Android Development

Android Performance Field Notes

Each module opens with a reproduced regression, then walks through capture, hypothesis, and verification. You keep a single engineering diary that becomes the spine of your final review.

4 weeks · sprint style

Sprint studios

KRW 334,000

Tuition is informational on this static preview. Enrollment confirmations arrive from staff after you schedule a call.

Schedule a call

Cover treatment for Android Performance Field Notes

Lead mentor

Noah Ibarra

Ex-retail scale Android lead; prefers teaching with annotated traces over slides.

What is inside

Perfetto slices narrated like incident notes
Allocation churn hunts with repeatable repro scripts
Cold start budgets with staged dependencies
Bitmap pipeline audits without magic numbers
StrictMode as a teaching ally, not a nuisance
Battery attribution drills using public APIs only
Release versus debug signal separation

Artifacts you ship

A regression brief with captured evidence
A startup budget table tied to modules
A mentor-signed performance retro

Cohort questions

Do I need physical devices?

One mid-tier device is recommended for thermal stories; otherwise cloud device minutes we provide cover basics.

Is JNI covered?

Only at the boundary where JNI skews metrics. Native rewrite workshops are not included.

Honest limitation?

We do not profile OEM-specific skins beyond publicly documented behaviors.

Notes from recent seats

“Cold start table alone changed how our squad sequences SDK init. Still wanted one more week on IO spikes.”

— Aya , Performance analyst · 4/5