Place Collection
Add countries, cities, landmarks, and personally meaningful stops into a structured travel archive.

An upcoming Expo app for turning the places you have been into a personal world archive.
Been-To-Box will collect the places a user has traveled, organize them into meaningful stats and highlights, and make personal travel history feel visual, memorable, and easy to revisit across mobile and web.
Travel archive
Primary signal
42 places
Secondary signal
8 countries
Audience
Travelers, digital nomads, families, and memory-keepers who want more than a static map of pins.
Problem
Travel memories often live in scattered photos, notes, and maps. Been-To-Box will package those places into a personal, stats-driven travel archive.
Product signals
Core workflow
The common product-page pattern here is simple: lead with the problem, show the working loop, then make the technical choices visible without turning the page into a spec sheet.
Add countries, cities, landmarks, and personally meaningful stops into a structured travel archive.
Surface totals, regions, continents, repeat visits, travel streaks, and other personal movement patterns.
Group favorite places into curated collections that feel more intentional than a plain checklist.
Use Expo with React Native and web support so the same travel archive can work on phone and browser.
Differentiators
These are the points that make the product easier to remember and explain in a portfolio review.
The product will focus on how travel feels to the user, not just where pins sit on a map.
Counts and charts become more useful when paired with highlights and personally meaningful groupings.
The page is ready for screenshots, map visuals, achievements, and richer trip data when the app exists.
Build notes
OnTrack and Reach are both Expo, React Native, and Supabase products, so the common portfolio method is a mobile-app showcase with a workflow loop, differentiators, and a compact technical layer.
A future Expo Router app can share navigation and product logic across native and web surfaces.
The baseline product model should keep locations, regions, highlights, and stats separate enough to evolve.
This page marks the concept as upcoming while preserving the same product presentation system as the finished apps.