Files

bwnyasse 554dc9f9e3 feat: Initialize monorepo structure and comprehensive documentation

This commit establishes the new monorepo architecture for the KROW Workforce platform.

Key changes include:
- Reorganized project into `frontend-web`, `mobile-apps`, `firebase`, `scripts`, and `secrets` directories.
- Updated `Makefile` to support the new monorepo layout and automate Base44 export integration.
- Fixed `scripts/prepare-export.js` for ES module compatibility and global component import resolution.
- Created and updated `CONTRIBUTING.md` for developer onboarding.
- Restructured, renamed, and translated all `docs/` files for clarity and consistency.
- Implemented an interactive internal launchpad with diagram viewing capabilities.
- Configured base Firebase project files (`firebase.json`, security rules).
- Updated `README.md` to reflect the new project structure and documentation overview.

2025-11-12 12:50:55 -05:00

6.1 KiB

Raw Blame History

Product Roadmap: KROW Platform Foundation (3-Month Plan)

Project Name: KROW - New Platform Foundation

Context: We are leveraging the validated visual prototype from Base44 to rebuild the KROW platform on a modern, scalable, and proprietary technical infrastructure. This ensures a smooth transition and provides clear visibility on delivered features.

3-Month Goal: To have a functional and autonomous first version of the KROW platform, including a web dashboard for event management and a mobile app for staff, all running on our new Google Cloud infrastructure.

Detailed Product Roadmap (Client/CEO View)

Phase 1: From Vision to Technical Foundation

Goal of the Phase (for the client): "We will transform your prototype into a concrete action plan. By the end of this phase, we will have a first version of the dashboard deployed where you can track our progress, and we will be fully independent to build and deploy future applications."

Visible Features Delivered at the End of Phase 1:

A Preview Web Dashboard (React):
- Description: A first version of the dashboard (based on the Base44 export) will be accessible via a private URL. Initially, the data will be static, but the visual interface will be live.
- What this means for the client: You will see the design and navigation of your dashboard come to life outside of Base44, on our own infrastructure.
A Foundation for the New Mobile Apps:
- Description: The skeletons of the new Flutter apps (Staff and Client) will be created, with a functional login system.
- What this means for the client: The foundations for the future apps will be ready, and we will have validated our ability to deploy them automatically to the app stores (TestFlight for Apple, Internal Testing for Google).
A Documented V1 API Contract:
- Description: A clear document that precisely describes how the frontend (web and mobile) will communicate with the backend. This is the "blueprint" of our system.
- What this means for the client: This guarantees that all parts of the KROW ecosystem (web, mobile, backend) will speak the same language, ensuring consistency and speed for future developments.

Technical Work Behind the Scenes (for the team):

Analysis of the Base44 code.
Setup of the infrastructure on Google Cloud (Cloud SQL, Firebase Auth, Data Connect).
Configuration of CI/CD pipelines for web (e.g., GitHub Actions) and mobile (e.g., CodeMagic).

Phase 2: The First Features Come to Life

Goal of the Phase (for the client): "You will start seeing your own data (events, staff) appear in the new dashboard. The staff mobile app will no longer be an empty shell but will display actual shifts. We are establishing a workflow that will allow you to continue prototyping in parallel with our development."

Visible Features Delivered at the End of Phase 2:

An Event Management Dashboard (Read-only):
- Description: The web dashboard will display the list of your events, hubs, and staff, reading the data directly from our new database. Create/edit functionalities will not be active yet.
- What this means for the client: You will be able to view your real operational data on the new interface, validating that our backend is correctly connected.
The Staff Mobile App (v2) Displays Real Shifts:
- Description: A staff member will be able to log into the new app and see the list of shifts they are assigned to, with basic details (date, location, role).
- What this means for the client: The synergy between the backend and the mobile app is proven. The foundation is ready to add interactive features.
An Established Design-to-Development Iteration Workflow:
- Description: We will have a clear process to "freeze" a version of the Base44 design for development, while giving you the freedom to work on the next version.
- What this means for the client: You can continue to innovate and prototype on Base44 without fear of disrupting the development team's work.

Technical Work Behind the Scenes:

Development of Data Connect queries to read data (listEvents, listStaff, etc.).
Integration of TanStack Query in the dashboard for data management.
Implementation of the service layer in the Flutter app to call the Data Connect SDK.

Phase 3: The First Complete Business Flow

Goal of the Phase (for the client): "By the end of this quarter, you will be able to perform a complete business action on the new platform: create a complex event on the web dashboard and instantly see the corresponding shifts appear on the staff mobile app."

Visible Features Delivered at the End of Phase 3:

A Complete Event Creation and Modification Flow on the Web Dashboard:
- Description: The event creation form will be fully functional. You will be able to create an event, add shifts, define positions with roles and rates, and assign contacts.
- What this means for the client: You are now autonomous in managing the core of your operations on the new platform. The Base44 prototype has been transformed into a functional production tool.
Synchronization Between Web and Mobile:
- Description: A shift created or modified on the web dashboard will be immediately (or almost immediately) visible and updated on the mobile app of the concerned staff member.
- What this means for the client: The vision of a unified and reactive ecosystem is now a tangible reality.
A Stabilized Platform Ready for Growth:
- Description: The technical foundation will have been tested, documented, and secured.
- What this means for the client: We have a solid foundation on which we can confidently build the more advanced features of your vision (KROW University, predictive AI, etc.).