dailyfocus

Most productivity tools solve only one problem: task lists, or Pomodoro timers, or journals. DailyFocus starts from a different premise — a productive day has a natural structure with a beginning, middle and end, and the tool should reflect that.

The project was built as part of my portfolio ecosystem under the moretes.com domain. It is a real, deployed, actively used application — not a throwaway exercise. That means the stack choices reflect what I would genuinely pick for a professional project of similar scope: Next.js for routing and SSR without unnecessary overhead, TypeScript for type safety across the entire codebase, Tailwind CSS for a functional UI without heavy component abstractions, and Vercel for frictionless continuous deployment.

The scope is deliberately contained. There is no custom backend, complex authentication, or relational database in this version. The focus is on the usage experience — a distraction-free interface that guides the user through the daily cycle without imposing unnecessary ceremony. This also makes the repository a useful reference for a production-oriented Next.js project structure.

Next.js as the foundation is not the obvious choice for a client-side productivity app, but it makes sense here for a few practical reasons: the file-based routing keeps page structure explicit, TypeScript support is first-class, and the Vercel ecosystem eliminates all CI/CD configuration. If the project evolves to include server-side persistence or authentication, the foundation is already in place.

Tailwind CSS was chosen over component libraries like MUI or Chakra because the app has specific UI requirements — distraction-free means granular control over spacing, typography and color without overriding third-party defaults. With Tailwind, what is in the code is exactly what is on the screen.

Strict TypeScript throughout the codebase. On a solo project this can feel like overhead, but it is what ensures that future refactors — especially when the project sits idle for weeks — do not introduce silent regressions.

pnpm as the package manager for installation performance and disk-efficient node_modules, particularly relevant in CI environments where every build second matters.

The project follows a modular, production-oriented structure. Although the README does not detail the directory tree, the Next.js + TypeScript pattern implies a clear separation between pages, components, hooks and utilities — enough for any engineer familiar with the ecosystem to navigate without friction.