Start with fragments
Let a memory begin as text, a recording, an image, a document or mixed media.
↳ Documented product behaviorFrom a remembered moment to a life story, with the author in control.
Product design & development
React Native · Expo · AI-assisted writing
Internal Android preview
Original app components · Fictional sample memories


Writing an entire autobiography is an intimidating blank-page task. People remember fragments, and AI-generated prose needs to preserve their meaning and sources.
Capture-to-chapter product model, mobile information architecture, memory organization, writing controls, local archive and optional collaboration flows.
React Native / Expo mobile interface, Encrypted local archive, Memory timeline and life-map entities, Guided recall and writing flows, Consent and collaboration roles, PDF, EPUB and archive export implementation.
Specific choices, connected to the work you can see.
Let a memory begin as text, a recording, an image, a document or mixed media.
↳ Documented product behaviorPreserve original material, corrections, confidence states and revision history alongside writing.
↳ Documented product behaviorUse editing levels, locks, permissions and reviewed editions instead of treating generated prose as unquestionable truth.
↳ Documented product behaviorSupport local-only startup and archive use, with separate cloud collaboration and server-side AI processing.
↳ Documented product behaviorSelect a stage to explore its purpose.
Begin with a moment instead of an empty book.
New portfolio explanation based on the documented implementation and original project material.
Selected views, framed to explain the work. Complete original artifacts are available in the source collection below.

A guided question offers a starting point. Speak, Write and Photo make capture a small action instead of asking someone to begin an entire autobiography.

The archive keeps memories searchable and separates source material from the chapters it may later inform. Differing perspectives have an explicit place.

The book view turns fragments into an evolving structure. Chapter states show where material exists and what is ready for review.

The timeline accepts approximate dates and keeps people and topics attached to the memory. The interface can express uncertainty without hiding the story.

The latest Memory Atlas connects a geographic map with a time lens. Nearby memories cluster together, while sensitive places stay hidden by default. This original screen is rendered from the newer app source with fictional memories and public city-centre coordinates.

The places index gives homes, streets and journeys a place in the archive. Location names, descriptions and connected-memory counts offer another way to rediscover a story.

A place brings its original memories and events together. This read-only view keeps the story’s connections visible without exposing editing controls.

The chapter studio combines editing, revision history, locks and source references. AI-assisted writing stays part of a reviewable authoring process.
The complete originals behind this case study. Open a board to inspect the source presentation.
The README and completion audit document an internal Android preview tested on an emulator and physical device. Production signing and public distribution remain separate work.
Original screen components, theme, fonts and icons are rendered from the project source using React Native Web. Local fixtures supply fictional memories and account data; device services and navigation are adapted for the capture environment. This is a source-rendered presentation, not a device capture or new interface proposal. No personal archive, cloud account or AI request was used. Original source files remain unchanged.
The journey diagrams and editorial explanations were prepared for this portfolio from the available project evidence. They are not additional historical research or measured outcomes.
A racing miniapp I founded, designed and built. Startale Superstars winner on Soneium.