CHRONOW

• 

  CHRONOW

• 

  Presentation

• 

  Cluster View

• 

  Memory View

• 

  Home Page

• 

  Collaborating on New Memories

• 

  Recreating the Interactions on Figma Make

Inspiration

We noticed something quiet happening to the people around us. Modern life is designed to pull attention forward. Algorithms, deadlines, and other people’s highlight reels leave little room for reflection. There is almost no space in the current digital ecosystem for the question of who you were and how that person became you. Chronoception, the subjective sense of time and how we locate ourselves within it, was being quietly eroded. CHRONOW began as a question. What would it feel like to get that thread back?

What it does

CHRONOW is a living memory canvas that helps you leave small traces of your life as you move through it and see how they connect. You capture moments through photos, notes, objects, and feelings, and it clusters them into a landscape of memory that reveals patterns and relationships across time. It is not a flat feed and not a timeline. It is a way of sensing your own continuity. You can zoom in, zoom out, drag, organize, and see how moments belong together. Because memory is richer when it is shared, CHRONOW also lets your found family into that canvas. The people who lived those moments alongside you can help hold the story with you.

How we built it

We started with research on narrative identity, chronoception, and the psychology of temporal coherence. We grounded the concept in a survey of 40 respondents, which revealed the core latent need. From there, we developed the interaction model around three capabilities. The first was capturing temporal connections. The second was surfacing memory clusters beyond a linear timeline. The third was enabling shared memory with consent. We built the interface to feel warm and spatial rather than archival, closer to a canvas than a database.

Challenges we ran into

The hardest design problem was about the safeguards. Our survey told us directly that people fear having traumatic moments resurface, being confronted with harm they caused others, or receiving memories that distort rather than restore. Every interaction pattern had to be designed against those fears. We also wrestled with the tension between automatic clustering and personal agency. The system should surface connections, but it should never impose them. We also had to resist the pull toward making CHRONOW feel like another social platform. It is not for performance. It is for perception.

Accomplishments that we're proud of

We are proud that the product is grounded in real human responses rather than assumptions. Our safeguards were designed directly from concerns raised in the survey, not added afterward. They became a core design constraint. We are proud of the narrative frame as well. Janus Duda’s story gave us a way to make an abstract psychological problem feel immediate and human. We are also proud of the concept of chronoception itself. Naming the thing that was missing turned out to be one of the most important design moves we made.

What we learned

We learned that a latent need can be a stronger design argument than an obvious one. There is something powerful about 88 percent of people wanting something they could not previously name. We also learned that safeguards are not only just a liability section, but also the proof of design maturity. Most of all, we learned that the most honest thing a product can do is not solve a problem for people, but make visible something they already felt and could not quite reach.

What's next for CHRONOW

We could build deeper memory clustering using semantic and emotional signals, not just time. We also want to explore a shared canvas feature that lets found families contribute to each other’s timelines with full consent controls.

Built With

• figma