Files

Achintha Isuru 6c72c2d9fd feat: Implement Staff Profile feature with BLoC architecture

- Added ProfileRepositoryInterface for staff profile operations.
- Created StaffProfileUI to represent extended profile information for the UI.
- Developed GetProfileUseCase to fetch staff profiles and map to UI entities.
- Implemented SignOutUseCase for user sign-out functionality.
- Introduced ProfileCubit to manage profile state and loading logic.
- Created ProfileState to represent various states of the profile feature.
- Developed ProfileNavigator for type-safe navigation within the profile feature.
- Built StaffProfilePage to display staff member's profile and statistics.
- Added various widgets for profile display, including reliability stats and menu items.
- Established StaffProfileModule for dependency injection and routing.
- Configured pubspec.yaml for feature package dependencies.

2026-01-24 14:25:17 -05:00

apps

fix(routes): update worker home route to worker main

2026-01-24 12:30:53 -05:00

packages

feat: Implement Staff Profile feature with BLoC architecture

2026-01-24 14:25:17 -05:00

.gitignore

Move apps to mobile directory structure

2026-01-22 10:17:19 -05:00

analysis_options.yaml

Centralize and update analysis options configuration

2026-01-22 12:19:05 -05:00

melos.yaml

Update mobile app docs and add gen:all Melos script

2026-01-22 12:06:07 -05:00

pubspec.lock

feat(client_coverage): add client coverage feature with user session data use case and dashboard widgets

2026-01-23 16:25:01 -05:00

pubspec.yaml

feat(staff): integrate staff_home feature

2026-01-24 12:11:25 -05:00

README.md

Update mobile app docs and add gen:all Melos script

2026-01-22 12:06:07 -05:00

README.md

KROW Workforce Mobile 📱

This folder holds the mobile app code for the KROW Workforce apps. This project uses Melos to manage multiple Flutter packages and applications.

📂 Project Structure

The project is organized into modular packages to ensure separation of concerns and maintainability.

apps/: Main application entry points.
- client: The application for businesses/clients.
- staff: The application for workforce/staff.
- design_system_viewer: A gallery of our design system components.
packages/: Shared logic and feature modules.
- features/: UI and business logic for specific features (e.g., Auth, Home, Hubs).
  - features/client: Client specific features.
  - features/staff: Staff specific features.
- design_system/: Shared UI components, tokens (colors, spacing), and core widgets.
- domain/: Shared business entities and repository interfaces.
- data_connect/: Data access layer (Mocks and Firebase Data Connect SDK).
- core_localization/: Internationalization using Slang.
- core/: Base utilities and common logic.

🚀 Getting Started

1. Prerequisites

Ensure you have the Flutter SDK installed and configured.

2. Initial Setup

Run the following command from the project root to install Melos, bootstrap all packages, and generate localization files:

# Using Makefile
make mobile-install
# Using Melos
melos bootstrap

3. Running the Apps

You can run the applications using Melos scripts or through the Makefile:

Client App

# Using Melos
melos run start:client -d android  # or ios
# Using Makefile
make mobile-client-dev-android

Staff App

# Using Melos
melos run start:staff -d android  # or ios
# Using Makefile
make mobile-staff-dev-android

🛠 Useful Commands

Bootstrap: melos bootstrap (Installs all dependencies)
Generate All: melos run gen:all (Localization + Code Generation)
Analyze: melos run analyze:all
Help: melos run info (Shows all available custom scripts)

🏗 Coding Principles

Clean Architecture: We strictly follow Domain-Driven Design and Clean Architecture.
Modularity: Every feature should be its own package in packages/features/. Client and staff specific features should be in their respective packages.
Consistency: Use the design_system package for all UI elements to ensure a premium, unified look.