Integrate Google Maps Places Autocomplete for hub address validation; update demo plan and Firebase configurations
This commit is contained in:
Achintha Isuru
@@ -1,7 +1,7 @@
|
||||
# KROW Workforce Platform — Feature Demo Plan for Milestone 3
|
||||
|
||||
**Version:** Milestone 3 (v3.0)
|
||||
**Date:** February 2, 2026
|
||||
**Date:** February 3, 2026
|
||||
**Audience:** Business Stakeholders, Customer Engineers, Sales Teams
|
||||
**Duration:** 25-30 minutes
|
||||
|
||||
@@ -28,33 +28,41 @@ This demo showcases the progress of the milestone 3.
|
||||
### Required Test Accounts
|
||||
|
||||
**Client Account (Business User):**
|
||||
- Email: `google_payment@gmail.com`
|
||||
- Email: `legendary@krowd.com`
|
||||
- Password: `Demo2026!`
|
||||
- Client Name: "Google Payements"
|
||||
- Client Name: "Krow"
|
||||
|
||||
**Staff Account (Worker):**
|
||||
- Phone: `+1 (555) 123-4567`
|
||||
- Phone: `+1 (555) 765-4321`
|
||||
- OTP Code: `123456` (demo mode)
|
||||
- Name: "Alex Martinez"
|
||||
- Name: "Mariana Torres"
|
||||
|
||||
### Prerequisites
|
||||
1. ✅ Both apps installed on demo devices (or simulators)
|
||||
2. ✅ Network connection stable
|
||||
3. ✅ Seed data is ready to be populated
|
||||
- the database should be empty.
|
||||
- remove unnecessary users from the firebase authetication.
|
||||
|
||||
### Pre-Demo Data Seeding
|
||||
|
||||
Tracked in :
|
||||
- https://github.com/Oloodi/krow-workforce/issues/345
|
||||
|
||||
- This should be easily populated and de-populated by the demonstrator to show the empty states in the apps.
|
||||
- At the start the database should be empty.
|
||||
- Commands to use:
|
||||
- `make dataconnect-clean`
|
||||
- To clean the database before seeding.
|
||||
- `make dataconnect-seed`
|
||||
- To populate the database with seed data for demo.
|
||||
|
||||
---
|
||||
|
||||
## 3️⃣ Demo Flows
|
||||
|
||||
**Note:**
|
||||
To start the demo you should clean the database running the next command:
|
||||
- make dataconnect-clean
|
||||
|
||||
### Demo 0: Show Empty Database
|
||||
**Purpose:** Demonstrate the starting point before any data exists
|
||||
**Action:** Show the empty database in Firebase console
|
||||
@@ -64,9 +72,9 @@ Tracked in :
|
||||
### Demo 1: Register Business & Show Empty States (Client App)
|
||||
**Purpose:** Show the client onboarding experience and empty states
|
||||
**Steps:**
|
||||
1. Open Client App → Tap "Create Account"
|
||||
2. Enter business details (email, password, company name)
|
||||
3. Complete sign up and navigate to home page
|
||||
1. Open Client App → Tap "Register"
|
||||
2. Enter business email, and password.
|
||||
3. Navigate to home page
|
||||
4. **Point out:** Empty dashboard, no orders, no workers, clean slate
|
||||
|
||||
---
|
||||
@@ -74,16 +82,18 @@ Tracked in :
|
||||
### Demo 2: Register Staff & Show Empty States (Staff App)
|
||||
**Purpose:** Show the worker onboarding experience and empty states
|
||||
**Steps:**
|
||||
1. Open Staff App → Tap "Sign Up"
|
||||
1. Open Staff App → Tap "Register"
|
||||
2. Enter phone number and verify with OTP code
|
||||
3. Complete profile setup wizard (skip detailed sections for speed)
|
||||
4. Navigate to home page
|
||||
5. **Point out:** Empty shifts list, no available work yet
|
||||
3. Navigate to home page
|
||||
4. **Point out:** Empty shifts list, no available work yet
|
||||
|
||||
---
|
||||
|
||||
> **🔄 PAUSE HERE:** Populate the database with seed data (run seeding script)
|
||||
|
||||
- Potulate database with the next comand :
|
||||
- make dataconnect-seed
|
||||
|
||||
---
|
||||
|
||||
### Demo 3: Client Logs In with Existing Account
|
||||
@@ -93,7 +103,7 @@ Tracked in :
|
||||
1. Restart Client App
|
||||
2. Tap "Sign In" button
|
||||
3. Enter credentials:
|
||||
- Email: `google_payment@gmail.com`
|
||||
- Email: `legendary@krowd.com`
|
||||
- Password: `Demo2026!`
|
||||
4. Tap "Sign In"
|
||||
|
||||
@@ -133,13 +143,13 @@ Tracked in :
|
||||
> ```
|
||||
>Client Posts Shift [O1]
|
||||
> ↓
|
||||
>*Vendor Accepts the Shift (This Part is missing for now)* [O2]
|
||||
>*Vendor Accepts the Shift (This Part is missing for now)/ Vendor is selected by client* [O2]
|
||||
> ↓
|
||||
>Worker Searches for a Shift [O3]
|
||||
> ↓
|
||||
>Worker Applies [O4]
|
||||
> ↓
|
||||
>Confirmation [O5]
|
||||
>Confirmation (This Part is missing for now, for now is confirmed)*[O5]
|
||||
> ↓
|
||||
>Worker Checks In [O6]
|
||||
> ↓
|
||||
@@ -157,12 +167,12 @@ Tracked in :
|
||||
- Order name: "Spring Gala 2026"
|
||||
- Date: [Select upcoming date]
|
||||
- Location: [Select existing hub]
|
||||
- Add position: Server, Count: 3, Hours: 5PM-11PM
|
||||
- Add position: Server, Count: 3, Hours: 5PM-9PM
|
||||
|
||||
---
|
||||
|
||||
### Demo 7: Client Views Order Details
|
||||
**Purpose:** Show detailed shift information and worker assignments
|
||||
**Purpose:** Show detailed shift information and worker assignments (this second part is missing for now)
|
||||
**Screen:** Orders Tab → Tap on any order card
|
||||
**Action:** Expand order to see full details
|
||||
|
||||
@@ -244,7 +254,7 @@ Tracked in :
|
||||
|
||||
---
|
||||
|
||||
### Demo 14: Staff Checks In to Shift (Day of Event) - [O6]
|
||||
### Demo 14: Staff Checks In to Shift (Day of Event) [O6]
|
||||
**Purpose:** Demonstrate the check-in process
|
||||
**Screen:** Home or My Shifts → Shift Card → "Check In" button
|
||||
**Action:** Simulate checking in to an active shift
|
||||
@@ -267,7 +277,7 @@ Tracked in :
|
||||
|
||||
---
|
||||
|
||||
### Demo 16: Staff Checks Out of Shift - [O7]
|
||||
### Demo 16: Staff Checks Out of Shift - - (this is under fixing)[O7]
|
||||
**Purpose:** Demonstrate the check-out process and shift completion
|
||||
**Screen:** Home or My Shifts → Shift Card → "Check Out" button
|
||||
|
||||
|
||||
Reference in New Issue
Block a user