A public-toilet finder with a literal compass needle is not the app you'd expect to hit ~2.7K upvotes and 180+ comments on r/ClaudeAI in under a day. But that's what happened with Compiss — a free, ad-free app built by Reddit user u/Jesus_Morty, who says the entire thing, iOS app, Android app, Apple Watch companion, and the compiss.app website, was written end to end with the Claude Code CLI on a Mac. It's a concrete data point in the same story explainx.ai has been tracking as software for one and solo builders shipping real products with Claude Code: what happens when the barrier between "I have an idea" and "it's on the App Store" collapses to one person and a terminal.
TL;DR — what people are asking about Compiss
| Question | Answer |
|---|---|
| What does it do? | Points a compass toward the nearest public toilet, shows nearby pins (including accessible-toilet icons), and adds a "Clench Mode" banner ("Almost there. No sudden moves") when you're close |
| Who built it, and how? | u/Jesus_Morty, solo, using the Claude Code CLI on a Mac for all code, assets, and e2e tests |
| Where does the data come from? | toiletmap.org.uk for the UK, OpenStreetMap everywhere else; cleanliness ratings and comments are community-submitted and moderated |
| Is it free? | Yes — free, no ads, no in-app purchases |
| Where can I get it? | compiss.app, Apple App Store, Google Play, and an Apple Watch companion app |
| Does it actually work? | Mostly — but it crashes on launch for a number of Android users (Pixel 10, Pixel 8a, Samsung S26/S23 Ultra); a fix is submitted and awaiting Google Play approval |
| Is this the same as the "$3,000 dream game" post? | No — that was a separate, unrelated viral post in the same subreddit that turned out to be a RuneScape screenshot. Compiss is a real, verifiable app on real app stores |
What Compiss actually is
The pitch, in the app's own tagline, is "emergency toilet radar." Open it and you get a radar-style interface with a compass needle pointing at the nearest public toilet, plus pins for other nearby options — including ones flagged as wheelchair-accessible. Get close enough and a "Clench Mode" banner takes over the screen with distance and time ("20m / 1 min — Almost there. No sudden moves"), which is the detail that made the thread laugh and also the detail that makes the app genuinely well-designed for its actual job: giving someone in real discomfort one glance of information instead of a cluttered map.
Beyond the compass, users can rate a toilet's cleanliness, leave comments, and attach photos — all moderated before they go live. Filters let you narrow results to free-only or accessible-only locations. The location data itself comes from two existing open sources rather than anything scraped or invented: toiletmap.org.uk covers the UK, and OpenStreetMap covers everywhere else. Cleanliness scores are entirely community-driven inside the app, not pulled from a third-party ratings API.
The whole thing is free, with no ads and no in-app purchases — a genuinely unusual combination for a utility app with real hosting and maintenance costs, and part of why the thread's reaction skewed positive rather than skeptical.
Why this is a real vibe-coding milestone, not a demo
The angle that matters for anyone following the "what can non-engineers and solo builders actually ship with an AI coding agent" thread is the surface area. This isn't a single-page Artifact or a weekend Three.js toy — it's three separate native-ish targets (iOS, Android, watchOS) plus a marketing site, plus a moderation pipeline for user-submitted content, plus community ratings, plus app-store submission and review on two platforms. According to the OP, Claude Code generated the code, the assets, and the end-to-end tests — the kind of scope that, a few years ago, would have needed a small team spanning mobile, backend, and QA.
That maps directly onto what Pieter Levels documented with his VPS + Claude Code + MacinCloud stack for shipping the Nomads iOS app: getting past App Store review and code signing is still real, non-trivial friction for a solo builder — Compiss cleared that bar on two stores and a watch platform at once. It's also a useful counterpoint to more disposable "software for one" projects built for a household of one: Compiss is explicitly built for strangers, at scale, for free, which raises the stakes on reliability in a way a personal sleep tracker never has to face.
The George Costanza callback, and why the thread loved it
A large share of the comment energy went to one joke: commenters compared Compiss directly to George Costanza's "iToilet" pitch from Curb Your Enthusiasm — a well-known bit where George tries to sell Jason Alexander on an app idea for locating public restrooms. The thread's running gag was, essentially, "someone actually built the George Costanza app," and that pop-culture hook did real work in getting the post past 2,700 upvotes. Layered on top of that, several commenters pointed out that Compiss works as a pun in Swedish (kompis means "buddy") and comes close in Italian, Spanish, and Dutch — the kind of accidental multilingual branding win that's genuinely hard to plan for.
Underneath the jokes, a recurring and more substantive thread of comments said the app is genuinely useful for people with disabilities, pregnant partners, and families with young kids — the exact audience an emergency bathroom-finder is actually for, independent of the compass gimmick's viral appeal.
The honest part: it also crashes for some Android users
This is the part worth taking seriously rather than skipping past, per how explainx.ai covers derivative and reaction content honestly — a viral launch thread is not the same thing as a finished, hardened product. Multiple commenters reported Compiss crashing immediately on launch on specific Android devices: Pixel 10 running Android 16, Pixel 8a running Android 17, and Samsung Galaxy S26 and S23 Ultra. The OP acknowledged the bug directly in the thread rather than deflecting it, and said a fix had already been submitted and was awaiting Google Play approval at the time of posting. Other requests surfaced in the comments — support for older iOS versions and imperial units instead of metric — which the OP said they'd look into, but hadn't shipped yet.
This is a familiar shape to anyone who has followed explainx.ai's coverage of community pushback on AI-coded output: a capable agent producing genuinely functional software doesn't mean zero-defect software, especially across the device fragmentation that Android specifically introduces. The crash reports scattered across specific device models rather than a single root cause is also exactly the kind of bug that's hard to triage from Reddit comments alone.
One piece of concrete engineering feedback worth copying
A commenter suggested something simple and worth generalizing: wire in a real crash reporter — Crashlytics was the example named — instead of trying to correlate crash reports by device model manually in a comment thread. That's a small, cheap addition (most crash reporting SDKs are a few lines of setup) that would have turned "several different people reporting different Pixel and Samsung models" into a single grouped, stack-traced issue the OP could fix from data instead of anecdote. It's the kind of production hygiene step that's easy to skip when an AI coding agent makes the happy path fast to build, and it's the single most actionable lesson in the whole thread for anyone shipping an AI-coded app to real users rather than to themselves.
Lessons for other vibe-coders shipping to production
| Lesson | Why it matters |
|---|---|
| Cross-platform + app-store review is genuinely achievable solo | Compiss cleared iOS, Android, and watchOS review as a one-person project, using Claude Code for code, assets, and e2e tests |
| Reuse existing open data instead of building your own | toiletmap.org.uk and OpenStreetMap did the hard data-collection work; Compiss just built the interface and community layer on top |
| "Built by AI" is not "bug-free" | The Android launch crash across several device models shipped to production before it was caught in the wild |
| Acknowledge bugs publicly, don't hide them | The OP owning the crash and stating a fix was already submitted did more for credibility than pretending it worked perfectly |
| Add real crash reporting before you scale distribution | Grouping crashes by stack trace beats triaging by device model in comments — cheap to add, expensive to skip |
| Free + no ads + no IAP is still a legitimate distribution strategy | It removed a common source of skepticism in the thread and let the app's utility carry the conversation |
Getting Compiss
Compiss is live at compiss.app, on the Apple App Store, on Google Play, and as an Apple Watch companion app. If you're on one of the affected Android devices and it crashes on launch, that's a known issue with a fix reportedly submitted and pending Google Play approval — not a sign the project has been abandoned.
Related reading
- Software for One: building personal apps with AI coding agents
- Claude Code on VPS + SSH: shipping an iOS app solo with MacinCloud
- Why developers say Claude Opus 5 over-engineers simple tasks (r/ClaudeAI)
- Claude Opus 5 games go viral: the browser-worlds wave
- Vibe coding nightmares: mistakes and how to avoid them
- What is vibe coding? explained
- Meta Pocket: vibe-coded mini-games from text prompts
- toiletmap.org.uk and OpenStreetMap — the underlying open data sources
Details in this post reflect a r/ClaudeAI thread by u/Jesus_Morty (~2.7K upvotes, 180+ comments) as of August 8, 2026, roughly 9 hours after posting, plus the developer's own claims about how the app was built. App Store availability, the Android crash fix, and feature requests (older iOS support, imperial units) may change after this post's publication — check compiss.app and the app-store listings directly for current status.