15. Feature Build Plan
Order of implementation, aligned with the timeline above.
| Order | Feature Block | Features Included | Deliverable |
|---|---|---|---|
| 1 | Auth & project setup | F1.1–F1.7, project skeleton, DB, Alembic | Users can register (customer/provider), login, access protected routes |
| 2 | Provider profile & image | F2.1–F2.5, F2.7 optional; image storage (F2.2) | Provider can create/edit profile, add services, upload profile image |
| 3 | Business hours & availability | F2.6, F4.1–F4.5 | Provider sets hours; API returns available slots for a date |
| 4 | Bank connection | F3.1–F3.3 | Provider can connect Stripe Connect; status visible in UI |
| 5 | Booking flow (customer) | F5.1–F5.10 | Customer can find provider, choose service/date/slot, choose cash or card, complete booking |
| 6 | Payments (card) | F7.1–F7.5 | Card payments work; funds go to connected account; webhooks update booking |
| 7 | Appointments management | F6.1–F6.5, F6.7 | Both sides see appointments; cancel; status lifecycle |
| 8 | Reviews | F8.1–F8.4 | Customers can leave review after completion; displayed on profile |
| 9 | Polish & notifications | F9.1–F9.3, F10.1–F10.5 | Emails, responsive UI, error/loading states, basic SEO |