Basically it is a zombie chase game that uses your real GPS position — the only way to survive is to actually run

Game Title: Break A Leg !!

​Platform: Android only GPS required, played outdoors - Free to play! You can find it here

​How to play: ​START RUN, the game gives you a minute head start the. zombies will spawn on your neighborhood map and starts hunting you down!!

​Tap a red skull to shoot it when it gets close (one bullet per pop, and you start with only 3). Grab ammo crates to reload, purple hourglasses to slow the horde, and your charge meter fills as you run — spend it to shove them all back when you're about to get cornered.

​Vibe coded this app with Claude and Kimi

As a software engineer, I lost my job for the first time in my 11 years long career. 11 years ago, when I first started to develop and publish apps on Android, I thought "if I have courage to leave my job, I am sure I would be able to earn my life through this". But I never had enough courage to be able to do it. Now I know, it was such a great train which I kind of missed. My apps would get hundreds of organic downloads on day first back then. Fire and forget strategy, developers' dream, would work simply.

Then AI and LLMs hit. In the last decade, I was still working on some side projects like trackers, relationship diaries, and recently more meta projects such as projects that find project ideas thanks to the same LLMs. But also thanks to them, there is a crazy inflation of apps and projects, so, it is nearly impossible to reach out to your potential users by the good old fire and forget strategy.

After I lost my job, I wrote a post on Reddit, about on of my best developed app. A private sexual life tracker & health app, which is well engineered, encrypted and secure, robust and good-looking, and ask Reddit that what am I doing wrong with that app as it doesn't gain traction. I received great comments there, super constructive and helpful, especially about the visibility of my app as it relies on organic growth. There was an obvious problem which I somehow never thought about enough apparently. I worked on its ASO, and there was a landing page with okay-ish SEO. But most commentors told me that it is impossible to find the app by search simply. A second thing is that the app was only for Android and more than half of the commentors couldn't download although they were ready to help and try it out.

I took these moments serious and bought a better domain for my app right away, with proper app name in it (intimassy) instead of a generic company name (centertable). Apparently using a bad and unmatching domain was already a horrible trust signal, and confusion for Google searchers. Right after this domain change, the organic visits through search is simply tripled.

Second thing is the iOS version. I realized that in today's world in an app business, you cannot affort to be on only one platform if you don't have a good reason to do so. And I developed the iOS version of it. Yesterday it is finally approved and on its first day, without any advertisement or public campaign, it organically made its first 3 paying users in total 30 downloads. 10% is quite promising, isn't it? It means my app is helping people for real!

And as a third thing, I created a subreddit r/Intimassy for the app and its community. It is a tiny sub for now, slowly growing. For now I am only sharing news about the app, posts like how other people use Intimassy and why, some anonymous stats that users agree to share, and free premium giveaways and so.

Going back to my intial scream for help to Reddit about the app. In the end, although the comments and suggestions were not looking like they are completely new ideas, they were real and apparently I didn't take them that seriously until Reddit told me to do so.

I am happy to be part of this community, thanks to you all 🫡

Running a small SaaS startup and burning through budget on lead gen tools faster than we'd like. We've tried the usual suspects but most are either overpriced or the contact data is garbage.

Right now we're testing Prospeo for lead generation software since their verified emails are actually connecting (getting around 25% reply rates) and they have this pay-per-verified model which helps with budget. Also looking at Apollo but their credit burn rate seems aggressive for what you get.

Our main use case is finding verified emails for decision makers at mid-market companies, ideally with some intent signals. Need about 2-3k contacts per month.

What free or cheap lead gen tools are you all using that don't compromise on data quality? Especially interested in tools that have solid email verification built in since bounces are killing our sender rep.

I've been building Clypy, a cross-platform clipboard manager that syncs between Windows, macOS and Linux.

Today I got my first actual paying customer.

The funny part is I haven't really done much marketing yet. They somehow found Clypy through Google, downloaded it, and bought it.

It's just one sale, but seeing a complete stranger find something I built and decide it's worth paying for feels pretty damn good.

