How sanogueralorenzo/android-kotlin-clean-architecture works
Project type and purpose
• This is a multi-module Android project demonstrating Clean Architecture and dynamic feature modularization.
• It hosts two consumable apps:
• “Amiga App” (in app/) – a feature-modularized wellbeing/calendar app
• “Sample Giphy App” (in sample/) – a reference app showing paginated Giphy search/trending.
• It shares cross-cutting modules under common/ (views, network, cache, resources), plus navigation (reflection-based router) and a small usermanager library.
File structure
• Top-level modules:
• app/ – the base Android application (Amiga), configured for dynamic features
• sample/ – standalone sample app demonstrating Clean Arch and networking
• common/ – reusable libraries (cache, network, views, resources)
• navigation/ – core Navigator, dynamic-install support, feature routing
• features/ – Android dynamic-feature modules (home, onboarding, profile) for the Amiga app
• libs/usermanager/ – simple user-management library
• Build scripts and Gradle configs orchestrate dependencies and dynamic-feature wiring.
• Detekt, lint.xml, proguard, legal/, and CI workflows support quality and publishing.
README for additional insights
• The README stresses:
• RUDT principles (Read, Update, Debug, Test)
• Clean Architecture (layered code + feature modules)
• DI experimentation (Dagger Hilt, Koin)
• Custom navigation without compile-time coupling
• Shared “common” modules