The Problem

We used to have shoeboxes of unorganized photos. Now we have the same photos — scattered across phones, SD cards, old laptops, and the cloud.

Although the format has changed; the disorganization seems to have remained the same.

Underneath, there's a bigger problem: we collect more of life than we pause to absorb. Saying 'I love you' shouldn't be hard or buried under busy lives.

The purpose of 'everyday love' is to solve both of these issues in one app.

What I Learned from Research

The research revealed that people were really moved emotionally and connected with the idea of being able to have a tangible way to remember their moments and reminisce about them.

What I Designed and Why

I designed the app mobile-first, since most existing products in this space are built for desktop—even though the photos people want to use already live on their phones.

That decision set up the two that mattered most, and both are easier to show than to describe — they're annotated on the flow below.

What I'd Do Differently

I'd spend more time understanding the technical architecture behind the app—especially around native photo pickers and building layouts that accurately translate to the final printed/PDF output.

The Problem

Transparency online has been drowned out — but the hunger for it hasn't gone anywhere. Review platforms like Google and Yelp are flooded with paid fake-review farms, AI-generated content, commercialized or sponsored content disguised as reviews, and review-management services that let businesses curate or suppress their public profiles. At the same time, small businesses juggle 5-7 separate tools just to stay visible.

Currently in closed beta — some details held back until public launch.

Market Context

Two things surprised me.

SMB software market worth $100B+ annually (industry reports)

Google removes 170M+ fake reviews per year (Google Transparency Report)

What I Designed and Why

1. In-app messaging between businesses and customers. The obvious alternative was email forwarding — send the customer's message to the business's inbox and let them reply. But email fragments the conversation across inboxes, the platform loses visibility, and the business ends up managing yet another channel. Keeping the thread in-app means the business owns the conversation and customers don't have to leave to follow up.

2. Discovery built on the Google Maps API. The most complete and up-to-date business data available. Launching with real coverage mattered more than building a proprietary database from scratch.

3. QR codes for profile sharing. So a business can share their profile in physical spaces — storefront, receipt, flyer — without a customer needing to type a URL.

The Problem

A wedding guest book collects a few hundred hurried signatures and then goes in a closet. The people who were there had something to say, and the format gave them a line and a pen.

What's actually worth keeping is the sound of the voice — your best friend saying the thing, not a summary of it written at speed while a line forms behind them.

What I Designed and Why

1. A curator, not a moderator. The couple names someone they trust — a maid of honour, a sister — who receives every contribution and arranges the book on their behalf. The couple stays blind to the contents until it arrives. The invitation is sent from the couple's own inbox rather than a noreply, because it's a personal ask, not a system notification.

2. Progress is hidden by default. The couple can turn on a view of who has responded, but never what they shared. Anticipation is the product; showing them the contents early would spend it.

3. Memories per guest is a setting, not a constant. Couples choose one to four. The reason is physical: a book needs at least 24 pages to print, so a small guest list needs more memories per person to reach it. The app recommends a number based on the list size rather than making the couple work it out.

4. Priced by book, not by guest. The page cap comes from the size purchased, not the number of people invited — with an upgrade offered if the list outgrows it. The physical object is what costs money, so that's what's priced.

The Live Wall

A second QR code, scheduled to open only on the wedding day, lets guests add a photo to a slideshow running at the reception. It accepts camera captures only — no library uploads — so what goes up is from that night rather than curated from somewhere else.

The gallery is set to delete itself permanently one year later, and the date is stated in the interface rather than buried in terms.