How arisguimera/firebaselogin works
Project Type and Purpose
• This is an Android mobile application module (“app”) following Clean-Architecture and MVVM.
• Purpose: four-screen flow for user introduction, login, sign-up, and email-verification, backed by Firebase Auth & Realtime Database, with reactive data streams (LiveData, Flow/StateFlow), DI (Hilt), Coroutines, and reusable UI components.
File-Structure Analysis
• Top-level: single Android module (“app”) with Gradle scripts, Google services, proguard, resources, manifests.
• Source packages under app/src/main/java/com/aristidevs/nuwelogin:
• core: application-wide utilities (Event, delegates, dialog launchers, extensions).
• data: network layer (AuthenticationService, FirebaseClient, UserService) + response models.
• domain: business-logic UseCase classes (Login, CreateAccount, SendEmailVerification, VerifyEmail).
• ui: screen Activities + ViewModels + ViewState + UI models, grouped by feature (introduction, login, signin, verification).
• Resources: layouts, drawables, fonts, styles for UI (ConstraintLayout-based, Lottie animations).
README Insights
• Architecture: Clean Architecture + MVVM + SOLID.
• Tech STACK: Kotlin Coroutines, LiveData, Flow/StateFlow, Dagger Hilt for DI, Firebase Auth & Realtime DB, Lottie.
• Activities vs. Fragments: four independent Activities for separation of concerns.
• Reusable UI components under core/dialog and core/delegate.