Traditional map products are built around public places, search, and navigation. They are awkward for private spots that matter only to you.
Primary mobile product / Private maps
Pean
The main Pean app: a private map product for saving meaningful places, organizing personal discoveries, and sharing selected spots with people you trust.
A product direction centered on one-tap saving, privacy by default, outdoor use cases, and low-friction capture from iPhone and Apple Watch.
Context
What this project is
Pean is my primary product surface: a private map for people who collect places that matter personally, not publicly.
Approach
How I shaped it
I am shaping the product around capture speed, privacy boundaries, outdoor usage, and a calm cross-device flow between iPhone, Apple Watch, and web.
Decisions
Product and engineering choices
Treat saved places as private personal data first, with sharing as an explicit action.
Design the mobile flow around one-tap capture before asking for organization details.
Keep web, mobile, backend, and native watch constraints visible in the product model.
Delivered
What the case includes
Private place-saving product direction
iPhone and Apple Watch capture flows
Next.js web surfaces and product storytelling
Offline-aware sync architecture direction