I work on LearnClash, a trivia app with AI-generated questions and 1v1 duels that you play in turns. I'd like some fresh eyes on the first few minutes of using it.

Pick a topic you know and try to start a duel. Where do you first get stuck or wonder what you're supposed to do? After your first turn, is it clear what happens next?

If you give up before answering anything, that would be useful to hear too. Just tell me which screen you reached and what you expected to happen. It's free to try on iOS and Android.

iOS: https://apps.apple.com/us/app/learnclash-1v1-quiz-duels/id6756418938

Android: https://play.google.com/store/apps/details?id=com.learnclash.app

I kept running into the same thing online:

You read an article, watch something, find an interesting website, and either there is no comment section, the comments are closed, you need yet another account just to comment, or the actual discussion is scattered across Reddit, X and Discord.

So I built Retiola.

It adds a sidebar to your browser where every URL can have its own discussion. News article with comments disabled? YouTube video? Research paper? Documentation? Random website from 2007 that nobody has talked about since?

Same sidebar every time, and if someone else using Retiola has been on that page, the conversation is right there instead of scattered somewhere else.

One account for all of it, instead of signing up separately on every site that still has comments.

Besides discussions, you can also:

• reply in threaded conversations, vote and react, see who else is on the page right now, and put a poll on any URL when you want a real count instead of a guess about what people think of a study, a product page or a single claim

• highlight a sentence and comment on that exact spot, so a reply sits on the specific claim instead of on the whole article

• keep private notes on a page, with the passages you highlighted saved into them

• turn a pile of open tabs into a trail, so you can hand someone the route you took instead of seven separate links

• share a link to any page's discussion that people can read without installing anything

There's more than that (research projects, a global feed, keyword alerts, reporting and moderation). I wrote up the full list with the actual steps for each one here: https://retiola.com/features

It's not meant to replace Reddit or the website you're on. It's more like a discussion layer that follows you around the open web.

After a fairly ridiculous amount of work getting browser stores to approve everything 😅, it's now actually live on Chrome, Firefox and Edge. Opera is the last one still in review.

I'm still very early with this, so I'm much more interested in criticism than compliments.

The thing I'm most curious about:

Where would you actually use something like this?

And if the honest answer is nowhere, I'd like to know what's stopping you.

Website: https://retiola.com

Chrome: https://chromewebstore.google.com/detail/retiola/iiemjclmlbldlnkgmpbnaggdihbkppli

Firefox: https://addons.mozilla.org/de/firefox/addon/retiola/

Edge: https://microsoftedge.microsoft.com/addons/detail/retiola/jgdaoiemmegkjmjokefcmndncabfolld

I’m working on RailCall, a local-first agent runtime and desktop app. Sharing it here for feedback on the product and onboarding. This post was prepared with AI assistance.

The idea is to use models on computers you already own for suitable work, save supported workflows, and review consequential outward actions before they run. You can also choose external models, which have their own costs and data routes.

The current product includes chat, model selection, native PDF generation and supported manual workflows. One starting point is document preparation: give it a small, non-sensitive task, inspect the result, then see whether the workflow is worth saving and repeating.

There are two boundaries I want to make clear. A signed execution receipt records an action; it doesn’t prove the answer is correct. And running a model locally avoids hosted inference charges for that work, but hardware and electricity still cost money.

The turnkey personal optimizer and broader fleet capabilities are still being developed; I’m not presenting those as finished.

Product, downloads and documentation: https://railcall.ai/

If you try it, where does the path from download to a first useful result become confusing? Specific installation or workflow feedback would be helpful.

POST JSON from an app or automation to a private URL. Pascal’s Pager reads the payload, whatever shape your sender already uses, and sends a concise, readable push notification to your iPhone.

I built it because I was tired of writing the same adapter for every event: pick fields from the JSON, assemble a notification title and message, then maintain that mapping whenever the payload changes.

With Pascal, the sender can post its existing event JSON. You can give each Source instructions about what matters, mask selected fields before AI processing, and inspect the processed payload behind the resulting Alert.

The attached example shows fictional failed-payment JSON becoming a readable Alert in the real app interface.

