- Introduced the Krow Platform System Bible detailing the executive summary, system vision, ecosystem overview, architecture, application responsibilities, use cases, and security model.
- Created a detailed use case overview for the Krow Web Application, outlining workflows for Admin, Client, and Vendor roles.
- Established non-negotiable agent development rules for mobile applications, emphasizing file structure, naming conventions, logic placement, localization, and error handling.
- Defined architecture principles for the Krow mobile platform, focusing on clean architecture, dependency direction, and session management.
- Documented design system usage guidelines to ensure UI consistency and adherence to design tokens across applications.
- Introduced comprehensive testing plan for Milestone 3 in m3-client-note.md
- Documented feedback and suggestions from demo sessions in m3-notes.md
- Created detailed demo flow for Milestone 3 in m3.md, outlining user interactions and expected outcomes
- Added planning tasks for Milestone 4 in m4-planning.md, covering backend and frontend development tasks, research, and business tasks
This commit addresses several critical issues across the mobile monorepo:
1. Centralized Error Handling: Integrated DataErrorHandler mixin into all repository implementations, ensuring consistent mapping of Data Connect exceptions to domain AppExceptions.
2. Build Stabilization: Fixed numerous type mismatches, parameter signature errors in widgets (e.g., google_places_flutter itemBuilder), and naming conflicts (StaffSession, FirebaseAuth).
3. Code Quality: Applied 'dart fix' across all modified packages and manually cleared debug print statements and UI clutter.
4. Mono-repo alignment: Standardized Data Connect usage and aliasing ('dc.') for better maintainability.
Signed-off-by: Suriya <suriya@tenext.in>
- Added CoverageWorker entity to represent worker status and check-in information.
- Updated CoverageRepositoryImpl to utilize CoverageWorker and its status.
- Removed legacy coverage_entities.dart file and replaced references with krow_domain imports.
- Enhanced coverage statistics calculations based on new worker status logic.
- Updated UI components to reflect changes in worker status representation.
- Modified acceptance of shifts to align with new status definitions.
- Cleaned up QA testing checklist to remove outdated items and clarify requirements.
Updated Makefile, mobile.mk, and melos.yaml to centralize mobile app build, start, and code generation commands using Melos scripts. Added info and install-melos commands for easier onboarding and workspace setup. Documentation updated to reflect staff app naming and new command structure.
This commit introduces a comprehensive document outlining the
KROW Workforce Platform project, covering vision, architecture,
domain logic, feature gap analysis, and development strategy.
The document serves as a central source of truth for team
onboarding and sprint planning, ensuring alignment and
consistency across the project. It details the migration from
a legacy system to a new GCP-based architecture using Firebase
Data Connect, Cloud Functions, and Cloud SQL.
Key aspects covered include:
- Project vision and business value proposition
- System architecture and technology stack comparison
- Core domain logic and entity definitions
- Feature gap analysis between legacy and prototype apps
- Data Connect schema evolution and development strategy
- Definition of Done (DoD) for features and sprints
The document also includes appendices with entity relationship
summaries, status enum references, and key file locations.
feat(internal/launchpad): add iframe viewer for prototypes and update links loader
This commit introduces an iframe viewer in the launchpad to display prototypes directly within the application. It also updates the links loader to handle prototype links differently, opening them in the iframe instead of a new tab.
The contributing guide has been updated to include a list of required development tools and recommended IDE setup, ensuring that contributors have the necessary tools to work on the project.
This commit introduces a new document explaining how to synchronize visual prototypes and POCs into the monorepo.
It also adds a script to automate the process of building and copying the prototype files into the `internal/launchpad/prototypes/web/` directory.
The documentation explains the benefits of synchronizing prototypes, the prerequisites, and the steps to synchronize them.
The script automates the process of installing dependencies, building the web application, and copying the resulting `dist/` folder into the `internal/launchpad/prototypes/web/` directory.
This allows developers to easily synchronize prototypes and make them available for local preview and deployment.
This commit restructures the monorepo to improve organization,
maintainability, and scalability. The changes include:
- Moving mobile apps from `mobile-apps/` to `apps/mobile-*`.
- Moving the web dashboard from `admin-web/` and `frontend-web/`
to `apps/web-dashboard/`.
- Moving Firebase-related files to the root `firebase/` directory.
- Adding a `.geminiignore` file to exclude unnecessary files from
Gemini analysis.
- Updating `.gitignore` to reflect the new structure and exclude
sensitive files.
- Updating `codemagic.yaml` to reflect the new app locations.
- Adding a `make help` command to the root directory.
- Adding a `make install-git-hooks` command to install git hooks.
- Adding a `docs/02-codemagic-env-vars.md` file to document
Codemagic environment variables.
- Adding a `docs/03-contributing.md` file to document
contribution guidelines.
- Adding prototype placeholders to the internal launchpad.
- Updating the `README.md` file to reflect the new structure and
provide updated instructions.
These changes improve the overall structure of the monorepo and
make it easier to develop, maintain, and scale the KROW Workforce
platform.
This commit introduces a new document, `docs/01-backend-api-specification.md`, which outlines the backend API specification for the KROW Workforce platform. This document serves as a reference for the development of the backend using Firebase Data Connect and Cloud Functions, replacing the Base44 backend. It includes details on authentication, data API, services API, security, migration notes, and implementation priority.
feat: remove obsolete documentation files
This commit removes several obsolete documentation files that are no longer relevant to the project. The removed files include:
- `docs/01-product-functional-roadmap.md`: This file contained the product roadmap, which is now outdated.
- `docs/02-architecture-overview.md`: This file provided an overview of the architecture, which has been superseded by more recent documentation.
- `docs/03-backend-api-specification.md`: This file contained the backend API specification, which has been replaced by `docs/01-backend-api-specification.md`.
- `docs/04-strategy-technical-roadmap.md`: This file outlined the technical roadmap, which is now outdated.
- `docs/05-project-plan.md`: This file contained the project plan, which is no longer current.
- `docs/06-maintenance-guide.md`: This file provided a maintenance guide, which is no longer applicable.
- `docs/07-reference-base44-api-export-v3.md`: This file contained a reference to the Base44 API export, which is no longer needed.
chore: remove obsolete documentation files
This commit removes several documentation files that are no longer
relevant or have been superseded by other documentation. Removing
these files helps to keep the repository clean and organized.
The following files were removed:
- `docs/07-reference-base44-api-export.md`
- `docs/08-reference-base44-prompts.md`
- `docs/09-sred-tracking.md`
- `docs/10-development-conventions.md`
- `docs/flows/vendor-flow.md`
- `docs/issues/template.md`
- `docs/prompts/create-codemagic-monorepo.md`
- `docs/prompts/create-full-architecture-diagram-flutter.md`
- `docs/prompts/create-mermaid-be-diagrams-flutter.md`
- `docs/prompts/create-mermaid-overview-flutter.md`
- `docs/prompts/create-mermaid-usecase-flutter.md`
This commit adds two new documentation files:
- `docs/03-backend-api-specification-v3.md`: This document defines the backend API to be built on the Firebase/GCP ecosystem, replacing the Base44 backend. It is based on the comprehensive Base44 API documentation (v3.0) and will guide the development of the new backend using Firebase Data Connect and Cloud Functions.
- `docs/07-reference-base44-api-export-v3.md`: This document provides complete API specifications for all entities, SDK methods, and integration endpoints of the KROW Workforce platform built on Base44.
