LIFELOG

Photos pile up in camera rolls and get buried under thousands of newer ones. Stories shared at dinner tables are never written down. The people who remember them most vividly are growing older.

There's no structured way to pass a memory — a story, a photograph, a voice note — from one generation to the next. Social media is too public, too ephemeral, and too cluttered. Photo albums are static and inaccessible. LifeLog was conceived to fill that gap.

• Photos without context

  A photograph means nothing without the story behind it. Who is in it, what happened that day, why it mattered.

• No generational continuity

  Memories live in the minds of individuals, not in shared family archives accessible to everyone — including those not yet born.

• The format problem

  Existing tools weren't built for memory preservation. They were built for sharing right now, not saving for later.

LifeLog is built around the idea that a memory is more than a photograph. The app is designed to let users add context — who, what, when, where — at the moment of capture, before the details fade.

• Contextual capture —

  Add names, dates, locations, and written notes to every memory as you create it. The context is inseparable from the content.

• Timelines & family albums —

  Memories organise chronologically into personal timelines and shared family collections — browsable by year, person, or event.

• Selective sharing —

  Share specific memories or albums with specific family members. A story intended for your children doesn't have to be visible to everyone.

• Generational hand-off —

  Memories can be set to unlock at a future date, or passed directly to the next generation as part of a family legacy archive.

The biggest design risk with LifeLog was making it feel like a chore. If adding a memory takes too long, people won't do it. If the UI feels clinical, it won't invite the kind of reflection the app is built for.

The design process centred on three principles that kept every decision grounded.

• Mobile-first, always

  LifeLog is used in the moment — at a birthday, on a walk, at the dinner table. It had to work naturally in those contexts, one-handed, with minimal setup.

• Low friction capture

  The flow from opening the app to saving a memory was timed and iterated until it felt effortless. Removing steps was always preferred over adding them.

• Privacy-first sharing

  Sharing a memory should feel as considered as sending a letter, not as casual as posting a story. The sharing model was designed to feel intentional.

The complete LifeLog case study — including research findings, user flows, wireframes, high-fidelity screens, and usability testing results — is documented on Behance.