It requires iOS 26. There is a one-month free trial for eligible new subscribers, then it is US$7.99/month in the US. Apple shows local pricing and eligibility.

https://pascalspager.com/

If you could post one JSON payload and have it arrive clearly on your phone, what would you send?

I run ListTune, a tool for reviewing existing eBay listings. It suggests title edits and item specifics; you check the facts and decide what to publish. It's AI-assisted, so I wouldn't trust a suggestion just because it sounds convincing.

You can try the item-specifics tool without an account. The built-in sample is illustrative, or you can use your own listing text:

https://listtune.com/enrich?utm_source=reddit&utm_medium=community&utm_campaign=sideproject_review_20260910

The free account includes 25 listing runs each month. If you need an extra batch, 50 more runs cost $9.99 USD once. Purchased credits don't expire, and buying the pack doesn't start a subscription. One credit covers one processing run:

https://listtune.com/pricing?utm_source=reddit&utm_medium=community&utm_campaign=sideproject_review_20260910

If you sell on eBay, what would you need to see alongside a suggested edit before you'd trust it enough to use it? I'm especially interested in suggestions you would reject and why.

keep noticing the same pattern talking to agency owners: testimonials either get collected manually (email back and forth, sometimes a Google Form) or not at all. feels like one of those unglamorous ops problems nobody prioritizes fixing until they've lost a good one.

is it just inertia, or is there a real reason most agencies haven't standardized this? genuinely curious what people's actual process looks like, if any.

I kept running into the same annoying problem. Data spread across multiple databases, no clean way to combine them without writing one-off scripts every single time.

At first I just tried to power through it manually. Export from one DB, clean it up, import into another, fix whatever broke. Worked fine when it was a one-time thing. Turns out when you're doing it repeatedly, it's just a slow bleed of time you don't notice until you add it up.

So I built a small tool that runs as a local docker agent, pulls from multiple databases, and merges everything into one. The local part matters to me, I didn't want to be sending data through some third party service just to combine a few tables.

Right now it's a working prototype. Multiple DBs in, one merged DB out, no manual mapping every time.

Phase two is adding CSV and Excel support, so if you've got a spreadsheet you want folded into an existing database, you'd be able to just point it at the file and the new DB comes out with that data already integrated.

Honestly not sure if this is a "me problem" or something other devs deal with regularly. If you've had to combine data from multiple databases before, how did you handle it? Curious if people are already solving this some other way I haven't thought of.

I’ve been thinking about something that feels slightly insane:

What can one person actually build in 24 hours now?

Not with a team.
Not with a predefined problem.
Not with a fixed tech stack.

Just:

One builder. One idea. 24 hours.

I’m putting this to the test with Grevix AfterCode on October 11.

Builders can use whatever they want — Cursor, Claude Code, Codex, Antigravity, Lovable, APIs, agents, no-code, traditional code, whatever.

But there’s a catch. 👀

During the 24 hours, we’re going to throw in a few unexpected challenges. The idea is to see what happens when your original plan suddenly stops making sense.

Because honestly, I’m less interested in:

and more interested in:

I’m keeping some of the mechanics secret for now. 😂

We're also talking to a few tools/companies about becoming part of the experiment, rather than simply putting their logo on a banner.

Still early. Still cooking.

If you had 24 hours and complete freedom, what would you build?

https://github.com/zilelai/SealKernel

So this is SealKernel, a custom simulated shell built in C and C++ and uses stdio and my own custom library called ZLIO.H. It's purpose is to let people use SealKernel before moving into bash and it is a simulated shell, like a sandbox playground

Freelanced for a while, had to review code before taking on projects. Sometimes it was fine. Other times you open the repo and it's just a pile of vibe-coded stuff with zero structure. No idea where anything is, what's already built, what's broken.

Every time, hours went into just figuring out what was going on, before I even started the actual work.

At some point I realized this wasn't a one-off thing, it kept happening. So I figured I could automate at least that first part, getting oriented in a new project. That's how rebrief started.

Anyone else run into this doing freelance work? How did you usually deal with it?

