Context

Plot began while planning our honeymoon to Japan. As the trip approached, we were saving places across multiple tools — maps, notes, screenshots, and shared links — without a clear way to organise them or see how they connected.

Many existing travel apps favoured rigid itineraries or focused heavily on package bookings. I wanted something more flexible: a tool that could capture ideas early, adapt while travelling, and remain useful afterwards.

Plot started as an exploration into what a calmer, more personal approach to travel planning could look like.

Adventures in vibe land

I began by designing and building an MVP in code, focusing on the core problem: helping people collect places and structure trips without unnecessary friction.

I used Cursor as a collaborative coding partner — supporting rapid prototyping, exploring technical approaches, and helping reduce the time between idea and working feature.

The early version used Supabase for persistence and the Google Places API to power search and location data, enabling me to validate the fundamentals of the experience quickly.

We took the MVP with us to Japan, using it to save locations and plan our days. Experiencing the product in a real travel context quickly proved its usefulness, while also revealing opportunities to simplify interactions and better support the natural pace of a trip.

Designing for real use

Using the product throughout the trip validated its usefulness and gave me the confidence to evolve it into a production-ready product. Returning home with a clearer understanding of how it performed in real conditions, I identified several opportunities to simplify interactions and better support the natural flow of a trip.

One of the most important decisions centred on data ownership and privacy. Rather than storing sensitive travel data externally, I chose to adopt CloudKit, allowing users’ information to remain securely within their Apple account.

At the same time, I transitioned from Google Places to Apple Maps. While Google offered richer location data and supported rapid prototyping, its pricing model introduced constraints that would challenge long-term sustainability as the product scaled.

Following the trip, I committed to taking Plot beyond prototype — refining the design, strengthening the experience, and preparing the product for public launch.

From prototype to product

What began as a prototype quickly proved its value through real-world use, providing the confidence to evolve Plot into a production-ready product.

Shipping the app reinforced the importance of momentum — prioritising progress over perfection and recognising that meaningful insight often emerges through release rather than prolonged refinement. It also highlighted how advances in tooling are reshaping product design, making it increasingly possible to take ideas from concept to launch with meaningful speed.

Plot is available on the App Store for those interested in exploring the product firsthand.