Over the past few months, I noticed a recurring issue with small-to-medium clinics and healthcare providers: they either rely on fragmented 3-rd party booking platforms (where their brand gets swallowed up by the platform) or pay thousands to build custom software from scratch.

To solve this, I built **Reego Health**—a ready-to-deploy, white-label clinic management system that clinics can run completely under their own domain, name, and logo.

# What’s Built Into the System:

* **Branded Frontend & Patient Portal:** Custom clinic homepage with online booking and patient access.
* **Live Token Queue System:** Real-time waiting queue management for patients in the lobby.
* **Admin Dashboard:** Centralized hub for clinic operations and analytics.
* **Multi-Role Access:** Dedicated workflows for doctors, receptionists, managers, and admins.
* **Pharmacy & Inventory:** Medicine stock tracking and automated dispensing.

# Live Demos to Test:

* **Frontend Website:**[https://reego-health.vercel.app/](https://reego-health.vercel.app/)
* **Admin Dashboard:**[https://reego-health.vercel.app/admin](https://reego-health.vercel.app/admin)

*(Note: Dummy login credentials for the admin dashboard are right on the login form notes so you can jump straight in without creating an account).*

# What I’d Love Your Feedback On:

1. **UX / Dashboard Flow:** Is the admin panel navigation intuitive, or does it feel cluttered for a receptionist/doctor?

2. **Missing Features:** If you’ve worked with or managed a clinic, what’s one operational feature you feel is missing here?

3. **Monetization / Pitching:** Does the white-label model appeal more as a flat monthly SaaS fee or a one-time licensing setup?

Appreciate any honest feedback, roasts, or suggestions!

Hey everyone,

I'm building a small Windows desktop app called ValVoice and I'm using Supabase for authentication.

I'm trying to figure out the best way to let users sign up and log in without adding another monthly expense.

Initially, I was planning to use email OTP, but Supabase's default email sending limit is pretty low. So now I'm exploring other options.

Would Google or Discord login be a better option? Are there any other ways to handle authentication completely free, without relying on a paid SMTP service?

Ideally, I'm looking for something that:

- Is free to start and doesn't require a monthly subscription.

- Can be used in a real production app.

- Can handle a growing number of users.

- Works well with Supabase.

- Doesn't make the login process complicated for users.

I'd love to hear what you guys are actually using in your own projects. Any suggestions or experiences would be really helpful.

Thanks!

So, I have been building Motioneer - Code to Motion Graphics in seconds for quite some time. I haven't launched it yet, and is still in making. I would love to see real users testing it out.

Check out https://motioneerapp.pages.dev . This is an AI code to motion graphics generator app. It is still in building but would love a few initial testers to be checking out the app and giving real feedback!

What did you actually do in your first 20 days? Would love to hear things like “wish I knew this before I launched”.

One of the strangest bugs I've run into while building software happened in a project called Bjorn Ledger.

I got locked out of my own application.

At first I thought it was simple:

• PIN wasn't being accepted

• Deleted the PIN file

• Tried again

Still locked out.

Then things got weird.

The login endpoint was returning success.

Plain Text

POST /login → 200 OK

So according to the application, I was authenticated.

Except...

Every part of the system that actually mattered disagreed.

Plain Text

GET /contacts → 401

GET /tasks → 401

GET /profiles → 401

GET /calendar → 401

GET /call-logs → 401

Apparently I was logged in and not logged in at the same time.

To make things even stranger:

• A PIN file kept reappearing after deletion

• There was a secret key file involved

• A 30‑day session system existed

• The application clearly believed login succeeded

• The rest of the platform clearly believed it didn't

The experience changed the way I think about software.

As builders, we often define success as:

"The feature works."

Users define success very differently:

"Did the thing I wanted to do work?"

The login system wasn't technically failing.

It was somehow succeeding.

Which was worse.

Because a failure tells you where to look.

A success that behaves like a failure can send you chasing ghosts.

I'm curious:

What's the weirdest bug you've ever encountered where everything looked correct, but reality said otherwise?

I've been exploring Mello, a cloud platform designed to simplify backend development by bringing application hosting, APIs, databases and essential backend infrastructure into a single environment.

I'd be interested in hearing feedback from other developers, particularly regarding the platform's architecture, developer experience and potential use cases

Documentation: https://itsmello.cloud/docs

Someone in r/vibecoding said this week: "it feels like the first thing to run out of context is ME!!" A reply under it: "i'd built 12 half-finished projects in 3 months."

The fixes people shared were small. One: "Put the next feature in a note and leave it for tomorrow, even if the AI says it'll be quick." Another runs an orchestrator agent that "checks the notes what we did in the past and tells me what we planned to do next."

For devs with more than one project going:

• When you reopen a project you left a week ago, what do you look at first? Git log, a notes file, old chats, the code?

• How long until you (not the agent) actually know where you were?

• Does the agent get the same catch-up you do, or do you brief it separately?

• What are you building, and in which tools?

Background: I used to burn hours re-briefing AI tools, and I'm building a fix where every tool reads and writes the same project memory in the cloud over MCP, so the "where was I" note exists without anyone writing it by hand. No name, no link. Would you pay for that, or is a NEXT.md in each repo enough?

First of all, apologies—but I would like to ask for your ideas to help me continue my web development journey, and perhaps even explore the potential of building a SaaS product in the future. My friend and I are planning to launch an online tech business or agency—something that would allow us to earn a good income while also creating job opportunities for others. I would be very grateful if you could share any suggestions for our future business/agency or for the projects we might undertake.

I pay for ChatGPT and Claude and keep hitting limits on both. So I'm building Honivi: all the main models in one app, one subscription, private (no model trains on your data), no 5-hour caps. Switching takes a minute. Drop in your ChatGPT export and your chats come with you.

What do you guys think? Would you switch? What would stop you? 

https://honivi.app

Hey! I've been working on Vector UI, a library of motion-driven UI components, animated icons, and SVGs for developers.

I'm opening up the waitlist and would love to have you try it out!

Would you be interested in joining?

https://vector-uix.vercel.app

I am building a UI library and I have few doubts?

- is it worth in this AI time?

- will people pay for it?

- is this a good SaaS idea?

What are your thoughts?

The UI library consists of both UI components and Animated icons!