Kotlin first, then how an Android app fits together: activities, the lifecycle, and Jetpack Compose for the UI. Then build one small app from start to finish. The free roadmap at androidfeed.com lays this out stage by stage, and in a call we work out where you are on it and what you can skip.

Most student projects are similar to-do or weather apps. Pick one you've built and solve one real problem in it, like slow startup, working offline, or running AI on the device. Measure it before and after, then write up what you found. That's how I write about my own work at shubhamsinghbisht.com.

Send me your GitHub link and resume before the call. I go through what an interviewer sees first, what reads as weak, and the one change that will matter most. You leave with a short list of fixes.

Yes. We go through the Android and Kotlin topics that come up most, like the lifecycle, coroutines and app architecture. Then you practise explaining your own project clearly.

Students and early-career developers who want to get into Android, or to move from basic apps to harder, more interesting work. If you're further along, a call about one specific performance or architecture problem works too.