Studio, Profilers & Firebase
BUILD & TOOLING › Delivery
Profiling, leak detection, baseline profiles, and Firebase tooling for diagnosing and shipping Android apps.
Interviewers use this topic to check whether you can diagnose real performance and stability problems instead of guessing. Expect questions on reading CPU/memory traces, catching leaks with LeakCanary, speeding up startup with baseline profiles, and wiring Firebase products like Crashlytics and Remote Config. They want to see you reach for the right tool and interpret what it reports.
What this covers
- Choosing the right profiler task: system trace, callstack sample, method trace, heap dump, or allocation tracking
- Profileable vs debuggable builds and why low-overhead profiling uses a release-based build
- How LeakCanary detects retained objects and reads a leak trace
- What baseline profiles do (AOT vs JIT) and how Macrobenchmark generates them
- Firebase setup mechanics: google-services.json, the Gradle plugin, and the Firebase BoM
- Firebase product roles: Crashlytics, Analytics, FCM, Remote Config, App Distribution
Study this topic
- Studio, Profilers & Firebase explained: the guided lesson
- 14 practice quiz questions
- 9 revision flashcards
- Studio, Profilers & Firebase interview questions and answers