Dental offices lose thousands every month to insurance denials nobody has time to fight.
We built AppealMD to fix that.
Waitlist link in bio.
#BuildInPublic#ZeroToOne
@JunaidAckroyd Built get https://t.co/XCDwiBqf67 a 3-step AI agent that turns dental insurance denials into payer-specific appeal letters in <30s. Full stack, no LangChain, every step typed and auditable.
TV Routine just hit its first real milestone.
You can now:
β’ Sign up
β’ Log in
β’ Stay logged in
β’ Edit your profile
Feels good when a project starts acting like a product instead of a collection of pages.
#nextjs#supabase#buildinpublic
@sujaldkl Ohh this is new or me, everyone trying to get in and you decline an interview. Big straight spine man, you will definitely make it πͺ keep pushing
Building something people said was a bad idea?
Drop it below.
I'm building an app that deliberately stops you from watching the next episode. People think I'm crazy.
Curious what "bad idea" you're shipping anyway.
Do you actually enjoy binge-watching or do you just do it because it's there?
Asking because I'm building something that forces you to watch one episode at a time on a schedule and I'm genuinely curious how many people would use it vs. how many would find it maddening.
The hardest bugs aren't the ones that crash your app.
They're the ones that fail silently.
Wrong Supabase URL β no error thrown, requests just vanished. Took me longer to find than any loud exception would have.
Silent failures are more dangerous than loud ones. Build systems that fail loudly or you'll spend hours debugging air.
Binge-watching isn't a feature. It's a dark pattern.
Netflix and every other platform optimized for "just one more episode" because watch time = revenue.
Nobody asked whether that was actually good for users.
TV Routine does the opposite β it locks episodes on a schedule and makes you wait.
Sounds annoying. Feels like watching TV used to feel before streaming ruined anticipation.
Phase 2 of TV Routine is done.
Built the full auth + profile layer: sign up, log in, stay signed in, protected routes, profile management backed by Supabase.
Hit two real bugs along the way:
β Wrong Supabase URL silently broke signup requests. No loud error, just requests disappearing into the void. Fixed by auditing the env config carefully.
β Server-side session bug blocked profile loading entirely. Took longer than I'd like to admit to trace it to session hydration timing on the server.
App went from foundation work to a functioning authenticated experience.
Phase 3 next: TV show search via TMDB API.
#BuildInPublic
Teams building AI products keep adding agents and prompts when the actual failure is bad input. A cheap validity gate before the model runs catches 80% of the nonsense and stops confident hallucinations dead. Seen it across three different apps now.