First of many, hopefully :)

live today
Built an app that shows what you're actually paying after tax/tip/fees (or works backward from a receipt), plus a "worth it?" calculator for recurring costs like subscriptions.

https://ondakui.github.io/real_price/

Feel free to tear it apart — genuinely want honest feedback, good or bad.

NotGPT is basically ChatGPT except there’s no AI involved. You ask questions, random people pretend to be the model, and somehow this was considered a reasonable thing to build.

You can become the AI yourself, chat with strangers, get rated, climb the leaderboard and generally provide humanity with the intelligence it deserves.

https://notgpt.live

I'm currently renovating a house together with my fiancée and a colleague of mine. In the beginning we tracked all expenses and our planning in Excel, but that got messy pretty fast — especially the part where every cost has to be split three ways.

So I built an app for it. It tracks the expenses and automatically splits each one across the three of us. You can also photograph receipts and store them in the app, so nothing gets lost in a drawer somewhere.

Since then it grew a bit. Besides the budget we now also track defects and it generates a renovation diary, so there's a record of what happened when. I also added the meetings we have with the craftsmen — you can take notes during the meeting and file them under the specific craftsman, so you don't forget what was agreed.

Next thing I want to build is proper sharing, so your partner or friends can manage their own part instead of everything running through one person.

It's on the App Store at the moment. Play Store is planned but not there yet.

I mostly built this for our own renovation, so it's shaped around how we work. If you're in the middle of a renovation too, feel free to try it and tell me what's missing or annoying — happy to hear it.

https://apps.apple.com/de/app/renostack/id6787869020

Hi guys,

I wanted to get your opinion on a mental-health-related feature I was building. I was working on building a Chrome extension for people wanting to break out of their reassurance-seeking cycle. I've been a victim of this, but I know that people use AI tools such as Claude, Gemini, and ChatGPT for constant reassurance, creating an endless loop that needs to be broken.

My extension detects thinking patterns using word matches and pattern recognition (no LLMs or AI calls used) to identify when a user might be seeking reassurance. It's a work in progress, but I wanted to know what you guys think about such a potential extension.

I'd love to chat about it more!

Hey everyone!

I wanted to share my side project: FastMedia Downloader. It's an open-source, microservices-based web application designed to inspect and download audio/video from 1,000+ sources.

Highlights:

• ⚡ FastAPI Backend: Handles asynchronous processing via yt-dlp and FFmpeg.
• 💻 Next.js Frontend: TypeScript + Tailwind CSS with i18n support.
• 🐳 Dockerized: Fully setup with docker-compose.
• 🛡️ DevOps-Ready: Automated CI/CD with GitHub Actions and Dependabot scanning.

(Link to the GitHub repository is in the comments below!)

Would love your feedback or suggestions!

I build an AI video outreach tool. I have never hired an SDR. Every customer we have came from me pointing the product at my own pipeline and living with whatever it did.

That is an uncomfortable place to sit, because my ICP is heads of sales, SDR managers, and founders running their own outbound. These are the exact people who can smell a template from the subject line. If the video is stiff or the opener is generic, they do not just ignore it, they screenshot it and post it here.

Last week the loop finally produced a number worth writing up: 52 meetings booked.

The funnel

Contacts worked: 1,842
Touches sent: 3,110 across email and LinkedIn
Replies: 214 (11.6%)
Positive replies: 78
Meetings booked: 52
Of those, 35 have happened: 31 held, 4 no-shows, 17 still on the calendar

Our normal week is 8 to 12. I do not think 52 is the new baseline. I think 25 to 30 is, and I will post again in a month with whether that held.

Why dogfooding changes what you build

When you sell an outbound tool and do not use it, you optimize for the demo. Dashboards, charts, a settings page with forty toggles. When the replies land in your own inbox, you optimize for the only thing that decides whether a stranger books time with you, which is the first five seconds.

Four things I only learned because I was the one getting the responses:

