MZ Rider App – POC Product Spec – 2026 18RK

MZ Rider App

POC Product Specification

Configured for 2026 18RK ownership workflow | Lean web app | Backlinked from GentleMedia.us

1. Purpose

MZ Rider is a lightweight owner-operator web app for managing a towable RV workflow without overbuilding. The proof of concept is designed around the real operating rhythm of a 2026 18RK: trip planning, hitch/departure prep, arrival/setup, tank and utility awareness, supply inventory, maintenance tracking, and document storage.

This POC is not intended to be a full native app, route engine, or telemetry platform. It is meant to prove that a simple, mobile-friendly web app can reduce missed steps, improve readiness, and centralize important RV ownership information.

2. Product Strategy

Build philosophy: keep only the features that solve repeated owner pain points.

Recommended format: responsive web app.

Hosting path: backlink from GentleMedia.us to a protected app page or subdomain.

User model: single-user only for POC.

Primary device: mobile phone in the field; desktop as secondary.

3. POC Goals

  1. Create and manage trips.
  2. Store and launch route links for Google Maps and RV-safe planning tools.
  3. Run repeatable operational checklists.
  4. Track inventory and low-stock items.
  5. Track maintenance for tow vehicle and trailer.
  6. Store manuals, receipts, photos, and maintenance records.

4. Core Product Decisions

Decision Area POC Decision
Accounts Single-user only
App type Responsive web app
Routing Saved outbound links, not embedded custom navigation
Trip planning Simple trip records with notes and optional budget fields
Maintenance reminders Date-based and status-based inside app only; no push notifications
Documents Upload and view only for POC
Offline support Not included in POC
Integrations No deep third-party API integration in POC

5. 2026 18RK-Oriented Scope Assumptions

This spec is tailored to a towable Winnebago workflow and assumes the app should reflect the kinds of systems described in the 2026 owner’s manual, such as hitching and leveling, 7-way connection, breakaway workflow, tank monitoring, battery and solar awareness, awning, slide-out care where applicable, seasonal winterization, roof and seal inspections, and recurring maintenance tracking.

Because the manual is broad across 2026 towables, any trailer-specific fields in the app should remain editable instead of hardcoded. That includes exact capacities, component brands, slide-out presence, and equipment variations.

6. Main Navigation

  • Dashboard
  • Trips
  • Checklists
  • Inventory
  • Maintenance
  • Documents
  • Settings

7. Functional Scope

7.1 Dashboard

The dashboard is the operational home screen.

Dashboard must show:

  • next trip
  • open checklist progress
  • overdue or upcoming maintenance
  • low-stock inventory items
  • recent documents
  • quick route links

7.2 Trips

The Trips module is a simple planner and recordkeeper. It is not a campground booking system and not a GPS engine.

Trip fields:

  • trip name
  • start date
  • end date
  • origin
  • destination
  • google maps link
  • rv-safe route link
  • campground or stop notes
  • fuel estimate (optional)
  • campground estimate (optional)
  • misc estimate (optional)
  • actual spend notes (optional)

7.3 Route Planning Hub

The app will not try to merge mapping platforms in the POC. Instead it will store and organize route resources in one place.

Route hub includes:

  • saved Google Maps URL
  • saved RV-safe route URL
  • route notes
  • hazard notes
  • fuel / stop notes

7.4 Checklists

Checklists are a core POC feature because they directly map to repeated RV tasks.

Required checklist templates:

  • Hitch-Up
  • Ready to Go / Departure
  • Arrival
  • Setup
  • Dump
  • Tear Down

Checklist behavior:

  • user can open a template
  • user can mark items complete
  • progress saves automatically
  • checklists can be attached to a trip
  • checklists can be reset for a new trip

7.5 Inventory

Inventory is meant for gear, consumables, and operational supplies.

Inventory fields:

  • item name
  • category
  • storage location
  • quantity
  • low-stock threshold
  • status
  • notes

Suggested categories:

  • hookups
  • tank / dump gear
  • electrical
  • kitchen
  • safety
  • cleaning
  • tools
  • spares

7.6 Maintenance

Maintenance should cover both the trailer and the tow vehicle.

Assets for POC:

  • 2026 18RK trailer
  • tow vehicle

Maintenance record fields:

  • asset
  • service title
  • status
  • last completed date
  • next due date
  • interval notes
  • notes
  • related document upload

7.7 Documents

Documents provide one place to store reference files and ownership records.

Required document categories:

  • manuals
  • receipts
  • maintenance records
  • insurance / registration
  • trip photos
  • campground confirmations

8. Suggested Default Checklist Content

8.1 Hitch-Up

  • confirm wheel chocks are in place before hookup
  • raise or lower tongue jack to align coupler and hitch ball
  • close coupler latch and insert safety pin
  • fully retract tongue jack
  • confirm stabilizer jacks are fully retracted
  • attach breakaway cable
  • cross and attach safety chains
  • connect 7-way plug
  • test running lights and brake lights

8.2 Ready to Go / Departure

  • lock windows and roof vents as needed
  • secure interior items and fridge contents
  • disconnect water, sewer, and power
  • store hoses and adapters
  • remove wheel chocks
  • confirm doors and compartments are locked
  • confirm awning is fully retracted
  • confirm slide-out is retracted if present

