Built BARK & BUBBLE πΎ for the @Lovable challenge β a booking experience for a solo mobile dog groomer where scheduling isnβt just about finding an open time.
The flow considers the dog, service time, location, and the vanβs existing route to suggest smarter appointments. Customers can book and pay a deposit without the usual back-and-forth, while the ownerβs schedule updates automatically.
My favorite part: when a cancellation happens, the system checks the waitlist, finds the best route-friendly match, sends the offer, and fills the opening if they accept β without the owner having to chase anyone.
From βCan I book my dog?β to βYouβre booked.β πΆπ
1
188
What if your family needed critical information tomorrow and couldn't reach you?
Family Vault uses AI to help families organize essential information, identify preparedness gaps, and stay ready before emergencies happen.
Built with Figma Make.
https://notice-decay-17883734.figma.site/
Been freelancing on Contra and building a tool for freelancers at the same time lol.
It's called ProposalForge. You give it a client brief and your rate and it drafts the proposal, and I use it on my own drafts too.
It's live now and free to try (3 proposals, no card). The video shows a free checker I made along the way that marks the phrases that make a proposal sound like ChatGPT. No sign-in: proposalforge.site/check
I'm trying to see where people actually get stuck. What part of writing a proposal takes you the longest? The opening, scoping and pricing, or just getting started?
Mudroom
It screens incoming mail, surfaces what needs a reply, holds the rest. Gmail and Outlook. A dollar for three days then ten a month.
Link to project: mudroom.email (http://mudroom.email)
3
7
731
Automate Product Master Data with RUNMYBOT
Simplify product data extraction from Commercetools with secure, API-based automation.
RUNMYBOT Connect Systems. Automate Data. Drive Efficiency.
π¨ βIt works on my machine.β The developer's most dangerous sentence π
Your app works perfectly locally, then suddenly breaks in production.
Before blaming the code, check:
πΉ Environment variables
πΉ Node.js versions
πΉ Database connection
πΉ API URLs
πΉ CORS configuration
πΉ Production build settings
Local success β production readiness.
Always test your application in an environment as close to production as possible.
Whatβs the funniest βworks locally, breaks in productionβ bug you've faced? π
4
11
618
π¨ The API is returning 200β¦ but your data is wrong?
This can be harder to debug than a clear error.
When I troubleshoot backend issues, I check:
π Database queries
π API request/response data
π Authentication state
π Backend logs
π Frontend data handling
A successful API response doesn't always mean the application is working correctly.
Sometimes, the real bug is hiding in the data flow.
Have you ever spent hours debugging a problem that turned out to be one small line of code? π
4
10
649
Getting this error in Next.js? Youβre not alone.
Hydration failed because the initial UI does not match what was rendered on the server.
This usually happens when your server-rendered HTML doesn't match what React renders in the browser.
Common causes:
β’ Using window or localStorage during server rendering
β’ Rendering different content based on browser-only values
β’ Incorrect date/time rendering
β’ Invalid HTML nesting
My first fix:
Move browser-only logic into useEffect, or make the component client-side when necessary.
π‘ Tip: Don't just hide the error. Find out why the server and client are rendering different UI.
Have you encountered this error before? π
2
18
598
Building digital products that solve real problems. π
Recently, I've been working on projects across mobile apps, user experiences, and digital products, turning ideas into functional experiences that people can actually use.
I'm excited to keep building, learning, and collaborating with great people here on Contra.
What are you building?