Every app is a collection of decisions. Some are obvious in retrospect; others took weeks of iteration to discover. Building Worldly forced me to think deeply about what a travel map app should be—and what it shouldn't.
This post is a behind-the-scenes look at those decisions: why I built what I built, what alternatives I considered, and what I learned along the way.
Why Build Another Travel Map App?
The honest answer: nothing existing matched what I wanted.
I'd tried Visited, been, Polarsteps, and others. Each was good at something but compromised elsewhere. Visited required a subscription and cloud account. been was too simple. Polarsteps wanted constant location access. Google Maps Timeline was surveillance disguised as convenience.
The app I wanted didn't exist:
- Beautiful visualization (3D globe, multiple map styles)
- Granular tracking (down to cities)
- Photo memories attached to trips
- Privacy-first (no account, local data)
- One-time purchase (no subscription)
So I built it.
Designing the Visual Experience
Five Map Styles
Early versions of Worldly had one map style. User feedback (and my own experimentation) revealed that map aesthetics are deeply personal. Some people want minimalist black and white. Others want full topographic detail with ocean texture.
I landed on five styles:
1. Standard - Clean, colorful, familiar
2. Satellite - Real imagery, grounding the abstract
3. Terrain - Topographic with elevation detail
4. Dark - For dark mode enthusiasts
5. Minimalist - Pure, simple, focused
Each style required balancing readability with beauty. The visited countries need to stand out from unvisited ones, but the distinction shouldn't be jarring. I spent significant time on the color treatment—how visited regions appear in each style while maintaining visual harmony.
See all five map styles in Worldly
The 3D Globe
I knew from the start that Worldly needed a globe view. Flat map projections distort reality—Greenland isn't actually the size of Africa. A globe shows the world as it actually is.
But 3D on mobile presented challenges:
Performance: Rendering a detailed 3D globe smoothly required careful optimization.
Interaction: How should rotation feel? The goal: it should feel like actually spinning a physical globe. Getting the spin momentum and zoom sensitivity right took iteration.
Visual clarity: A globe has half the world hidden at any time. Tap-to-focus on a country brings it to center view.
The globe became Worldly's signature interaction. Users open the app just to spin their globe, watching visited countries catch the light as they rotate past.
Photo Memories
Most travel tracking apps treat travel as data: countries visited, dates, statistics. This misses something important. Trips aren't rows in a database—they're memories.
Adding photo memories to Worldly changed how the app felt:
10 photos per trip: Enough to capture a trip's essence without overwhelming. The limit forces curation—pick your best, not every snapshot.
Tied to locations: Photos attach to the country/city level, creating a visual journal organized geographically.
Private by design: Photos store locally, synced only through your personal iCloud. They never touch Flowstate servers.
This feature nearly didn't happen. Photo handling is complex—permissions, storage, performance. But testing revealed that photos transformed Worldly from "travel tracker" to "travel journal." Worth the complexity.
Platform Decisions
iOS-Native
Worldly is built natively for Apple's ecosystem. No cross-platform framework, no web wrapper.
Why native matters:
Performance: Native development gives direct access to Apple's graphics stack. The 3D globe runs smoothly because we're working with the platform, not against it.
Integration: iCloud sync, system dark mode, Dynamic Type accessibility—all first-class features, not afterthoughts.
Polish: Native apps feel different. Scrolling physics, gesture recognition, keyboard handling—a thousand details that users feel even if they can't articulate them.
The tradeoff is reach. Worldly doesn't support Android. I made peace with this by focusing: build the best possible iOS experience rather than a compromised everywhere-experience.
Supported Platforms
Worldly runs on:
- iPhone (iOS 18.5+)
- iPad (iPadOS) - Larger canvas for the globe
- Mac (macOS 15.5+)
- Apple Vision Pro (visionOS 2.5+)
There's something special about your travel map across all your Apple devices.
Privacy Architecture
Why Local-First?
The default in modern apps is cloud-first: store user data on your servers, sync across devices through your infrastructure. It's convenient for developers and enables features like social sharing.
I deliberately rejected this model.
Privacy as architecture: When data never leaves the device, privacy isn't a promise—it's a fact. I cannot access, analyze, or leak data I never receive.
No breach surface: Worldly users aren't exposed if Flowstate gets hacked. There's no central database of travel histories to steal.
No account friction: New users open the app and start immediately. No email, no password, no profile setup, no confirmation link.
Offline-first: Because data is local, everything works without internet. Log trips on the plane, in rural areas, wherever.
iCloud Sync
Users still want backup and cross-device sync. The solution: use their own iCloud.
Apple's CloudKit handles the complexity. User data encrypts with keys only they possess. It syncs through Apple's infrastructure, not mine. I implemented the integration; I never see the data flowing through it.
This creates a clean boundary: Flowstate builds the app, Apple handles cloud infrastructure, users own their data throughout.
Monetization Decisions
One-Time Purchase vs Subscription
Subscriptions are the dominant model in iOS apps. The recurring revenue is attractive for developers and the App Store takes a lower cut after year one.
I chose one-time purchase anyway.
User alignment: Subscriptions create misaligned incentives. The business benefits from keeping you subscribed, which can lead to artificial feature gating, lock-in, and "engagement" mechanics.
Trust: Users are subscription-fatigued. Another $5/month app is friction. A $4.99 one-time purchase is a clear transaction—you pay, you own it.
Simplicity: No subscription management, no billing issues, no "your payment failed" emails. Buy once, use forever.
Sustainability: Worldly doesn't require ongoing server costs. There's no technical reason to charge monthly. The honest monetization matches the technical reality.
Worldly Pro is $4.99 once, forever
Free Tier Design
The free tier had to be genuinely useful, not a crippled demo:
Free forever:
- Track all continents and countries
- Basic globe visualization
- Standard map style
- Limited photo storage
Worldly Pro ($4.99):
- All five map styles
- Unlimited photo storage
- Advanced statistics
- All future premium features
The division is: free users get a complete travel tracking experience. Pro users get customization and depth. Nobody hits a wall that makes the app unusable.
What I'd Do Differently
Hindsight reveals some things I'd change:
Launched too late: I over-polished before launching. Should have shipped earlier with fewer map styles, gathered feedback, iterated publicly.
Underestimated city data: Getting accurate city boundaries for every country was more complex than anticipated. Some regions have cleaner data than others.
More user testing: I relied heavily on my own intuition. Earlier beta testing would have caught interaction issues faster.
But overall, the core decisions—native iOS, local-first privacy, one-time purchase, visual-first design—I'd make the same way again.
Building Forward
Worldly is live and growing. The architecture supports features I'm building toward: trip timelines, richer statistics, export options. Because it's local-first, new features don't require server changes—just app updates.
If you've read this far and you're curious, download Worldly from the App Store. See the decisions in action. Spin the globe. Watch your travel history turn into something you want to look at.
And if you're building your own app, I hope this peek behind the curtain is useful. Every app is a collection of decisions. Make them deliberately.