Goal and prerequisites
Read the companion lesson and use the pinned PocketCook checkout. Work in your own learning branch. This exercise combines source reading with observable behavior; do not edit production credentials or upload conversations.
Source to inspect
Recipes.kt and docs/verification.md. Kotlin files live under app/src/main/java/com/androidengineers/pocketcook/; unit tests under app/src/test/java/com/androidengineers/pocketcook/, device tests under app/src/androidTest/java/com/androidengineers/pocketcook/.
Predict, run, explain
Use the seven-case table in the lesson. Define expected behavior before running each case, record model/device/route, and repeat at least two questions three times if live access is available. Classify each result as pass, fail or unverified. Add a camera design showing how stale frames are discarded and sharing stops when disabled.
./gradlew :app:testDebugUnitTest :app:lintDebug
Run commands from gemini-live/. Record the source revision, prediction, result and explanation. A test failing to compile is a setup problem, not the expected behavioral failure. If the device or provider is unavailable, state which checks remain unverified.
Reference reasoning and submission
Expected reasoning: these commands do not evaluate answers or acoustics. Live observations must be listed separately. No camera behavior can be tested in the baseline because camera sharing is absent. Deliver the sanitized evaluation sheet, a failure analysis, a camera design and one proposed next measurement. An honest unverified entry is preferable to fabricated evidence.
Self-check
Can another learner reproduce your result from your branch and notes? Can you name the responsible source method without reading the lesson? Have you separated local tests from actual device/provider evidence? Revisit the corresponding concept if any answer is no.
Course study guide · Hands-on codelab · Pinned Android source