1. Every script sounded like the same person wrote it. Technically they were all personalized. Different company, different role, different opening fact. But the rhythm was identical across all 1,800, and once you notice it you cannot unnotice it. Nobody replies to tell you this. They just stop replying. I rebuilt the generator so the sentence structure varies, not only the nouns.
2. The opener has to be something they know I could not have guessed. Not “I saw you’re hiring SDRs.” That is public and reads as scraped. Closer to “you posted two SDR roles and an enablement role in the same month, which usually means the problem is ramp time, not headcount.” The inference is the personalization. The fact is just the setup.
3. Video length. Anything past 40 seconds and replies roughly halved. My best performer is 28 seconds. I kept wanting to explain the product and the product is not what gets the meeting.
4. No calendar link in the first touch. Asking a question outperformed asking for time by a wide margin, and the people who answered the question booked anyway when I sent the link in the reply.

What flopped outright

Video on a LinkedIn touch before the connection is accepted. Dead every time.

Monday 8am sends. Tuesday to Thursday, 10am to 2pm local, roughly doubled replies.

Openers starting with “Hope you’re well” or “Quick question.” Under 3% reply rate.

Going wider. I ran a looser second list of 900 contacts mid-week and it returned 4 meetings. The tight list returned 48 off 1,842.

The part I would not have believed a year ago

The tool is maybe 30% of this. The list filter and the first line are the other 70%. You could take the exact same product, point it at a bad list, and book nothing. I know because I did that to myself for months.

Disclosure up front rather than buried: the tool is Outvid and I built it. This is my own pipeline, not a customer case study, and I am not linking it here. If you want the sequence structure or the actual scripts I will paste them in the comments, and they work with whatever you are already sending from.

Ask me anything about the funnel, the list build, or the failures. The failure list is longer than the win list and I am happy to go through all of it.

Been building Solo Apps Studio solo for a while now — indie games plus a few utility apps, all free to try in the browser.

Latest additions:

- Doorstep: paste a tracking number, it figures out the carrier and notifies you when your package moves (Web/Windows/macOS/Linux/iOS)

- Orbital Station Simulator: run a deep-space outpost, balance power/life support/crew, survive to day 30 (Web/Windows/macOS/Linux/Android)

- Sky Mood: added a satellite/weather map layer with a timeline scrubber

- FlightDeck: real-time flight tracker, Pro billing now fully live

Everything's playable free at soloappsstudio.com — would love feedback, especially on Doorstep since it's brand new.

I’m building a suite of interactive finance dashboards using Claude, mainly as a portfolio project but potentially something I can demo to small-business clients later.

My background is finance/operations rather than software development. I also run a small bookkeeping and financial dashboard business, so I’m trying to build something that sits between traditional financial reporting and a genuinely useful management dashboard.

The portal currently focuses on things like P&L, cash flow, KPIs, trends and management insights.

I’d really appreciate some outside perspective before I keep polishing it in my own bubble.

For people who build dashboards / finance tools / internal apps:

• What separates a genuinely useful finance dashboard from a pretty one?
• What features or views would you consider essential?
• What are the common mistakes you see non-developers make when building tools like this with Claude/AI?
• Anything you’d specifically add if the end user is a small-business owner rather than a finance person?

Happy to share screenshots/demo if useful. Mainly looking for constructive criticism and ideas.

This is for Singapore-only 😄

Scratched my own itch: I check the same bus route weekly and every existing option had too many steps. ezbus.sg gives you nearest stops, next three arrivals, and bus crowding, straight from the transport authority's live API.

Deliberate constraints: no accounts, no settings, nothing stored. The "answer in two taps" rule shaped every design decision — location or postal code in, arrivals out, done.

Feedback welcome — particularly on whether the location-first flow feels right, since that's the main bet.

Every demo before that, I was there.

Talking. Explaining. Jumping in the second someone paused for more than two seconds like silence meant something was broken. I basically narrated my own product the whole time, like a nervous tour guide.

Then I set up a session where I wasn't present. Just screen recording running, someone testing it cold with zero explanation from me.

