u/Content-Jaguar-578

Hey everyone! 👋

Managing build health on multi-module Android and KMP projects can be a nightmare. I wanted a tool that would just tell me exactly what’s wrong with my architecture and build performance without taking hours to configure.

So I built Gradle Lighthouse.

You just add id("io.github.dev-vikas-soni.lighthouse") version "2.1.0" to your root build file, run ./gradlew lighthouseAudit, and it gives you a score out of 100 with actionable fixes.

What it scans for (20+ rules):

• Build Performance: Configuration Cache readiness, KAPT->KSP migration ROI, build caching, parallel execution, unused BuildConfig waste.
• Architecture Graph: DFS circular dependency detection, high coupling scores across modules.
• Dependencies: Unused dependencies, duplicate declarations, hardcoded versions.
• Quality & Security: Dark modules (0 test coverage), exposed signing config passwords, deprecated plugins.

I recently successfully audited the Now in Android app and the NutiSport KMP app to ensure it handles complex, enterprise-scale configuration caches perfectly. (Screenshots linked below!)

• [Screenshot: Terminal Dashboard on Now in Android] (Link your image here)
• [Screenshot: HTML Report on NutiSport KMP] (Link your image here)

It supports SARIF (for GitHub Security tab) and JUnit XML for easy CI/CD integration.

You can check out the source code and docs here: 
Repo: https://github.com/dev-vikas-soni/gradle-lighthouse

Would love for you guys to try it on your codebases and let me know your Lighthouse score or if you have any feature requests!

Android SDE2/SDE3 interviews have changed significantly in 2026.

Most candidates still prepare by memorizing:
- APIs
- lifecycle callbacks
- architecture definitions

But senior Android interviews now go much deeper.

One example:

StateFlow vs SharedFlow.

Interviewers rarely ask only:
“What’s the difference?”

Instead, they explore:
• replay behavior implications
• event delivery guarantees
• lifecycle-aware collection
• configuration change handling
• backpressure scenarios
• recomposition side effects
• architecture tradeoffs in production apps

The biggest difference between SDE1 and SDE3 candidates is usually this:

Junior candidates explain features.
Senior candidates explain failure modes, scalability, and engineering tradeoffs.

Over the past few weeks, I’ve been building a complete Android SDE2/SDE3 Interview Roadmap covering:
- Jetpack Compose internals
- Kotlin Coroutines & Flow
- Android System Design
- Performance Optimization
- Debugging Scenarios
- Modularization
- Architecture Deep Dives

The goal was to create the kind of Android interview preparation resource I wish existed for experienced Android engineers.

Would love feedback from fellow Android developers and mobile engineers.

#AndroidDevelopment #AndroidDev #JetpackCompose #Kotlin #SoftwareEngineering