Skip to content
← All entries

What we learned launching KokoroLinks

Notes from shipping a wedding invite product with a small team.

KokoroLinks started as a simple problem: couples needed a clean way to share details without building a full website. The first prototype was a single page with RSVP.

Clear surfaces matter

When a product is meant for a once‑in‑a‑lifetime event, the interface can’t be noisy. We focused on hierarchy, spacing, and fast page loads.

Mobile is the default

Most guests open the invite from a phone. We designed for thumb reach and made sure the schedule and RSVP were readable without zooming.

Trust beats novelty

We added just enough customization to feel personal without overwhelming the couple. The product works because it’s simple and dependable.

← Previous entry Operating principles for a small product studio Next entry → Why static-first matters for product studios