Case study · Flagship web app
A calm, local-first notebook designed around the real rhythm of conventions and assemblies: listen, capture what matters, and return to the exact context without rebuilding it.
Project snapshot
The starting point
Generic note apps are flexible, but that flexibility creates work during an event. A user may need to create folders, name pages, copy talk titles, and remember where a note belongs while also trying to listen.
Noted began from a more specific question: what would note-taking feel like if the app already understood the program, the day, the session, and the user’s next likely action?
Selected screens
The home dashboard points to the next action, the program provides structure, and the notes view preserves context by day and time.
Project evolution
The most useful progress came from repeatedly reducing setup, preserving context, and making the next action easier to see.
These are product phases rather than exact release dates. The screenshots show the current product; earlier stages are described from the decisions that led to it, not presented as archived interfaces.
Notebook first
The initial direction centered on one personal notebook for conventions and assemblies. Defining the routine first kept the product focused on listening, capturing, and returning rather than becoming an all-purpose notes app.
Structure arrives
Instead of requiring users to create folders and copy talk titles, the schedule became the information architecture. That connected each note to its day, time, and session before writing began.
Context continuity
Scripture lookup, interruptions, and switching sections should not make the user rebuild their place. The product direction shifted toward preserving the exact notebook and session context across navigation.
Responsive + bilingual
Mobile navigation, touch targets, compact layouts, English, and Spanish were refined as product behavior—not added as decorative adaptations after the desktop interface was finished.
Next-action clarity
The dashboard evolved from a collection of tools into a calmer decision surface. Noted Live, the next gathering, and “continue your notes” reduce the number of choices a user must make before returning to the work.
Current beta
The current phase emphasizes accessibility, bilingual consistency, import reliability, offline behavior, backups, and respectful companion workflows. The goal is a dependable personal tool, not the largest possible feature list.
The problem
Creating files, copying titles, and deciding where information belongs can interrupt listening before the note is even written.
A user may leave briefly to look up a scripture or reference. Returning should not mean hunting through a generic document.
A note app can have many useful tools while still making the two or three most common actions difficult to find.
The product should not require unnecessary accounts or pretend to offer official integration with another app when that support does not exist.
How the product evolved
The work did not move in a straight line. Each pass focused on making the product easier to understand during real use.
Mapped the event around programs, days, sessions, notes, and personal follow-up instead of starting from a generic document editor.
Made the program, notebook, and session list behave like parts of one experience rather than separate pages with duplicated setup.
Moved the current event and recommended next action forward while placing less-common tools behind clearer secondary paths.
Adjusted labels, hierarchy, English and Spanish content, and return paths so the interface explains itself with less instruction.
Product decisions
Each decision removes friction before, during, or after the event rather than adding a feature simply because it is possible.
Sessions receive their place before the user begins writing, so the event’s structure does the filing work.
The dashboard prioritizes the current event, the next gathering, and the most useful continuation point.
Notes are saved on the device by default, supporting privacy and making the product usable without a required account.
The direction is to reduce friction around scripture lookup and returning to Noted without promising official JW Library synchronization.
English and Spanish are treated as complete interface experiences rather than decorative translation afterthoughts.
The basics remain prominent while importing, editing, settings, and other tools stay available without dominating the screen.
My contribution
This wording is intentionally specific: the case study focuses on the work I can confidently explain rather than overstating a formal engineering role.
Identified the audience, the event routine, the primary user problems, and the product boundaries.
Organized programs, days, sessions, notes, checklists, and navigation into connected workflows.
Shaped hierarchy, visual tone, responsive layouts, labels, and the calm interaction model.
Reviewed builds, identified friction, rewrote prompts and requirements, tested changes, and continued refining the product.
What I learned
The strongest Noted changes were not the most technically dramatic. They were the changes that made the next action clearer, preserved context, and reduced the amount a user had to organize while listening.
What is still evolving
Current areas of attention include smoother context return, accessibility, bilingual consistency, import reliability, and a respectful companion workflow around scripture lookup.
Explore the current beta ↗What this demonstrates
Noted demonstrates designing from a routine I personally understand, information architecture, responsive interface direction, iterative problem-solving, and the discipline to keep simplifying after a product becomes usable.
Project status
The live version continues changing as I use it, test it, and simplify the workflow.
Open usenoted.app ↗