Portfolio and next steps

Four apps that cover the ground

Make each project easy to judge

• README with a one-line summary, screenshots or a short GIF, features, architecture diagram, libraries and why, how to run, and what you would improve.
• A Play Store link or a downloadable APK for the published app.
• Clean commits with clear messages; no API keys or keystores in the repository.
• At least a few unit tests and one UI test, plus CI running them (for example GitHub Actions).

Learn from real codebases

Google's open-source "Now in Android" app shows modern Android practices: Compose, modularisation, offline-first data, Hilt, testing and Baseline Profiles. Do not try to copy it all; read one feature end to end, then apply one idea in your own app. The official Android Developers site, the Android Developers blog and release notes help you stay current.

Next steps after this course

• Advanced Compose: animations, custom layouts, performance tuning.
• Modularisation: splitting a big app into feature and core modules.
• Security: encrypted storage, certificate pinning concepts, safe WebViews.
• Kotlin Multiplatform (KMP): share business logic (networking, data, rules) between Android, iOS and other platforms while keeping native UIs. Compose Multiplatform goes further and shares UI as well. Both are maturing quickly; check JetBrains' current documentation.

A 90-day plan

1. Days 1 to 30: build and polish the local data app with tests; write its README.
2. Days 31 to 60: build the API app with offline cache and the Firebase app; add CI.
3. Days 61 to 75: publish one app on the Play Store (start the closed test early).
4. Days 76 to 90: mock interviews (topics 2 and 3), DSA practice if targeting product companies, and start applying.

One focused hour a day is enough if you are consistent. Share progress on LinkedIn or a blog; explaining what you built is excellent interview practice, and recruiters notice it.

Common mistakes

• Starting many apps and finishing none.
• No screenshots or README, so reviewers skip the project.
• Committing secrets: rotate them immediately if this happens.
• Chasing every new library instead of mastering the core stack.