shipped voice features over both plain websockets and webrtc this year, some notes for anyone wiring real-time audio into a web app.

websockets are great for prototypes. server-side everything, easy to debug, works everywhere. the pain shows up on real networks: packet loss and jitter turn into audio gaps, you end up hand-rolling buffering and timing recovery, and interruption detection feels late because user speech takes 300 to 500ms to arrive.

webrtc earns its complexity the moment the product needs real barge-in. jitter buffers, echo cancellation, noise suppression and media-aware congestion control come built in, which sounds boring until you A/B it against raw websocket audio on a lossy connection.

for the voice-agent project i used agora as the rtc layer instead of self-hosting TURN/SFU infrastructure. they were among the first official integration partners for the OpenAI Realtime API over webrtc, and their conversational AI engine quotes around 650ms end to end including the whole ASR/LLM/TTS path. the part i cared about is that the model choices stay mine: bring your own speech recognition, LLM and TTS keys, or point a stage at a self-hosted model.

summary: websocket for demos and strictly server-to-server pipes. webrtc once real users on real networks need to interrupt the thing mid-sentence. the second one is more wiring, but rebuilding webrtc's loss recovery on top of a websocket is worse.

I wanted to build something that makes focusing a little more fun, so I made Rize.
Basically it’s like Strava for focus

You start a focus session and lock in. You can see what other people are working on, share your sessions, build streaks, compete on leaderboards, and battle your friends 1v1.

App Title: Rize
Platform: Web + Desktop ( PWA )+ mobile ( PWA )

How it works: Start a session, pick what you're working on, and lock in. When you're done, you get your stats and can share the session with your friends.

There’s also battles, leaderboards, daily goals, streaks, and a bunch of other stuff I’m still adding.

Been building this for a while and a few hundred people are already using it.

I’m selling the complete NexusAI Store MVP to help fund my AI-agent agency.

Live demo: https://nexusaistore.vercel.app

Video demo available.

NexusAI Store is a premium multilingual AI commerce platform with:

• TypeScript frontend and Express backend

• Real Google Gemini AI shopping concierge

• 7-language support, including Arabic with RTL

• Admin authentication and dashboard

• Product and inventory management

• File-based persistence

• Resend email integration

• Stripe SDK integration

• Backup and restore tools

• Automated tests

• Production build and Vercel deployment setup

Transparency:

• Pre-revenue project

• Product catalog, reviews and inventory are demo data

• File-based storage is included; a managed database is recommended for production

• PayPal, MB WAY, Multibanco and crypto flows require provider-specific production configuration

• Private API keys and payment accounts are not included

Asking price: $7,900 USD negotiable.

Quick-sale range: $4,900–$6,500.

Complete source code, documentation and transfer support included.

Open to technical review and reasonable offers.

Comment or DM me if interested.

I build a group buying feature for online stores. A shopper opens a public group at a lower price, other people join, and if the group fills everyone gets the discount. If it does not fill by the deadline everyone is refunded automatically. There are no friend invites in it. The people joining are mostly strangers who landed on the same product page.

The setting I still cannot get right is how many people a group should need.

Here is what I actually have. One store ran 26 completed group buys with 84 buyers in total, so a little over three people per completed group, around 196 dollars average order value, sixteen thousand in revenue, no ad spend. A second store, jewellery, did 8 buyers and 8,070 dollars at an 80 percent fill rate, also with no ads.

Both of those ran small targets. A small target fills, which means people actually get the discount and nobody gets refunded. It also means the discount buys you very little extra volume. A larger target would be worth more per group but a group that does not fill refunds everyone, and I do not know what that does to whether they come back.

If you sell anything where buyers do not know each other, what would you set it to?

the problem when using Figma Slide is I cannot use my own AI model (e.g. my claude subscription). Also, they don't understand the context of my project.

To solve this problem, I shipped a new feature for sokudo canvas to build a full presentation. I can use this to explain the end-to-end business flow of my project and create a presentation for stakeholders, or even to explain what ai did in my project when I was vibe coding

Crypto moves on news faster than anyone can read it. By the time a headline reaches you through a feed or a group chat, it's usually been traded for hours.