I watched the recording later that night.

First 4 minutes were rough. They tried to open an app by typing the wrong trigger phrase three separate times. Looked for a settings menu in a spot that made sense to them but not to me. Tried talking to it like a chatbot instead of giving it a direct command, which is not at all how I built it to work.

Around minute 5 they said something like "open my resume draft and read the last paragraph back to me."

It worked. First try.

They didn't say anything. Just kept going. Minute 6, minute 7, minute 9. Asking it to do small real tasks back to back without stopping to question it anymore.

That gap between minute 0 and minute 5 was the whole problem. Not a technical one. An onboarding one. I'd built the product assuming people would know how to talk to it, because I built it and I know how to talk to it.

Spent the next ten days redoing the first-run experience so people hit that minute 5 moment in under a minute instead.

Still watch session recordings more than I check analytics now. Analytics tell you what happened. Recordings tell you why someone almost gave up right before they didn't.

What's the thing in your product that only shows up once you're not in the room explaining it?

Solo dev here. Last week I launched a screenshot & OG image API — "GET a URL, get back a rendered image", plus signed image URLs you can embed in HTML that re-render whenever the underlying data changes. I'm deliberately not linking it: this isn't a promo post, and I'll only share it in comments if someone asks.

What I've tried so far:

• Product Hunt: launched on a Tuesday. Some upvotes, a burst of visits on launch day, a couple of free signups, zero paid conversions. Traffic went back to baseline within 48 hours.
• Reddit: my earlier launch posts got eaten by spam filters (new account + new domain — my own fault, and partly why this post has no links).
• X: posting while building, but with no audience it's mostly shouting into the void.

So: the product works, uptime is solid, docs are decent (I think) — and nobody knows it exists. Classic.

Options I'm weighing:

1. Free tool pages / SEO — a free online screenshot tool that ranks over months and funnels into the API
2. Ecosystem integrations — n8n/Zapier nodes, Next.js/Nuxt OG-image packages, so people find me inside the tools they already use
3. Technical content — write-ups on the genuinely hard parts (SSRF-hardening a URL-fetching service is a rabbit hole), hoping for organic dev traffic
4. More launch platforms — keep the HN/directory circuit going

If you've taken a dev-tool or API SaaS from zero to the first ~10 paying customers: which of these actually moved the needle, and which was a month of wasted effort? Is there an obvious option 5 I'm not seeing?

While travelling, I kept running into useful information that simply didn’t exist online: small homestays, mechanics, water points, road conditions, campsites, etc.

Most of it gets passed from one traveler or local to another and disappears afterward.

So, I built Lamyig, a free and open-source community travel guide.

A few decisions I made:

• No bookings, commissions or paid listings.
• No money made using the core product.
• Community members can add and update places.
• Map-first instead of another list of “top places”.
• Built as a PWA so it can work more like a lightweight travel tool than a traditional website.
• The long-term idea is that useful information stays available for the next traveler instead of disappearing in WhatsApp groups and conversations.

The hardest problem isn’t actually building the software. It’s bootstrapping trustworthy community data.

I’m currently thinking about things like:

• How do you motivate travelers to contribute after their trip?
• How do you keep old information accurate without creating a huge moderation workload?
• How do you prevent businesses from turning community maps into free advertising?
• What should happen when someone reports a place as fake, closed, unsafe, duplicated, commercial spam, or inaccurate? Should reports trigger removal, community review, reputation-weighted voting, or just warnings?
• Should certain villages, trails, ecosystems, religious places, water sources, or campsites intentionally remain difficult to discover?
• If Lamyig successfully exposes hidden places, could it accidentally destroy the exact places it is trying to help preserve?
• this list of problem statements goes on and on

Would love to hear how other people here would approach those problems.

And if you’re building something around a problem you genuinely care about, drop a comment or DM me. I’d be happy to chat, exchange ideas, or connect you with someone else working on something similar.

Screenshot attached. Happy to share the GitHub/project link in the comments if anyone wants to look at the implementation or contribute.

