Authentication
A clean sign-in flow as the entry point to the application.
Auth · Access controlArchitecture-focused build
Employee Attendance with clean architecture
An employee attendance application built as a production-grade architecture reference — strict data, domain, and presentation layers with authentication and service-locator dependency injection.
Clean Architecture
BLoC
Service locator
Inside the product
Attendance done with discipline
A focused domain executed with the same engineering standards I bring to larger products.
Data layer
Repositories and data sources isolated behind domain interfaces, with mappers for domain models.
Repositories · Data sourcesDomain layer
Entities, use cases, and business rules written in pure Dart with zero Flutter dependencies.
Use cases · EntitiesPresentation layer
Screens and widgets driven entirely by BLoC events and states.
Screens · BLoC · WidgetsService-locator wiring
Dependencies registered and resolved through a central service locator.
DI · Testable wiringBLoC state
Predictable, event-driven state with testable business logic.
BLoC · Events · TestsBuild facts
An architecture you can trust
Domain logic isolated from Flutter and from data sources.
BLoC keeps UI updates explicit and debuggable.
Service locator makes swapping implementations trivial.
The same structure scales directly to larger domains.
Your product could be next
Inherited a messy codebase?
I can restructure it around Clean Architecture without pausing feature delivery.