CleanStop
Community Restroom Finder
A mobile-friendly public utility designed to help people locate a nearby restroom that is usable right now through concise status reports, freshness indicators, practical details, and moderation-first publishing.
Overview
CleanStop began with the frustration of stopping at gas stations and other public locations without knowing whether a restroom would be available, clean, stocked, private, or usable.
Existing map listings show that a business exists, but they rarely answer the practical restroom question. CleanStop is intentionally not a long-form review platform. It is designed for fast, current, structured information.
A person should be able to see whether a location is currently a good stop, how recent the information is, what type of restroom is available, and whether the update has been reviewed.
How It Started
The initial concept focused on a direct consumer need: reducing uncertainty when someone needs a restroom quickly.
The product direction became clearer when raw reviews were separated from the public status. Contributions could be accepted without allowing every unreviewed submission to immediately alter what another user sees.
Where can I find a nearby restroom that is usable right now?
Architecture
Public Interface
- Candidate list
- Detail view
- Structured report form
- Freshness and status
Local UX
- Pending acknowledgement
- Quick-edit window
- Cooldown messaging
- Fallback storage
Private Intake
- Pending reports
- Place suggestions
- App feedback
- Anonymous session data
Approved Public Data
- Moderation workflow
- Summarized status
- Latest approved note
- No raw public history
Development Timeline
Concept origin
The app was framed around practical restroom usability rather than general business reviews.
Functional front end
A static mobile-friendly application was built with candidate lists, detail views, structured reports, sorting, and local pending states.
Supabase alpha architecture
Database tables, row-level security, pending-report intake, public status, suggestions, and feedback were defined.
Manual moderation loop
SQL helpers were created to approve, reject, or flag reports and synchronize approved public status.
Local alpha preparation
Coverage, privacy review, abuse controls, testing, and deployment remain the next steps.
Results and Current Boundaries
Working alpha interface
The current app provides the full user path from finding a candidate to submitting a structured update.
Trust model implemented
Pending reports do not override public status, and approved summaries remain separate from raw report history.
Release package prepared
The recoverable front end, schema, migrations, moderation helpers, and documentation have been organized into a public candidate.
The alpha does not yet provide guaranteed live coverage, automated trust scoring, full abuse protection, public photos, user accounts, or a completed map-discovery system.
Project Materials
Application
HTML, CSS, JavaScript, centralized copy, and browser-state handling.
Data Layer
Supabase schema, migrations, RLS rules, seed planning, and public-status model.
Operations
Moderation workflow, admin helpers, trust guidance, and alpha documentation.
Add your final GitHub, ZIP, diagram, video, or document links here only after each public package has been reviewed and sanitized.