Mingüini: Building an All-in-One Productivity Platform

The everyday version of the problem is the one the product itself answers: most people manage their day across five different apps — a task manager, a Pomodoro timer, a habit tracker, a project manager, a time tracker — each with its own subscription, its own data model, and no shared context between them.

The harder version is the one we had to solve to build it. "All-in-one" is exactly where most productivity products collapse, into either a bloated everything-app or a shallow one that does nothing well. Thirteen feature areas — tasks, habits, pomodoro, projects, notes, time tracking, study, readings, workouts, money, reminders, billing, and articles — sharing one auth boundary, one database, and one UI language is a surface area that turns into a mess unless every module is built the same way from day one.

We settled on one data model, one auth boundary, one design system, and exactly one way to read or write data. Every module, from Tasks to Finance, is a thin vertical slice over the same primitives, so adding a new one is the same shape of work as the last one, not a bespoke integration.

The other decision was to let the product grow in public without growing complicated. Modules ship behind a global feature-flag layer admins can toggle instantly, and every user can hide the modules they personally don't use — so the sidebar of an all-in-one app is only ever as big as the stack that one person actually wants.

Next.js 16 on the App Router with React Server Components and React 19. Server Actions are the only data-access path — 21 action modules, about 10,200 lines, each following the same contract: session check, Zod validation, a Prisma write, a cache revalidation, and a typed success/error result. There's no REST layer for app data at all, which is exactly what keeps thirteen modules from drifting apart.

PostgreSQL through Prisma 7 on the native pg driver adapter: an 808-line schema, 36 models and 14 enums, 43 ordered migrations, and a hard no-drift policy — every schema change is a real migration, never a push. Composite indexes carry the heavier UI, like the five-day drag-and-drop task board with optimistic reordering. Auth is email/password plus Google OAuth, issuing HTTP-only session cookies validated on every route and every action.

Feature gating runs on two layers. A global flag lets us switch a module off for everyone instantly if something breaks, and a per-user preference lets each person hide the modules they don't personally use — so the sidebar of an all-in-one app never has to feel like one. Plan gating sits on top of that, with payment-provider webhooks keeping subscription status in sync for the paid tier.

The parts that run with no one watching: a cron job checks every user's reminders once a minute, resolves each one against that user's own timezone, and delivers it as a real push notification through a service worker rather than an in-app toast. Mingüini installs as a PWA with an offline fallback instead of shipping a native app, and a calendar integration pulls the day's meetings straight onto the dashboard. The whole interface runs on one perceptually-uniform color system that adapts to light, dark, and a handful of user-picked palettes, served in English and Spanish from the same codebase.

Thirteen feature modules live behind one sidebar today:

Mingüini has been in continuous development for about six months, built and tested the way we'd build any production product: