Structured alerts
People choose a useful category rather than opening an unrestricted conversation.
Why RoadPing exists
A useful heads-up without exchanging personal details.
RoadPing explores a simple idea: if someone spots a time-sensitive problem with a vehicle, they should be able to alert its verified owner without either person seeing the other’s name, email address or phone number.
The original RoadPing concept was created by Continuity Through Planning. This demonstration develops that idea into an interactive product experience.
Product principles
Built to be calm, constrained and private.
Identity separation
The product is designed to route an alert without revealing either driver’s contact details.
Verified ownership
A production service must prove a user can receive alerts for a vehicle before delivery is enabled.
What is built
A working product demonstration—not a live vehicle network.
Working today
- Sender and recipient journeys
- Registration formatting and issue selection
- Acknowledgements and safe preset replies
- Restricted tester authentication
- Private server-side persistence foundations
Still simulated or gated
- Vehicle-owner identity and verification
- DVLA or third-party vehicle lookups
- Email and push delivery
- Production support and abuse operations
- Use of genuine registrations
Technology
Deliberately straightforward infrastructure.
The pilot keeps identity, application logic and data access separated, with sensitive database access confined to the server.
Next.js 16, React 19 and TypeScript
A responsive web-first pilot that works well on a mobile viewport and can be iterated quickly.
Clerk
Passwordless tester access and server-verified sessions without building custom authentication.
Supabase PostgreSQL in London
Private, structured storage behind authenticated server routes; no database credential reaches the browser.
Zod
Consistent request validation at the application boundary.
Vitest, Testing Library and Playwright
Unit, component and mobile-browser journey coverage.
Vercel
Repeatable Next.js builds, preview deployments and a clear path to roadping.co.uk.
Browser → Next.js server → Clerk + Supabase
The browser never receives the Supabase service-role credential. Protected operations derive the signed-in user on the server and scope data to that identity.