The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Someone asked why ATS FastScan uses both Firebase and Supabase, since usually one tool covers what the other does too.
Fair question. Here's the actual reasoning:
Firebase handles login only. Fast Google sign in, zero friction, since job seekers won't tolerate a clunky signup flow.
Supabase handles the data. Postgres with row level security, so tenant isolation is enforced by the database itself, not by my application code. If I ever ship a bug in my API logic, the database still refuses to leak one tenant's data into another's.
For a product processing resumes and personal info, that's not a nice-to-have. It's the difference between isolation being guaranteed vs isolation depending on me never making a mistake.
Two tools, each doing the one job it's strongest at. Not redundancy, division of labor.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Patitas & Tijeras: from "can I book?" to "you're booked" for a solo dog groomer in Lima
One-line problem: Mariela grooms one dog at a time in Surco, Lima, and loses about 2 hours a day on WhatsApp while 1 in 5 clients never show up.
THE BUSINESS
Patitas & Tijeras is a one-woman grooming studio in Santiago de Surco, Lima. Its quirks shape the whole product:
One dog at a time, never in a cage, so the calendar can never double-book
Slot length depends on the dog: a chihuahua takes 45 min, a matted golden takes 3 h
15 protected minutes between dogs to clean the table
Saturdays fill first; weekdays have room
Clients pay a deposit by Yape (Peru's most used payment app) to hold a slot The business is fictional. The problem is real for thousands of small shops in Lima.
FOR CLIENTS
Book in about a minute: breed, size and coat set the exact slot length, so only times that really fit are shown
A Yape deposit holds the slot. A booking can't be confirmed until the deposit arrives
Every booking gets its own page with a QR code and clear next steps
Waitlist and reminders; returning clients are recognized by phone number
Spanish and English, detected automatically
FOR MARIELA
Inquiry inbox: "got a slot Saturday?" gets real times back in one tap
QR check-in on arrival, with clear warnings for codes from another day, cancelled or already used
Regulars with no no-shows in the last 90 days can rebook without a deposit
A dashboard with revenue, occupancy, no-shows and hours saved
In the demo data, no-shows drop from 21% to 4%
HOW IT'S BUILT
Built entirely in Lovable on Lovable Cloud (Postgres, auth, storage): 21 versions in about 18 hours. Overlapping bookings are blocked by the database itself, not just the interface. Most fixes came from testing it on my phone as a real client would.
TRY IT
Live app: https://patitas-y-tijeras.lovable.app
Owner view: "Studio login" → "Enter the demo as Mariela" (demo data resets every night)
Lovable project: https://lovable.dev/projects/2549d272-0442-42a4-b7b3-52122c971817
Process video: https://x.com/Sebas_TZ_/status/2104022416062312659
Social post: https://www.instagram.com/p/DdxTkJYmmTa/?img_index=1
Built with @Lovable #lovablechallenge
How does the app know a Yape deposit has arrived before it confirms the booking? Does Mariela confirm it from her phone, or does the app read the payment itself?
What I Built
I built Glow & Grace, a self-service booking website for a solo, home-based nail studio in DHA Phase 5, Karachi. Clients can view services and prices, pick an open time slot, and get instantly confirmed — no messages exchanged with the owner. The owner has a simple dashboard where every booking appears automatically, along with deposit status, so there's no manual confirming or texting required.
Why I Built It
Solo, appointment-based businesses like small nail studios, salons, and home-based service providers often run entirely on WhatsApp. The owner is doing the client's nails with one hand and replying to booking messages with the other — checking availability, confirming times, and texting reminders, all manually. This doesn't scale, wastes hours every week, and leads to double-bookings or missed messages. I wanted to solve the actual bottleneck: turning "can I book with you?" into "you're booked" without the owner lifting a finger, while also addressing the no-show problem with a small deposit built into the booking flow.
Soical Post Link: https://lnkd.in/p/dbXGPbzt
I love the color style
ESG reporting is a workflow problem as much as a data problem: teams need applicability rules, evidence, consolidation, review, and approvals before a report is ready.
For OriginSustain, I built NestJS/TypeScript backend services, PostgreSQL and Redis/BullMQ processing, and AWS/Docker delivery with CI/CD. OpenAI API and RAG support part of the reporting flow. The screens here are from the product’s illustrative command center; the numbers are demo values, not client outcomes.
The full backend case study: https://contra.com/p/WvNXbmQR-origin-sustain-or-multi-tenant-esg-reporting-backend
