# Fermenty App Development Process

> See `00_PROJECT_OVERVIEW.md` for the current state of all three surfaces.
> **Progress:** Step 1 (Create the API) — foundation done 2026-06-05 (Sanctum
> auth + `/v1` register/login/logout/me/dashboard). Feature endpoints pending.
> Step 2–3 (app subdomain + BETA web app consuming the API) not started.

## Terminology
- **web**: Current ERP system (erp.fermenty.es)
- **app**: Web-mobile BETA (app.fermenty.es or app.fermenty.local)
- **android app**: Final mobile app (Flutter/Dart)

## Workflow Steps

1. **Create the API**
   - Build RESTful endpoints in Laravel for all required features.
   - Test endpoints with Postman/Insomnia.

2. **Set Up the app Subdomain**
   - Configure `app.fermenty.es` on the server to point to a new frontend directory.
   - For local development, use `app.fermenty.local` and update the hosts file.

3. **Develop the BETA Web App**
   - Scaffold a simple HTML/CSS/JS (or Vue/React) project in the new directory.
   - Connect the frontend to the API endpoints.
   - Simulate mobile screens and flows.

4. **Test and Iterate**
   - Use the BETA web app to test all API flows and UX.
   - Fix issues before moving to mobile development.

5. **Translate to Android (Flutter/Dart)**
   - Use the tested API and flows as a reference for the mobile app.

## Notes
- The BETA web app serves as a bridge between backend and mobile development.
- Early testing helps catch bugs and UX issues before mobile implementation.
- The process is iterative—improve API and frontend as needed.

---
_Last updated: 2026-04-20_