Memorandum
Save meaningful memories, add a note and choose who to share them with.
- My role
- UX designer · UI designer · User flows · UX research
- Tools
- Figma
- Timeline
- June 2026
Context
Memorandum began with the idea of giving important moments a space of their own. Instead of collecting every photo and video, it focuses on the ones that mean something to you.
Capture a moment, write down how it felt and choose whether to keep it private or share it with someone you love. A calendar and a collection of Polaroid-style cards make those memories easy to return to. The aim is to give each moment a little more attention than it gets in a gallery of thousands of pictures.
The problem
A camera roll fills with thousands of images and gets opened for two reasons: to find a screenshot, or to free up storage. Everything is saved, so nothing is chosen. The archive grows and the memory does not. Journaling apps fail in the opposite direction. They ask for effort every day, then punish you for missing one. Break the streak and the app becomes a reminder of what you stopped doing. Both are the same failure. Neither one asks the only question worth asking: what actually mattered today?
The insight
When you can save everything, saving costs nothing, and nothing feels worth saving. When you can save one thing, you have to choose. The choosing is the act of remembering. So I inverted the brief. Instead of asking how to capture more, faster, with less friction, I asked what happens if the app allows exactly one entry a day and then closes. Every decision after that point follows from it: the empty state, the archive, the widget, the way sharing works. One rule only: One picture for every day of the year.
The idea
Memorandum turns one meaningful moment into a daily ritual. Choose a photo, add a short note about how it felt and decide whether to keep it private or share it with someone close to you. A Polaroid-style card gives that moment a place of its own. Today holds the current entry, Shared brings people into a memory and Album lets you return to the days you have kept. The limit of one entry a day is intended to make choosing feel worthwhile, rather than turn saving into another task.
The architecture
The entire app is three tabs. Today is the only place a memory can be created. Shared is where a memory belongs to more than one person. Album is everything you have kept, in order. There is no feed, no profile grid, no discovery tab. Nothing in the structure invites you to scroll, because scrolling is the behaviour the app exists to replace.
Design system
A warm cream surface gives the app a paper-like feel. Purple marks prompts, primary actions and the active tab, so the next step is easy to find. Handwritten display type adds a personal tone to dates and headings. Monospaced labels and metadata provide a quieter, more structured contrast. Polaroid-style cards, soft corners and a thin shadow separate each memory from the background while keeping the overall composition calm.
Flow walkthrough
There is exactly one thing a new user has to understand: you get one memory a day. Every screen here serves that idea. No feature tour, no permissions wall before the value is clear, no account required to see what the app actually does.
Today opens with the date, a prompt and an empty card: What felt worth saving today? The flow asks for one photo and a short note. Once the memory is saved, the create button gives way to the finished card until the next day. The aim is to make remembering a small, deliberate pause.
A shared memory appears in both albums, with each person contributing their own part of the story. The aim is to keep a meaningful moment together, rather than lose it in a group chat.
One entry a day makes a year 365 cards instead of twelve thousand photos. That is a number a person can actually move through. The album is the payoff for the constraint, and it is the only screen in the app designed for browsing.
Close
This is a concept. Its central assumption still needs testing: does saving one memory a day feel like relief or restriction? Three questions would guide the next stage.
1. Does the daily limit help? I would test whether people value choosing one moment or feel frustrated when they want to keep more.
2. Do people return to the album? The archive needs to be worth opening again, not just a place where entries accumulate.
3. Does sharing feel mutual? Both people need to want to contribute. I would look for where a shared ritual starts to feel like an obligation.
What I learned
Designing around a restriction is harder than designing around a feature list. Every screen becomes a place where the rule could quietly break. Most of the work was finding twelve different visual ways to say no.