365 lines
8.0 KiB
Markdown
365 lines
8.0 KiB
Markdown
# CampReg Mobile Experience Specification
|
||
|
||
**Version:** 0.1
|
||
**Date:** 2026-06-01
|
||
|
||
---
|
||
|
||
## 1. Mobile Principle
|
||
|
||
Mobile is required. It is not a secondary or reduced experience.
|
||
|
||
Parents are often discovering camps, registering, paying, completing forms, and responding to reminders from their phones. Staff are operating camp away from desks, during drop-off, pickup, activities, field trips, and emergencies.
|
||
|
||
The mobile experience must be designed around real-world camp moments, not simply a responsive version of desktop screens.
|
||
|
||
---
|
||
|
||
## 2. Mobile User Types
|
||
|
||
## 2.1 Parent / Guardian
|
||
|
||
Parents use mobile to:
|
||
|
||
- Search for camps
|
||
- Compare camps
|
||
- Save camps
|
||
- Register children
|
||
- Pay
|
||
- Complete forms
|
||
- Upload documents
|
||
- Sign waivers
|
||
- Manage waitlists
|
||
- Receive messages
|
||
- Update authorized pickups
|
||
- View schedules
|
||
- Respond to urgent updates
|
||
|
||
## 2.2 Staff / Counselor
|
||
|
||
Staff use mobile to:
|
||
|
||
- View rosters
|
||
- Check campers in
|
||
- Check campers out
|
||
- Verify authorized pickups
|
||
- View emergency contacts
|
||
- View medical/allergy flags based on permissions
|
||
- Record attendance
|
||
- Add notes
|
||
- Report incidents
|
||
- Receive operational alerts
|
||
- Communicate with admins
|
||
|
||
## 2.3 Provider Admin
|
||
|
||
Provider admins use mobile to:
|
||
|
||
- View enrollment status
|
||
- Send urgent communications
|
||
- Monitor attendance
|
||
- Check underfilled sessions
|
||
- Review leads
|
||
- Approve growth campaigns
|
||
- Manage urgent parent/provider issues
|
||
|
||
---
|
||
|
||
## 3. Parent Mobile Requirements
|
||
|
||
## 3.1 Mobile Camp Discovery
|
||
|
||
Required:
|
||
|
||
- Location search
|
||
- Category search
|
||
- Date filters
|
||
- Age filters
|
||
- Price filters
|
||
- Availability filters
|
||
- Saved camps
|
||
- Comparison view
|
||
- Map/list toggle where relevant
|
||
- Camp detail pages
|
||
- Registration call-to-action
|
||
|
||
## 3.2 Mobile Registration
|
||
|
||
Required:
|
||
|
||
- Account creation/login
|
||
- Family profile creation
|
||
- Child profile creation
|
||
- Session selection
|
||
- Multi-child registration
|
||
- Form completion
|
||
- Document upload from camera/files
|
||
- Waiver review and signature
|
||
- Payment checkout
|
||
- Confirmation page
|
||
- Outstanding task checklist
|
||
|
||
## 3.3 Mobile Parent Portal
|
||
|
||
Required:
|
||
|
||
- Dashboard of upcoming camps
|
||
- Registration status
|
||
- Payment balance
|
||
- Invoice/payment history
|
||
- Outstanding forms
|
||
- Uploaded documents
|
||
- Authorized pickup management
|
||
- Emergency contact management
|
||
- Waitlist status
|
||
- Provider messages
|
||
- Announcements
|
||
- Calendar view
|
||
|
||
## 3.4 Mobile Notifications
|
||
|
||
Required channels:
|
||
|
||
- Email
|
||
- SMS
|
||
- Portal notifications
|
||
- Push notifications when PWA/native supports them
|
||
|
||
Required notification types:
|
||
|
||
- Registration confirmation
|
||
- Payment confirmation
|
||
- Failed payment
|
||
- Form reminder
|
||
- Waitlist opening
|
||
- Schedule change
|
||
- Urgent provider announcement
|
||
- Pickup authorization update
|
||
- Camp start reminder
|
||
|
||
---
|
||
|
||
## 4. Staff Mobile Requirements
|
||
|
||
## 4.1 Staff Home Screen
|
||
|
||
Required:
|
||
|
||
- Today’s sessions
|
||
- Assigned groups
|
||
- Attendance status summary
|
||
- Urgent alerts
|
||
- Quick check-in/check-out access
|
||
- Incident report shortcut
|
||
- Message/admin contact shortcut
|
||
|
||
## 4.2 Roster View
|
||
|
||
Required:
|
||
|
||
- Session roster
|
||
- Group roster
|
||
- Search campers
|
||
- Filter by status
|
||
- Attendance indicators
|
||
- Pickup status indicators
|
||
- Medical/allergy icons where allowed
|
||
- Emergency contact shortcut
|
||
|
||
## 4.3 Check-In
|
||
|
||
Required:
|
||
|
||
- Fast camper lookup
|
||
- Session roster check-in
|
||
- Bulk check-in when appropriate
|
||
- Individual check-in
|
||
- Late arrival status
|
||
- Notes
|
||
- Staff attribution
|
||
- Timestamp
|
||
- Audit log
|
||
|
||
## 4.4 Check-Out
|
||
|
||
Required:
|
||
|
||
- Authorized pickup list
|
||
- Pickup person verification
|
||
- Optional photo/ID note
|
||
- Check-out timestamp
|
||
- Staff attribution
|
||
- Early pickup note
|
||
- Unauthorized pickup warning
|
||
- Parent notification option
|
||
|
||
## 4.5 Emergency Access
|
||
|
||
Required:
|
||
|
||
- Emergency contact access
|
||
- Medical/allergy flags based on permission
|
||
- Important notes
|
||
- Provider emergency instructions
|
||
- Offline/degraded access plan for roster/emergency basics
|
||
|
||
## 4.6 Incident Reporting
|
||
|
||
Required:
|
||
|
||
- Camper selection
|
||
- Incident type
|
||
- Severity
|
||
- Description
|
||
- Action taken
|
||
- Staff notes
|
||
- Parent notification status
|
||
- Photo upload where appropriate
|
||
- Admin review status
|
||
|
||
## 4.7 Staff Communication
|
||
|
||
Required:
|
||
|
||
- Receive announcements
|
||
- Session-specific operational messages
|
||
- Admin-to-staff notifications
|
||
- Urgent alerts
|
||
- Task assignments
|
||
|
||
---
|
||
|
||
## 5. Mobile Technical Strategy
|
||
|
||
## 5.1 Responsive Web Foundation
|
||
|
||
The first implementation should be mobile-responsive web for all core flows.
|
||
|
||
Required responsive support:
|
||
|
||
- Parent discovery
|
||
- Parent registration
|
||
- Parent portal
|
||
- Provider admin essentials
|
||
- Staff roster
|
||
- Staff attendance
|
||
- Check-in/check-out
|
||
|
||
## 5.2 Progressive Web App
|
||
|
||
The PWA layer should support:
|
||
|
||
- Home screen installation
|
||
- Cached shell
|
||
- Fast loading
|
||
- Push notifications where supported
|
||
- Offline-friendly roster data
|
||
- Background sync where possible
|
||
|
||
## 5.3 Native App Consideration
|
||
|
||
Native apps may become required if the product needs:
|
||
|
||
- Reliable push notifications across all devices
|
||
- Camera-heavy QR scanning
|
||
- Strong offline check-in/check-out
|
||
- Staff field operations
|
||
- App store presence for parent trust
|
||
|
||
Native app should be considered after core workflows are validated, unless provider sales require it earlier.
|
||
|
||
---
|
||
|
||
## 6. Mobile UX Requirements
|
||
|
||
Required UX principles:
|
||
|
||
- Large touch targets
|
||
- Minimal typing
|
||
- Fast repeat actions
|
||
- One-handed staff workflows
|
||
- Clear status indicators
|
||
- Immediate confirmation feedback
|
||
- No hidden critical actions
|
||
- Accessible contrast and typography
|
||
- Avoid dense tables on mobile
|
||
- Use cards, lists, filters, and search
|
||
- Graceful error handling
|
||
- Clear offline/degraded warnings
|
||
|
||
---
|
||
|
||
## 7. Real-World Scenarios To Design Around
|
||
|
||
### Scenario 1: Parent Registers From Phone
|
||
|
||
A parent discovers a soccer camp during lunch, creates a child profile, registers, pays a deposit, signs the waiver, and receives confirmation without needing a desktop computer.
|
||
|
||
### Scenario 2: Morning Drop-Off
|
||
|
||
A staff member checks in 80 children in 20 minutes using a mobile roster. The interface must be fast, forgiving, and clear.
|
||
|
||
### Scenario 3: Pickup Change
|
||
|
||
A parent updates an authorized pickup person from their phone. Staff see the updated pickup list at checkout.
|
||
|
||
### Scenario 4: Waitlist Opening
|
||
|
||
A parent receives a waitlist opening on mobile, accepts, pays, and completes registration before the spot expires.
|
||
|
||
### Scenario 5: Urgent Weather Message
|
||
|
||
A provider sends an urgent weather update to all families in a session from mobile.
|
||
|
||
### Scenario 6: Medical Awareness
|
||
|
||
A staff member with appropriate permission sees that a camper has a severe allergy flag during attendance. Staff without permission only see operationally necessary alerts.
|
||
|
||
### Scenario 7: Field Trip Connectivity Problem
|
||
|
||
Staff need access to rosters and emergency contacts even with weak connectivity. The app should support cached emergency-critical information when allowed.
|
||
|
||
---
|
||
|
||
## 8. Mobile Acceptance Criteria
|
||
|
||
The mobile experience is acceptable when:
|
||
|
||
- Parents can complete registration and payment on a phone.
|
||
- Staff can complete check-in/check-out on a phone.
|
||
- Staff can verify authorized pickups on a phone.
|
||
- Emergency contacts are reachable from staff mobile views.
|
||
- Sensitive information is permission-scoped.
|
||
- Providers can send urgent messages from mobile.
|
||
- Parent portal is fully usable on mobile.
|
||
- Key actions have clear success/error states.
|
||
- Mobile pages load quickly on normal mobile networks.
|
||
|
||
---
|
||
|
||
## 9. Mobile Data Safety
|
||
|
||
Mobile devices are easy to lose, share, or leave unlocked. Required safeguards:
|
||
|
||
- Session expiration
|
||
- Optional MFA
|
||
- Role-based access
|
||
- No unnecessary sensitive data caching
|
||
- Encrypted offline cache where supported
|
||
- Remote session revocation
|
||
- Audit logs for sensitive views/actions
|
||
- Staff access removal when employment ends
|
||
|
||
---
|
||
|
||
## 10. Mobile Product Differentiation
|
||
|
||
Many camp platforms technically work on mobile but are not designed around camp moments. CampReg should be built around actual field usage:
|
||
|
||
- Parent in a parking lot changing pickup details
|
||
- Staff checking in children quickly
|
||
- Director sending urgent updates
|
||
- Nurse accessing medication information
|
||
- Parent accepting a waitlist opening immediately
|
||
- Provider approving a VibnAI campaign from phone
|