We built Protocall five years ago, used it internally every day since. But when we decided to launch, we knew there were still plenty of things to fix and add. So we had two options:
Don't launch and spend another year making it great on our own, going only off internal team and client feedback.
Find people who'd actually share their feedback and help us get there much, much faster.
One decision I went back and forth on for a long time: whether to add rewards for testing and feedback, or just ask people nicely.
Since testing a product properly, reporting a bug that's actually reproducible, or writing up an idea that's usable looks like real work. It's literally someone's job internally, our product owner and QA engineers get paid to do exactly this. Asking strangers to do the same thing for free felt like asking a favor we wouldn't ask of our own team without paying them. So we set up a small pool: $10 to $200 per contribution.
Most parking apps show you the rules for a street. ParkSpot shows you the streets with the best chance of an actual free spot so you stop circling and go where the odds are good. Free, ad-free, no login, built on Stockholm s open data. News See which nearby streets give you the best shot at parking right now Evening & morning combined into one automated view when to park, when to move Motorcycle parking Accessible parking Try it: parkspot.se feedback welcome, especially from Stockholm drivers.
Okay so this is either a really good idea or a really embarrassing one. Genuinely can't tell anymore.
I've been building an AI-powered astrology oracle for the past few months. Not the vague "you're a Scorpio, you feel deeply" kind. Something that actually goes deep combining 5 different astrological systems plus Tarot into one coherent reading.
Over the past few weeks, I've been building Launch Pilot an AI co-founder designed to help indie hackers and solo founders launch with more confidence.
The idea came from seeing the same problems repeated over and over: shipping without validation, unclear positioning, weak ICPs, and launch plans based more on guesswork than evidence.
I m building Storio, a small web app for sharing story time with friends and family. The current version includes a library of classic stories and simple Create and Read experiences. I m trying to understand a bigger question: what makes a digital story experience feel genuinely shared, rather than just another screen? For parents, grandparents, families, and makers here: Do you prefer guided classics, original stories, or a mix? What would make you invite someone else into a story session? Which parts of reading together should stay deliberately simple? If you d like to see the current experiment: https://storio.web.app/ I m not looking for upvotes specific feedback on the experience, audience, or what feels missing would be most useful. Happy to answer questions and participate in the discussion.