TransitPin Roadmap¶

This document lists what is next for TransitPin, with a current status for each item. Statuses are "Shipped", "In progress", or "Planned". There are no target dates here on purpose; this reflects what exists in the codebase and what the product documents call for, not a schedule.

Shipped (in the live deployment today)¶

These are verified against the live app3 deployment:

Operator dashboard (admin.html) with the 11 operator capabilities: route table, sort/filter, add/edit/delete with confirmation, route detail with stops and riders, autosave drafts with publish, dashboard stats, live fleet map, pin-driver, route polylines, and TomTom traffic toggle.
Route geocoding of stop addresses via TomTom.
Per-stop riders (comma-separated) in the route editor.
Role-aware login: parents go to the parent portal, operators go to the operator dashboard.
Combined sign-in and registration page (signin.html), with the old register.html redirecting to it.
Parent registration form: parent and second parent info, emergency contacts, up to three children with school dropdowns and transport need, five policy checkboxes, and the $50 registration fee.
Five policy documents (transportation agreement, photo/media release, late pickup, late payment, child privacy).
Billing rates: $50 registration fee, $120/week one-way, $175/week two-way, with the first invoice generated 5 days before first pickup.
Full-screen fleet map layout at fleet/dashboard.html.
Tenant theme resolution from subdomain, served from /api/theme/.
Driver page (driver.html) with browser geolocation tracking.

In progress¶

Full-screen live fleet map enhancements (dashboard req 8)¶

Status: In progress.

The full-screen map layout already exists at fleet/dashboard.html and polls bus locations. The traffic toggle and the pin-driver-to-center toggle are present. The remaining piece called for in the requirement is a dedicated Maps surface with a right-side geofence and ETA panel, plus per-stop markers on the full-screen view. The recommendation is documented in the dashboard code; the geofence/ETA panel is not yet built.

AI Route Builder on the fleet dashboard¶

Status: In progress.

The AI Route Builder lives on admin.html and is launched from the "+ Add AI Route" button. The requirement is to also surface it on fleet/dashboard.html (the preferred layout). The chosen approach is a "+ Add AI Route" button next to "+ Add Route" on that dashboard.

Driver PWA (on-the-clock tracking)¶

Status: In progress.

The driver page (driver.html) already uses the browser geolocation API to track position, and the buses table stores latitude, longitude, heading, speed, and last-update time with a PUT /api/buses/{id}/location endpoint. Remaining work is completing the on-the-clock flow so a driver who is logged into the driver PWA is treated as on the clock and tracked.

Parent portal re-skin (tenant-aware)¶

Status: In progress.

The sign-in page already resolves the tenant slug and applies the tenant's theme and brand name. The next step is applying the same tenant-aware theming to the parent portal (parent.html) so a parent sees the client's brand end to end, not TransitPin's.

OPS Assume Identity and audit log¶

Status: In progress.

The platform ops console has an Assume Identity feature (platform-admin only) with a short-lived impersonation token and a full audit log, plus per-tenant log views. These are wired through the ops backend router and the ops console UI. Final verification and polish are ongoing.

Billing (households, split-billing, outstanding)¶

Status: In progress.

Billing is built around households, payers, and allocations, with weekly totals computed from each child's transport need. The rates endpoint is live. Remaining work is verifying the generate-due flow (first invoice 5 days before first pickup) end to end and the outstanding-payments report.

Map traffic and weather¶

Status: In progress.

TomTom live-traffic overlay and local weather (Open-Meteo) are wired into the dashboard, with a TomTom health check exposed for the ops console. Per-route driving conditions are available via the maps backend router.

Planned¶

Replace placeholder marketing content¶

Status: Planned.

The marketing pages (index.html, about.html, schools.html, policies.html, fleet.html) still contain placeholder content: example phone numbers (912) 555-xxxx, placeholder testimonials, and a placeholder team section. These need to be replaced with real statistics, customer testimonials, a real support phone number, and a real team/company story before public launch.

Square payments integration¶

Status: Planned.

Square is the intended primary payment provider, with Stripe as an option. The provider abstraction and the "not connected" handling are in place, and the provider-status endpoint reports connection state. Real invoice creation requires Square OAuth credentials (access token and location id) from the client's Square account; until those are configured, invoices are generated as drafts with no payment provider.

Twilio SMS notifications¶

Status: Planned.

A Twilio number is provisioned for SMS. Parent notifications (route changes, delays, sign-in/sign-out) via SMS are planned but not yet wired.

Parent discovery portal¶

Status: Planned.

A parents.transitpin.com-style discovery portal where a parent searches for their transportation provider and is redirected to that provider's branded subdomain. Documented in the product launch document; not yet built.

White-label custom domains (Fleet tier)¶

Status: Planned.

Tenant subdomains (slug.transitpin.com) work today. Custom domains for a client (for example track.client.com) are a planned Fleet-tier feature per the white-label vision document.

Native mobile apps¶

Status: Planned.

Capacitor wrappers for iOS and Android are a Phase 2 item in the product launch document.

Domain and brand finalization¶

Status: Planned.

The transitpin.com domain (all three major TLDs are available) has not been purchased yet. Purchasing the domain and finalizing the logo and brand are open items before public launch.

Sources¶

OPERATOR-DASHBOARD-REQUIREMENTS.md (the 11 dashboard requirements)
REGISTRATION-POLICIES-PRICING-REQUIREMENTS.md (registration and pricing)
TECHNICAL-SPEC.md (ops assume identity, map traffic/weather, billing)
product-launch-doc.md (tiers, discovery portal, native apps, domain)
white-label-vision.md (custom domains, tiers, branding)
Live code comments in admin.html and fleet/dashboard.html (req 8 note)