Completed my exam-proctoring SaaS — AI-powered exam creation, live proctoring, real-time analytics. Built with Next.js, LLM APIs, and computer-vision-based monitoring.
Live proctoring + real-time analytics on top of Supabase is a great fit — Realtime channels handle that kind of continuous state well. Curious how you're structuring the video/behavioral data pipeline (raw events vs. pre-aggregating for the dashboard). I hit similar tradeoffs on
Pawline: booking built around the van, for mobile pet groomers
Pawline is a booking system for a small mobile pet grooming business: one van, two groomers, three Austin zones.
Most booking tools treat a mobile groomer like a salon. The real problem is logistics: travel fees by zone, visits with several pets that take different amounts of time, and one van that can't be double-booked.
What it does:
🐾 ZIP check with instant zone travel fees
🐾 Live pricing and visit length for up to 4 pets, including add-ons and setup time
🐾 Only shows time slots the van can actually fit, and respects the owner's blocked time
🐾 Private links so customers can reschedule or cancel without an account
🐾 Owner dashboard with a daily van timeline
🐾 Public demo mode with fictional bookings and hidden customer details
Built for real use: owner-only data access, leaked-password protection, and full end-to-end testing on desktop and mobile.
🤔When applying to jobs, I often see requirements like “advanced Figma skills” or “using best practices, Auto Layout, components, variables, etc.”
Come on, this is the basics.🤷🏻♀️
As a designer with 10+ years of experience building SaaS web applications, I see these things as a foundation, not something that should even need to be asked about.