Architecture

E-Core follows a clean, layered architecture that promotes separation of concerns and testability.

Layer Overview

┌─────────────────────────────────────────┐
│           Presentation Layer            │
│         (UI, Widgets, Screens)          │
├─────────────────────────────────────────┤
│           Application Layer             │
│      (State, Providers, Notifiers)      │
├─────────────────────────────────────────┤
│             Domain Layer                │
│       (Entities, Use Cases)             │
├─────────────────────────────────────────┤
│              Data Layer                 │
│   (Repositories, Data Sources, DTOs)    │
└─────────────────────────────────────────┘

Package Responsibilities

Foundation

Core entities, value objects, and utilities shared across all layers.

State

Riverpod providers and notifiers for reactive state management.

Data

Repository implementations, data sources, and network/cache handling.

UI

Pre-built widgets and components following the design system.

Data Flow

1. User interaction triggers a UI event
2. Provider/Notifier handles the event and calls repositories
3. Repository coordinates data sources and returns domain entities
4. State updates propagate through Riverpod to rebuild UI

Learn More