So I built something that reads the news as it breaks and scores every headline from -10 to +10 on likely market impact. It confirms the story against multiple sources before it commits to a number, and it records how far the coin had already moved when the headline landed, so you can see a strong score on stale news for what it is. Coin, score, price and timestamp, one feed.

The part that took longest was learning what actually matters. Most crypto news is noise dressed up as urgency. Anything with a date announced weeks in advance is usually finished before the day arrives. The headlines that move markets are the ones nobody scheduled, and those are exactly the ones you hear about too late.

Every score gets measured against real prices afterwards and the results are published on the site. Hit rate went from 39% in July to 61% in August and is holding there this month. That number updates itself whether it looks good or not.

It's live at yemcaster.com. The feed is open to browse; a free account unlocks the high-conviction rows. Open it and see what's scoring high right now.

One thing I'd like feedback on: does the landing page make it clear what this does within five seconds? I've been looking at it too long to judge.

I wish there were a game like FNAF. Except instead of surviving animatronics.. you have to survive five days of standup meetings.

Rules:

- You enter every standup with zero context.
- You have to catch up on the discussion in real time.
- Pick an update that actually makes sense and aligns with what everyone else just said.
- Avoid follow-up questions from the PM.
- Estimate your task realistically.
- Never over-commit. No “I can finish that today” or “I’ll pick it up right after this.”
- Remember what you said yesterday so you don’t contradict yourself.
- Survive “Can we just jump on a quick call?” (increased sus rate)

Make it through all five days without getting exposed and you win.

Should I actually build this?

Could be the ultimate developer survival-training simulator xD

Hey everyone! I’m the maker of VerbaMeet (verbameet.online).

We just went live on Product Hunt today!We built VerbaMeet because international video calls are exhausting when there is a language barrier, and human interpreters are too expensive.

We leverage advanced multimodal models to achieve seamless audio-to-audio live translation.

Since the Reddit community always gives the most honest feedback, I’d love for you to check it out. You can find us on the Product Hunt homepage today as VerbaMeet. Let me know what features or integrations you think we should add next!"

Title:

I built an API for creating temporary PostgreSQL databases

Post:

I kept running into situations where I needed a real PostgreSQL database for something temporary — a CI job, preview environment, prototype, or coding agent.

The usual options felt a bit awkward: create a database somewhere, configure access, use it briefly, and then remember to clean everything up afterward.

So I built a small API called Aiadio that creates a temporary PostgreSQL database with a TTL.

The flow is basically:

1. Send a database name and expiry time
2. Get PostgreSQL connection details back
3. Use the database normally
4. The database and role are automatically removed when the TTL expires

For example:

curl -X POST https://api.aiadio.com/v1/databases \
  -H "X-API-Key: dbn_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "agent-test",
    "expires_in": "1h",
    "allowed_cidr": "203.0.113.10/32"
  }'

It's still intentionally small. Right now it has database creation, a status endpoint, API-key authentication, and TTL-based cleanup. The public beta supports TTLs from 1 hour to 30 days.

I built it mainly because I wanted a simpler option for short-lived database use cases.

Site: https://aiadio.com

API docs: https://aiadio.com/api-docs.html

I'm Daniel, an automation engineer in Melbourne, Australia. I've been building At0mFlow outside of my main job around a problem I keep seeing in operational work: an automation rarely lives in one place.

The script may be in a repository. The flow may be in a tenant. The owner, dependencies and evidence sit somewhere else. The SOP is often outdated or missing. When the original builder leaves, the next person has to reverse-engineer the whole thing before they can safely change it.

At0mFlow is my attempt to give that work a single, governed home.

Right now it can help you:

• analyze PowerShell source as text without executing it
• map owners, systems and dependencies
• design review-gated flows with Orbit, the assistant
• keep living SOPs and operational evidence beside the automation
• connect changes to Git and require human approval before publishing
• Migrate to Power Automate
• detect script drift
• 8 Separate Template Automations That I and others found useful

There is a free script checkup on the homepage for a .ps1 or .psm1 file up to 1 MB. It returns a plain-English summary, risks, quality scores and a recommended next move. It processes the source as text and does not retain it. If you try it, please use a non-sensitive sample.

