I ve spent years in marketing, and there s one thing that always drove me crazy: The massive gap between what Meta claims is happening and the reality of our bank accounts.
Meta loves to show us link clicks and high CTRs to keep us spending, but we know that many of those clicks are just ghosts accidental taps, bot traffic, or low-intent engagement that never reaches the checkout page.
I'm building CleanLedger, an early iPhone prototype for independent cleaners. It records cleaning and travel time, direct costs, invoices and payments received, to compare hourly earnings before tax and owner labor and see unpaid balances. Records stay on the device; no login is required.
My biggest uncertainty: is the benefit worth entering each visit?
Hi everyone! I m a first-time app builder working on CYPHER, a live dance battle app for iOS (16+).
How it works: two dancers, one track, 4 rounds of 10 seconds. The audience votes in real time, and anyone watching can challenge the winner, so spectators become competitors. Besides 1v1 battles, there s a Party Mode for up to 6 people, a rhythm mini-game for anyone not ready to turn their camera on, and Chaos Mode, where judges pick one of two challenges for the dancer (like next round, dance like your drunk uncle at a wedding ).
I m about to start a small closed beta. Live video is costly to run, and the app can t be a paid download, so I m trying to figure out if this can be sustainable before I go all in. I d love your honest take:
Hey everyone, I'm here to showcase my project that I just built for the BharatCode Build League, and I am looking for some technical feedback.
The Problem: Freelancers lose billions to chargebacks because banks reject messy WhatsApp/Slack screenshots as legal proof of work.
The Solution: I built NYAYA-AI, a Sovereign AI defense engine that cross-references your contract against your raw chat logs to instantly generate a Visa/Mastercard-compliant rebuttal dossier.
Because AI hallucinations in FinTech are dangerous, I built this with strict architectural constraints:
I'm on the Yooada team. We're working on a voice-first assistant for email, calendars, notes and follow-ups, still pre-launch.
Our demo brief got less glamorous this week: take one client follow-up, change the date, close the screen, then reopen it. Show the right person, the right date and what actually got saved. A cheerful 'Done!' isn't much comfort if Friday is still lurking somewhere else.
This is what we're asking the demo to prove, not a claim that we've already solved every edge case.
If you handle your own client work, what would you insist on seeing before connecting your inbox: where drafting stops and sending starts, whether rescheduling sticks, or how it picks the right person? Something else?
Google Forms is great for collecting responses. But who makes sure every request gets assigned, who followed up, and actually handled? How do you make sure nothing gets forgotten?
That's the problem I wanted to solve when I started building Form Watchdog, a Google Workspace Marketplace add-on that turns Google Forms responses into organized team workflows. With automatic assignments, conditional routing, deadlines, reminders, notifications, and more.
Every time I started a new project, I found myself doing the same thing: setting up the framework, auth, database, storage, caching, Docker, CI, and all the little pieces that make a project ready for actual development.
Initially, I wanted a starter template I could reuse. But I kept running into another problem: not every project needs the same stack.
Sometimes I want Next.js or TanStack Start. Other times, I want React + Vite on the frontend with a separate backend. I don't want to maintain a completely different boilerplate for every combination.
That's why I built Clubedge Starter and its CLI, @clubedge/create-clubedge-app.
