MZ Rider App
Proof of Concept Product Specification for a lightweight, single-user RV owner web app, designed to be linked from GentleMedia.us.
This spec intentionally avoids overbuilding. It uses a web app approach, outbound route links instead of custom navigation, manual app-based reminders instead of push systems, and a single-user model for faster delivery and cleaner validation.
1. Product Summary
MZ Rider is a mobile-friendly web app for managing the repeated operational workflows of owning and traveling with a 2026 18RK. The app centers on six practical functions:
- Trips and route organization
- Operational checklists
- Inventory management
- Maintenance tracking
- Document storage
- A dashboard that surfaces the next most important actions
2. Product Decisions Locked for POC
| Decision Area | POC Decision |
|---|---|
| User model | Single-user only |
| App format | Responsive web app |
| Hosting model | Protected app page or subdomain backlinked from GentleMedia.us |
| Routing strategy | Saved Google Maps and RV-safe planner links, not embedded custom navigation |
| Trip planning | Simple trip records with notes and optional budget fields |
| Reminders | In-app status and due dates only |
| Documents | Upload and view only |
| Offline mode | Not included |
| Native mobile apps | Not included |
| Third-party integrations | No deep API integrations in POC |
3. Why This Fits the 2026 18RK Use Case
The scope is aligned to the actual operating patterns described in the 2026 Winnebago Towables owner’s manual: safe hitching and towing workflows, 7-way connection, breakaway procedures, leveling, tank monitoring, battery and solar awareness, winterization, recurring pre-trip inspections, and document-heavy ownership tasks. The manual also emphasizes repeated maintenance, checklist-like procedures, and tracking owner responsibilities, which makes this app structure a good fit. :contentReference[oaicite:0]{index=0}
The manual is broad across 2026 towables rather than exclusive to one floorplan, so this spec keeps equipment-related fields editable. That means capacities, optional features, and exact installed components should be configurable rather than hardcoded. :contentReference[oaicite:1]{index=1}
4. Primary User
Primary user: owner-operator of a 2026 18RK trailer
Primary context: mobile phone usage before departure, at arrival, at dump stations, during setup, and when checking maintenance or documents
Secondary context: desktop use for planning trips, uploading files, and reviewing maintenance history
5. Success Criteria for the POC
- User can create and manage trips
- User can save and launch route resources from one place
- User can complete repeatable checklists without losing progress
- User can track supplies and low-stock items
- User can track maintenance across trailer and tow vehicle
- User can upload and retrieve manuals, receipts, and trip documents
- User can use the app comfortably on a phone browser
6. Information Architecture
Primary Navigation
- Dashboard
- Trips
- Checklists
- Inventory
- Maintenance
- Documents
- Settings
Core Relationships
- A trip can contain route links, notes, checklist progress, and documents
- Maintenance items belong to an asset
- Documents may belong to trips or maintenance records
- Inventory supports trip readiness and checklist execution
7. Functional Scope
7.1 Dashboard
The dashboard is the operational home screen.
- Shows next trip
- Shows incomplete checklist counts
- Shows overdue and upcoming maintenance items
- Shows low-stock inventory items
- Shows recent documents
- Shows quick links to route tools
7.2 Trips
The Trips module is a simple trip planner and log, not a booking engine.
- Create trip
- Edit trip
- Delete trip
- Store route links
- Add trip notes
- Attach checklist progress
- Attach documents
7.3 Route Hub
The route hub organizes route resources without trying to replicate map software.
- Save Google Maps link
- Save RV-safe planning link
- Store stop notes
- Store hazard notes
- Store campground notes
7.4 Checklists
Checklists are a core feature because the trailer workflow is heavily procedural.
- Arrival checklist
- Setup checklist
- Dump checklist
- Tear Down checklist
- Hitch-Up checklist
- Ready-to-Go / Departure checklist
7.5 Inventory
Inventory covers supplies, tools, consumables, and frequently used gear.
- Add item
- Edit item
- Delete item
- Search items
- Filter items by category or location
- Flag low-stock items
7.6 Maintenance
Maintenance covers both the trailer and the tow vehicle.
- View items by asset
- Add maintenance task
- Edit maintenance task
- Mark maintenance complete
- Track due dates
- Attach maintenance documents
7.7 Documents
Documents create one place for manuals and ownership records.
- Upload files
- Upload images
- View files by category
- Open individual files
- Associate files with trips or maintenance
8. Recommended Default Checklist Templates
8.1 Hitch-Up
- Wheel chocks in place before hookup
- Coupler aligned over hitch ball
- Coupler latch closed
- Safety pin inserted
- Tongue jack fully retracted
- Stabilizer jacks fully retracted
- Breakaway cable attached
- Safety chains crossed and attached
- 7-way plug connected
- Running lights and brake lights tested
8.2 Ready-to-Go / Departure
- Cabinets and drawers secured
- Refrigerator latch engaged
- Windows and vents closed as needed
- Power cord disconnected and stored
- Water hose disconnected and stored
- Sewer hose disconnected and stored
- Awning retracted
- Slide-out retracted if equipped
- Exterior compartments locked
- Wheel chocks removed last
8.3 Arrival
- Select level site
- Vehicle in park and ignition off
- Wheel chocks placed
- Unhook 7-way and breakaway when appropriate
- Unhook safety chains
- Raise coupler off hitch ball
- Move tow vehicle clear
8.4 Setup
- Level front-to-rear
- Level side-to-side
- Lower stabilizers evenly
- Connect shore power if available
- Connect city water if available
- Check control panel tank readings
- Extend awning if weather allows
- Extend slide-out if present and clear
8.5 Dump
- Wear gloves
- Connect sewer hose
- Open black tank first
- Flush black tank if available
- Open grey tank second
- Rinse sewer hose
- Close valves
- Add treatment and starter water
8.6 Tear Down
- Turn off water heater or appliances as needed
- Disconnect utilities
- Store hoses, cords, and adapters
- Secure loose outdoor items
- Retract awning
- Retract slide-out if equipped
- Raise stabilizers
- Move into Hitch-Up workflow
9. Inventory Categories
Suggested Categories
- Hookups
- Tank / dump gear
- Electrical
- Kitchen
- Safety
- Cleaning
- Tools
- Spare parts
Suggested Locations
- Front pass-through
- Kitchen storage
- Bathroom
- Bed storage
- Exterior hatch
- Tow vehicle
- Rear storage
- Utility bin
10. Maintenance Scope
The manual strongly emphasizes recurring pre-trip inspections, wheel and brake checks, tank and water care, roof and seal inspection, and regular winterization/storage procedures. Those maintenance rhythms are a direct fit for the app’s maintenance section. :contentReference[oaicite:2]{index=2}
10.1 Assets
- 2026 18RK trailer
- Tow vehicle
10.2 Seed Trailer Maintenance Items
- Check tire pressure before each trip
- Inspect tires for wear and debris
- Torque lug nuts
- Test safety detectors
- Inspect roof, sidewalls, and underbelly
- Inspect seals and reseal if needed
- Check auxiliary battery charge
- Check exterior lights
- Check brakes
- Inspect awning
- Sanitize fresh water system annually
- Winterize before storage
10.3 Seed Tow Vehicle Maintenance Items
- Oil change
- Tire rotation
- Brake inspection
- Tow wiring check
- Brake controller check
- Battery test
- Hitch hardware inspection
11. Data Model
11.1 Trip
- id
- title
- start_date
- end_date
- origin
- destination
- google_maps_url
- rv_route_url
- route_notes
- campground_notes
- fuel_estimate
- campground_estimate
- misc_estimate
- actual_notes
- status
11.2 Checklist Template
- id
- name
- description
11.3 Checklist Item
- id
- template_id
- label
- sort_order
11.4 Trip Checklist
- id
- trip_id
- template_id
- progress_percent
- notes
11.5 Trip Checklist Item State
- id
- trip_checklist_id
- checklist_item_id
- completed
- completed_at
11.6 Inventory Item
- id
- name
- category
- location
- quantity
- low_stock_threshold
- status
- notes
11.7 Asset
- id
- name
- type
11.8 Maintenance Item
- id
- asset_id
- service_name
- last_completed_date
- next_due_date
- status
- interval_notes
- notes
11.9 Document
- id
- title
- category
- file_url
- related_trip_id
- related_maintenance_id
- uploaded_at
12. Acceptance Criteria
12.1 Access
- Authorized user can sign in successfully
- Unauthorized visitor cannot access app data
- App is reachable from GentleMedia.us backlink
12.2 Dashboard
- Dashboard shows next trip, checklist status, maintenance status, low-stock items, and recent documents
- Dashboard links to all major modules
12.3 Trips
- User can create, edit, and delete a trip
- User can save route links
- User can open saved route links
- User can add notes and optional budget values
12.4 Checklists
- System contains Arrival, Setup, Dump, Tear Down, Hitch-Up, and Ready-to-Go templates
- User can mark items complete
- Checklist progress persists after refresh
- User can reset checklist for a new trip
12.5 Inventory
- User can add, edit, and delete inventory items
- User can search and filter inventory
- User can identify low-stock items
12.6 Maintenance
- User can add, edit, and complete maintenance items
- Maintenance items are grouped by asset
- Overdue and upcoming items are visually distinct
12.7 Documents
- User can upload and view files
- User can categorize files
- User can associate files to trips or maintenance items
12.8 UX
- App works on mobile without horizontal scrolling
- Touch targets are comfortable on phone screens
- Core pages load in a reasonable time on common mobile and Wi-Fi connections
13. Non-Goals
- No custom turn-by-turn route engine
- No live campground booking system
- No native app-store deployment
- No push notifications
- No multi-user or family account model
- No sensor sync or telematics
- No deep integrations with Google Maps, RV Life, Lippert, or Furrion APIs
- No offline-first architecture
14. Recommended Technical Stack
- Frontend: Next.js
- Backend / Database: Supabase
- Storage: Supabase Storage
- Hosting: Vercel
- Auth: Single authorized user login
This stack is fast to ship, simple to host, supports file uploads, and is ideal for a clean web POC.
15. Definition of Done
- App is linked from GentleMedia.us
- User can authenticate
- User can create and manage trips
- User can save and open route links
- User can run operational checklists
- User can manage inventory
- User can track maintenance for trailer and tow vehicle
- User can upload and open documents
- App is usable on mobile browser
16. Approval Statement
Approval of this document means agreement to build MZ Rider as a lean single-user web app with: Dashboard, Trips, Route Hub, Checklists, Inventory, Maintenance, and Documents, with no advanced route engine, no native app packaging, and no deep third-party integrations in the POC.