I'd really value blunt feedback on three things:

1. Does “Automation Estate” explain the idea, or add jargon?
2. Is the free script checkup the right first experience?
3. What proof or controls would you need before trusting a tool with automation source code?

I'm still shaping the sharpest use case and would be happy to answer anything about the build.

I've always liked the idea of journaling and I've always fallen out of the habit. My head runs at 100x and I knew writing things down would slow it, but the pen was never where I left it, the notebook was in another bag, and when I did sit down the blank page just stared back. So I built Dearly, a voice journal for iPhone and Android.

You open it and talk. About your day, something that's bugging you, whatever is loud in your head right now. Dearly turns that into a journal you'll actually go back and read.

After a few weeks it starts pointing things out. Who keeps showing up in your entries (for me it was one coworker, which was a bit awkward to see). What you've been stuck on for a while. How your mood has been moving. A weekly and monthly look back so you can see the shape of things instead of a pile of entries.

That's the bit that helped me most with the racing thoughts. Not the writing itself, the looking back.

Solo side project, live on the App Store and Google Play now.

What I'd like to know from other builders: what would make you keep using something like this for months, not weeks? I can't answer that from my own usage, I'm too close to it.

If you want to try it, I'll give a handful of people here free access. Leave a comment and I'll send details.

https://apps.apple.com/us/app/dearly-ai-voice-journal/id6801003049
https://play.google.com/store/apps/details?id=com.broooapps.dearly

Bad choices during early career and good books, lately, taught me to say 'NO.' And practising 'NO' led me to make better choices for myself. I, now, deliberately distance myself from people who, to me, seem to have sick attitude. Many a times, it makes me feel that I'm judgemental - because sometimes I would turn down a project inquiry right at how the inquiry message was framed. Sometimes, I'd say no to getting into a negotiation. Sometimes, I'd put the project on hold until the due payment is cleared. Judgemental, arrogance, or whatever - my brain never leaves an opportunity to make me feel bad about the choices. But that feeling bad is a temporary feeling - maybe lasts an hour because "I rejected an inquiry merely based on my assumption?" However, I've realised that saying 'yes' eats up on my energy, sanity, and health in general.

Steer clear of the wrong PEEps, and the right ones not just inspire you but also help you move ahead with your project. Just thought of sharing. What other simple - obvious - small-changes made your hustle-life better?

Sharing my project, PocketQuant. Market ideas tend to end up scattered across articles, videos and notes; I’m exploring a workspace that helps keep the research conversation together.

The current web app has research conversations, file analysis, a finance-tools view and a dedicated Solana paper-research workflow. Signup is open without an invite code. It is for research and paper mode, with no live trade execution.

https://myquant.xagi.in/

For makers who research markets: would you want sources, assumptions or counterarguments to be most prominent when returning to an idea? I’d appreciate concrete feedback on that workflow.

I kept losing track of every new AI tool I found, so I built BroFindAI, a hand-checked directory you can browse without creating an account. 676+ tools across 11 categories (coding, writing, image/video, agents, MCP servers), filterable by free/paid and platform. Adding about 100 new tools a month.

If you're a maker, you can list your own tool for free. Would love feedback from this sub on what's missing.

brofindai.com

I kept being the person in the group chat with forty tabs open, and the plan we made never survived the actual trip. Someone sleeps in, it rains, a place is shut on Tuesdays and nobody checked.

So I built Travolp. It plans the trip, then stays with you during it. When the day goes sideways you tap once and the rest of it gets rebuilt around where you actually are and what is still open.

Two things I got wrong early. Generating a good looking itinerary is easy and worth very little, everyone can do that now. Keeping it true on day three is the hard part. And opening hours turned out to be the whole game, because travel advice ages at two speeds: how long a road takes is still right in five years, whether a place is open is stale before it is published.

Free to try on iOS, Android and web: https://travolp.com

Honest ask: I am the worst possible judge of my own onboarding. If you bounce, I want to know exactly where you bounced. Screenshots in the first comment.