What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Would a version showing upcoming stations like the in-car door display be useful?From this comment
- Could a quieter, more background version run longer with softer chimes for sleeping?From this comment
- Could the next and previous buttons be clearer, since their direction changes with the loop?From this comment
- Could the travel sections between stations be made longer for a truer trip feel?From this comment
- Could the audio be binaural rather than standard stereo?From this comment
What they doubted or pushed back on our summary
- The install-as-app popup after the first station seems unnecessary and its not-now button looks disabled.From this comment
- The chimes and melodies feel too loud and too frequent for sleeping.From this comment
- The seek controls confuse users because sideways buttons change travel direction with the loop.From this comment
- Access was blocked because company policy rejects newly registered domains.From this comment
What the maker answered our summary
9 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Coding assistance sped up work but needed many rounds to get right, though caching and service workers went smoothly.From this comment
- An early attempt at replicating the door display went poorly, so a custom mobile interface was designed instead.From this comment
- A sleep mode is planned, and it should be simple since chimes and melodies sit on separate tracks.From this comment
- Vertical next and previous arrows plus mouse wheel support were added, and a soundscape revision is planned.From this comment
What a builder can take from it: Builders should expect rough spots when using coding tools, respond fast to usability feedback, and fix manipulative install prompts before shipping. our reading
The title, taken apart our calculation
This post got 238 points; the median for all 1442 posts is 112.
When it was posted our calculation
Tuesday at 12:00 UTC. Of 3,017 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 80 (2.7%) reached 50 points; on Tuesdays it was 2.8% of 8,995. The average over all hours is 2.9%. One post's time does not explain its result; the full table of hours is on the Show HN hub.
Check your title our calculation
Type the title you plan to post. It is compared with 1,442 Show HN posts that reached 50 or more points: its length, its shape, and how posts of that length and shape did. Nothing is sent anywhere.
Type a title above to see where it sits.
Draft my Show HN post
Paste your site address and get title options and a first comment for your own Show HN post, written from what your site says and checked against the numbers above. Nothing is posted for you.
Free to try and no account needed. FoxPlug is for people who ship several projects and keep stalling on telling anyone: it turns what you ship into posts you approve before anything goes out. See what each plan includes.
More teardowns
Points, comments, titles and times are Hacker News's own numbers, read from the post itself, last updated Nov 2026. Summaries of what people said are ours, written in our own words, and each one links to the comment it came from. Percentages and medians marked "our calculation" are computed from the posts counted on the page: they describe what happened, not what will happen to your post. FoxPlug posts nothing for you. Plans and limits are on the pricing page. Questions: support.
After the launch post: a changelog your users read
A launch brings visitors once. FoxPlug turns what you ship afterwards into a public changelog and ready posts, so the next visitor finds something new.
Start your changelog See a SaaS changelog example
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Visual cards and walkthrough videos made from what you shipped
- Posts for X, LinkedIn and dev.to written from your changes
- Connect GitHub and the tools you build with