8.3 Arrival

  • choose level site
  • place tow vehicle in park and shut off ignition
  • place wheel chocks
  • disconnect 7-way and breakaway cable when appropriate
  • uncouple trailer
  • level front to rear with tongue jack
  • level side to side

8.4 Setup

  • lower stabilizer jacks evenly
  • connect shore power if available
  • connect city water if available
  • check battery disconnect and 12v status
  • extend awning if conditions allow
  • check control panel tank readings
  • open slide-out if present and site clearance allows

8.5 Dump

  • wear gloves
  • connect sewer hose
  • dump black tank first
  • flush black tank if available
  • dump grey tank second
  • rinse hose
  • close valves
  • add tank treatment and water after dump

8.6 Tear Down

  • turn off water heater or appliances as needed
  • disconnect water and power
  • stow hoses, cords, and accessories
  • secure loose gear
  • retract awning
  • retract slide-out if present
  • raise stabilizers
  • prepare for hitch-up workflow

9. Maintenance Seeds for POC

The app should ship with starter maintenance tasks based on the manual’s recurring inspection logic.

9.1 Trailer Maintenance Seed Items

  • check tire pressure before each trip
  • inspect tires for wear and debris
  • torque lug nuts
  • test safety detectors
  • inspect roof, seals, sidewalls, and underbelly
  • inspect propane system visually
  • sanitize fresh water system annually
  • winterize before storage
  • check battery condition
  • clean solar panel
  • inspect slide-out for debris if equipped
  • inspect awning condition

9.2 Tow Vehicle Maintenance Seed Items

  • oil change
  • tire rotation
  • brake inspection
  • tow wiring and brake controller check
  • battery check
  • mirror and hitch hardware check

10. Data Model

10.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

10.2 Checklist Template

  • id
  • name
  • description

10.3 Checklist Item

  • id
  • template_id
  • label
  • sort_order

10.4 Trip Checklist State

  • id
  • trip_id
  • template_id
  • completed_count
  • total_count
  • notes

10.5 Trip Checklist Item State

  • id
  • trip_checklist_id
  • checklist_item_id
  • completed
  • completed_at

10.6 Inventory Item

  • id
  • name
  • category
  • location
  • quantity
  • low_stock_threshold
  • status
  • notes

10.7 Asset

  • id
  • name
  • type

10.8 Maintenance Item

  • id
  • asset_id
  • service_name
  • last_completed_date
  • next_due_date
  • status
  • interval_notes
  • notes

10.9 Document

  • id
  • title
  • category
  • file_url
  • related_trip_id
  • related_maintenance_id
  • uploaded_at

11. POC Acceptance Criteria

11.1 Access

  • authorized user can sign in successfully
  • unauthorized user cannot access app content
  • app can be reached from GentleMedia.us backlink

11.2 Dashboard

  • dashboard displays next trip, checklist status, maintenance status, low-stock items, and recent documents
  • dashboard links to all major modules

11.3 Trips

  • user can create, edit, and delete a trip
  • user can store Google Maps and RV-safe route links
  • user can open saved route links from trip detail
  • user can add planning notes and optional budget notes

11.4 Checklists

  • system includes Hitch-Up, Departure, Arrival, Setup, Dump, and Tear Down templates
  • user can mark checklist items complete
  • progress persists after page refresh
  • user can reset checklist for a new trip

11.5 Inventory

  • user can add, edit, and delete inventory items
  • user can search or filter by category or location
  • user can identify low-stock items

11.6 Maintenance

  • user can add, edit, and complete maintenance items
  • maintenance items are grouped by asset
  • upcoming and overdue statuses are visually distinct

11.7 Documents

  • user can upload and view documents or images
  • user can categorize uploaded files
  • user can associate documents with trips or maintenance items

11.8 UX

  • app is usable on mobile browser without horizontal scrolling
  • buttons and checklist controls are easy to use on touch screens
  • core screens load in a reasonable time on normal mobile data or Wi-Fi

12. Explicit Non-Goals

  • no custom turn-by-turn map engine
  • no live campground booking
  • no native iOS or Android build
  • no push notifications
  • no multi-user household accounts
  • no deep API integrations with RV Life, Google Maps, Lippert, or Furrion
  • no telematics, sensor sync, or vehicle diagnostics
  • no offline-first sync architecture

13. Recommended Technical Approach

Frontend: Next.js

Backend + Database: Supabase

Storage: Supabase Storage

Hosting: Vercel or equivalent

Access control: single authorized user account

This is the fastest route to a credible POC with authentication, structured data, file uploads, and a responsive interface.

14. Definition of Done

The POC is considered ready for review when all of the following are true:

  • the app is reachable from GentleMedia.us
  • the user can authenticate
  • the user can create and manage trips
  • the user can save and launch route links
  • the user can use operational checklists
  • the user can manage inventory
  • the user can track maintenance for trailer and tow vehicle
  • the user can upload and view documents
  • the app is mobile-friendly

15. Approval Prompt

Approval of this spec means agreement to build the POC exactly as a lean, single-user web app with: Trips, Route Hub, Checklists, Inventory, Maintenance, and Documents, and without advanced integrations or custom navigation logic.