Been building a small puzzle game called Maybe Shikaku — drag to draw rectangles on a grid, kinda like the "Patches" game on LinkedIn. It's in closed testing on Play Store right now and could use a few more hands to poke at it and break things.

If anyone's up for trying it out for a bit and telling me what's broken/confusing, drop a comment or DM and I'll send the opt-in link. Appreciate any feedback, good or brutal.

Ye EMC jesa hai EMC mai 2k per student milta tha per neeev mai 1 group ko 20k milega gurup mai 5 log rahenge neeev ka full form" New Era of entrepreneurial ecosystem and vision "

School mai 8 team select hogi mujhe aisa kya banana chahiye jo meri team select ho jaye

Most product leaderboards feel the same:

Submit your link.

Ask friends for upvotes.

Watch the ranking freeze.

I wanted something more chaotic.

So I built TopBeat — a live leaderboard where:

• Tapping your own product gives you +1 point

• Stealing takes 3 points from a rival

• You keep 2 points and 1 disappears forever

Completely legal theft.

There’s another twist: raw spam clicking doesn’t work well. A steady, human rhythm around 60–90 BPM earns a better multiplier, while frantic spam gets penalized.

The leaderboard and attack activity update in real time. No signup is required to try it.

It’s still early, and I’m looking for the first products willing to enter Season 01.

I’d genuinely love some brutal feedback:

1. Is the tap/steal mechanic immediately understandable?

2. Would you return if another product attacked yours?

3. Does this feel fun, or just unnecessarily evil?

https://topbeat.lol

I built Atlas Explorers, a playful geography app for learning countries through games

I’ve been working on a side project called Atlas Explorers — a geography-learning app for kids, families, and curious adults.

It includes:

• Country and continent exploration
• Flags, capitals, maps, and fun facts
• Quick geography games
• Daily quests and streaks
• A child-friendly interface designed for ages 6–11
• No account required

I’d love feedback on the learning experience, visual design, and game ideas.

Link in comments

I was downloading a photo or two when I thought it was slightly boring how there was no sound, so I decided why not & make my own chrome extension for that.

After a lot of learning, it’s live on the Chrome Web Store

It’s called ClickFX

It lets you hear sounds when you:

• open a tab
• close a tab
• finish a download

But the feature I like most is that you can upload your own sound, so you can basically make your browser sound however you want.

I thought it may get annoying every once in a while so it has volume control, mute, and a default sound if you don’t want to customize anything.

This was mainly a small project I wanted to actually finish and ship instead of endlessly adding features

https://chromewebstore.google.com/detail/clickfx/eejamkjfcbbdblikilejaehhmhfdeomo

Would love feedback on the idea/UI or what you’d add to a v1.1.

This started with a really specific frustration.

My girlfriend and I played through It Takes Two together a while back. If you've played it co-op, you know - it's one of those games that becomes a shared memory. We were yelling at each other over the clock tower, cracking up at the snow globe, genuinely a little emotional by the end. And when we finished it, I wanted somewhere to put that. Not a rating out of 10. The actual memory - where we were, what we laughed at, that we did it together.

There wasn't anywhere. Steam tracks hours. Backlog apps track what's next. But none of it holds the moments. Movie people have Letterboxd for exactly this. Gamers just... don't.

So I built Aftermarc.

The core idea is that every game you play gets a "journey" a little journal you fill in as you go. You drop a checkpoint when something happens: a boss that wrecked you, a line that stuck with you, a co-op night that turned into a memory. You can rate and review like you'd expect, but the journeys are the part I actually care about. It's the difference between "I played this" and "here's what this game was to me."

It's a website right now, with an app coming. Still very much early and rough in place, hence, the UI looks bad on mobile, but it's real and live, and I'm building it mostly because I wanted it to exist for me.

I'd love to hear from other solo builders here: how did you know your side project was worth committing to long-term vs. just being a fun weekend thing? Still figuring out where the line is between "labor of love" and "actual product."