Noue

Énouement

The name is derived from the word Énouement (from The Dictionary of Obscure Sorrows). It represents the bittersweetness of having arrived in the future, seeing how things turned out, but being unable to tell your past self.

I have felt this way many times—longing to reassure my past self about how things turned out, while simultaneously wishing I could capture exactly what I am feeling right now for my future self. People often turn to physical diaries for this, and I did too for a time. However, I soon realized traditional journals weren't the right solution for me. They are fragile, they can be filled up, they lack privacy if they fall into the wrong hands, and they can easily be lost. Furthermore, my most profound thoughts usually strike throughout the day when a physical diary isn't within arm's reach.

At one point, I even used Google Docs to write scheduled emails to my future self. In fact, I have one scheduled to arrive in 2028 that I wrote back in 2023. But managing these scattered files made me realize I needed a unified system.

Beyond journaling, I also wanted a centralized way to track daily metrics like reading, exercising, coding, and applying for jobs, alongside qualitative data like my emotional mood and overall health. My goal was to analyze this data to find meaningful correlations—such as whether more sleep directly yielded a better mood, or if regular exercise noticeably improved my health.

I needed a singular platform to track my feelings, log my activities, write freely, and store that data securely for years to come. The only way to get exactly what I wanted was to build it myself.

The Birth of DayTracker

When I began this journey in 2023, I was proficient in React and core web technologies, but completely new to mobile development. I decided to build a web application, but with an unconventional constraint: I wouldn't use any modern UI frameworks, despite knowing them.

I wanted the raw experience of engineering a sizable application using purely vanilla web technologies. So, I started with plain HTML, CSS, and JavaScript. I didn't fully realize how complex state management and UI rendering would become without a framework, but I dove in anyway.

I sketched out a modular system where users could customize exactly what they wanted to log. To support this, I built the app around four UI primitives:

• Toggle Switch: Used to track binary metrics like exercising, reading, coding, or applying for jobs.
• Emoji Slider: Featuring a customizable five-tier scale to track qualitative metrics like emotional mood or overall health.
• Small Text Field: For quick logging of numeric values or short activity logs.
• Large Text Field: For free-form journaling and storing unstructured thoughts in the moment.

I built an editor view to configure these primitives, a default logging view to interact with them, and a calendar dashboard where clicking any date revealed that day's history. Finally, I added a profile view intended for future analytics.

After a few months of heavy vanilla development—entirely by hand, long before LLMs were advanced enough to write clean code—I delivered a functional MVP. It successfully saved entries to Firebase and featured a clean, responsive UI with robust loading states. It lacked deep analytics, but the core engine worked. I gave it a simple, literal working title: DayTracker.

Life got busy, and I left the app in that state for years. Yet, it became an indispensable part of my life. I have used it daily ever since, even as the interface grew dated and incomplete.

Noue

A few months ago, I decided it was time to bring the experience to mobile. The progressive web app (PWA) wasn't cutting it. As I began planning the migration to React Native, I realized that if I was going to put in the effort to overhaul the underlying architecture, I should completely reimplement the UI to make it modern, beautiful, and ready for a wider audience.

I went back to the drawing board to rethink the entire philosophy of the application. I wanted to pin down the exact feeling I intended to invoke in the user. After mapping out these emotional goals, I ran the concepts through an extended brainstorming session with Gemini. We eventually landed on Énouement—the exact word for that bittersweet desire to communicate across time.

Since Énouement is a bit of a linguistic mouthful, I shortened it to Noue. Finding the name clicked everything into place. I went all-in on that reflective aesthetic, designing an intentional, modern interface centered around personal legacy and emotional clarity.

What’s Next

Noue is currently in active development, and the new design completely embodies the philosophy I always intended for it. I am on track to finish and launch the mobile application soon, and I look forward to updating this case study with the results of Version 2.

The process of building both iterations has been deeply personal. While I am building this version to production-grade standards so that anyone can download it, the truth is that even if I remain the only user, I would still build it. The utility and meaning this system brings to my daily life are immense. I built it for myself in 2023, stuck with a half-finished version for years, and now, creating the definitive version of Noue is a project I am incredibly proud to bring to life.