Project Overview

I read and listen to a lot. Books, audiobooks, podcasts. And I kept losing the parts that actually mattered. The quote that stuck, the idea I wanted to think about later. Notes ended up everywhere — voice memos, random apps, nothing I could find again when I needed it.

So I built Noema for myself. An offline-first mobile app for capturing and organizing insights. Capture something fast, come back to it later. I chose local-only storage instead of auth and cloud sync — I wanted to validate that I'd actually use it before building backend infrastructure.

An offline-first mobile app for capturing and organizing insights from books, audiobooks, and podcasts.

Industry

Personal Productivity

Services

UX/UI Design
Web Development
Product Strategy

Key Deliverables

Responsive Design
Custom Development
User Experience Improvements

Platform Type

Mobile Application

Tech Stack

TypeScript
React Native
Expo

The Challenge

Every note app I tried wanted me to build a system before I could save a thought. Categories, links, templates, onboarding. I just wanted to write down what I heard on a podcast and find it again next month.

The real challenge wasn't coding features. It was saying no to features, and keeping everything on-device without making sync feel like a missing piece.

Approach

I designed the whole thing around my own habits — phone for capturing in the moment, on the couch, on a commute, after a good chapter. Everything lives locally. No account, no server, no waiting for a sync.

I kept the scope tight on purpose. If something didn't help me capture, organize lightly, or revisit old notes, it didn't go in. I planned JSON and CSV export/import so my data stays portable when I'm ready to add a backend.

The Solution

You can save a highlight from a book, a thought from a podcast, or a quick note without thinking about where it belongs. Tags and sources are there if you want them, but nothing forces you to set up a system first.

Everything works offline. Your notes are on your phone, not on someone else's server. The revisit part matters as much as capture — old notes come back in a daily review. Swipe through cards, not dig through folders.

Key Challenges

capture had to be fast enough that I'd use it every single day, not just when I was feeling organized
turning messy notes into something I could actually search later, without making me categorize everything upfront
keeping everything offline-first without the app feeling incomplete compared to cloud-based alternatives
resisting the urge to add features that would turn this into another bloated note app

The Outcome

I use it daily. That's the whole proof for me. If I stop opening it, the project failed.

It's for people who consume a lot and hate when a good idea disappears by next week. Export/import is planned so the data stays mine either way.

Context

I built Noema because I had the problem. I'm still the main user. Local-only was a deliberate choice — prove the habit first, infrastructure second.

The hardest part wasn't TypeScript. It was keeping it small enough that I'd still want to use it six months later.

Noema