A private daily view, with an optional view of shared content.
Product case study · In development
Morly
A private app for couples to keep memories, conversations and shared history in one place.
I’m developing Morly around a simple rule: the relationship space is private first, and anything social is optional. Couples can save moments, keep notes, start conversations and decide together what, if anything, they want to share.
01 / Problem
Why I started it.
A lot of relationship apps focus on prompts, scores or public couple content. I wanted to explore something quieter: a place for everyday memories, difficult conversations, recurring concerns and the things a couple may want to come back to later.
02 / Architecture
The product is built around five areas.
A shared archive with a timeline, albums, monthly recaps and a yearly review.
A creation flow that starts with the camera, with options for moments, memories, notes, conversations, wishes and posts.
Private conversations and topics that need attention.
The couple’s profile, shared space, privacy options and settings.
03 / Identity model
Two people, one shared space.
Each person has an individual account for access and ownership. The couple profile connects those accounts and represents the relationship only when both people choose to use it that way.
Individual account
Shared couple profile
Private relationship space
Optional sharing
04 / Privacy decisions
Private by default, share only when both choose to.
Designed to stay private
- Talks
- Sensitive notes
- Private memories
- Relationship history
Shareable by choice
- Selected moments
- Approved posts
- Milestones
- Recaps selected for sharing
05 / First-version scope
What the first version needs to do.
Individual accountsShared couple profileOnboarding that explains privacyHome with a switch between Us and CouplesAdd carousel starting with the cameraMoments timelineTalks tabUs dashboardMonthly recap
06 / Language inside products
Building the product changed how I look at interface copy.
Morly has forced me to make decisions about labels, onboarding, privacy wording, recurring terms and emotional tone. Those are the same kinds of questions that appear in localization: what does the user need to understand here, how much space is available, and what wording still works after it becomes part of an interface?
UI labelsOnboarding languagePrivacy wordingTerminology consistencyTone across flows
Why it is on this site
It gives me product context when I localise software.
Working on Morly means I see interface language from the product side as well as the translation side. I have to think about where a string appears, what action follows it and what the user may misunderstand if the wording is vague.
Back to projects