@Puneet626 · X

hi, let's connect, i'm building

@orilekunke_ · X

@nundinaapp · X

I dropped 😋

@Joyerz5 · X

@abhishekbariyaa · X

@AbhinavtejR · X

u/MainNail9026 · Reddit

Killing Luma and Partiful in 2026 I built an AI co-host that actually does the event logistics, not just the invite page Every group chat I've been in dies the same way: five people say "we should do something," someone suggests a date, three people don't reply, and it's dead. Currently the tools that exist (Partiful, Luma) are great at making a pretty invite and then sending to an RSVP list. But the invite is the last 10% of the work. The other 90% is picking a place,

u/Accomplished-Top8168 · Reddit

Looking for honest feedback on the productivity app I've been building finally got tired of juggling 5 different productivity apps, so I've spent the last few months building my own. I call it BusyMind AI. instead of just storing notes, it tries to help you turn thoughts into actions. A few things it can do: AI summarizes messy notes and pulls out action items automatically. Records voice notes and has them transcribed. Built in calendar for scheduling events, tasks or reminders.

@HossainArif85 · X

Building — a platform for paid events where organizers manage registrations, approve payment proofs, send QR tickets, and check attendees with any phone browser. Happy to connect with fellow builders!

@lynkxapp · X

@harryjwang · X

I've used many of the major conference systems. Plenty still have docs as an unsearchable static site — or worse, as PDFs that stopped tracking the product three versions ago. Somehow, still true in 2026. We took an AI-first path with instead. Our docs are generated from the codebase itself. A custom Claude Code skill writes each page and retakes the screenshots whenever a feature changes — so the docs don't drift from the product. Every page still gets reviewed by a human before it ships. Now you can talk to them, too. We just shipped "Ask AI" over our docs: This feature also turned out to be a nice teaching case for agentic RAG vs. classic RAG: • Classic RAG: chunk → embed → vector DB → retrieve once, by fixed rules • Agentic RAG: hand the model a search tool and let it drive — write a query, read the results, rewrite, retry At more than 100 pages, still no vector database needed. And every answer cites the exact page it came from. #Age

@HaiderA73446923 · X