What is the hardest part of building healthcare apps? (Introducing MedBase)

Hey Product Hunt! 👋 I'm Josue (Isaac), the maker behind MedBase.

Building a healthcare SaaS from scratch is usually a nightmare. Between coding complex patient CRUDs, handling overlapping appointments, and structuring clinical records, developers waste hundreds of hours before even touching their core business logic.

To solve this, I’m launching MedBase soon—an enterprise-grade React 19 & Supabase boilerplate specifically engineered for the medical niche, designed to save you months of UI/UX and backend setup.

Before our official launch day, I wanted to open this thread to gather your early feedback and spark a conversation about the engineering behind it. MedBase is built on a Feature-Driven Architecture (FDA) and skips heavy external libraries in favor of a custom Drag & Drop Calendar (@dnd-kit/core + CSS Grid) and strict type-safe forms (React Hook Form + Zod).

I'd love to hear your "Questions or insights about MedBase that would be relevant to other users or the MedBase team":

• For those who have built clinic or booking systems, what was your biggest technical bottleneck?

• When dealing with complex scheduling, do you prefer building raw CSS Grid calendars or relying on heavy third-party libraries?

• Are there any specific AI features or automation workflows (like n8n) you'd consider an absolute "must-have" for a premium healthcare boilerplate?

Drop your thoughts below! I’ll be hanging out here to answer any questions about the architecture, the tech stack, or our upcoming launch.