Worlds Apart: People, Time Zones, & Travel

• The description states that Worlds Apart is a people-first iOS time-zone app.
• It allows users to:
  • See someone’s local time, date, weather, and part of the day.
  • Get guidance on good, maybe, or quiet hours (set by the user).
  • Scrub through time to find better moments to connect.
  • Adjust time directly from interactive widgets.
  • Use offline Fly Mode to follow an itinerary through departures, layovers, and arrivals while keeping everyone’s local time visible.
• It stores all data privately on-device, with no account required.

Inference The app appears to be a personalized time-zone management tool, focused on helping users stay connected across time zones. It is not described as a marketplace or platform, but rather a utility for individuals.

• The author positions Worlds Apart as an app that "closes distance" by helping people know when to connect.
• It is framed as a world clock that goes beyond timekeeping — it aims to help users understand others' routines and availability.
• The app is described as:
  • A personal tool for travelers or people in different time zones.
  • An interactive experience, with widgets and time-scrubbing features.
  • A privacy-first solution, storing data locally without requiring an account.

Inference The positioning has evolved from a basic world clock to a private connection layer. The author envisions future features like trusted circles, real availability, and shared moments — suggesting a shift toward a more social or collaborative product.

• The description states that the app is for people who are:
  • Traveling.
  • Living in different time zones.
  • Staying connected across countries.

Inference The target customer seems to be individuals, not enterprises. The app is described as a personal utility, and there is no mention of B2B use cases or team-based features.

• No specific ICP is defined beyond "people" and "travelers."

Not evidenced No segmentation, persona details, or user research are provided.

• The description states that the app stores everything privately on-device, with no account required.
• There is no mention of:
  • Pricing.
  • Freemium tiers.
  • Monetization strategy.
  • Paid features.
  • Subscription model.

Inference The business model is unclear. It may be a freemium or free-to-use app, but there is no evidence to confirm this.

• The app is built as a native iOS app using:
  • Swift
  • SwiftUI
  • WidgetKit
  • WeatherKit
  • Core Location
  • App Intents
  • App Groups
• AI tools used include:
  • Codex (for code generation and feature logic)
  • GPT-5.6 (for UI design, QA review, and release prep)
• The author mentions:
  • Automated unit tests and UI tests.
  • TestFlight and App Store submission.
  • Use of Figma for design.

Inference The app is technically sound, with a focus on native iOS experience, offline functionality, and AI-assisted development. It appears to be a solo-built product, which suggests the author has strong technical skills or significant AI support.

• The project was submitted to the OpenAI 2026 hackathon.
• The author built it during Build Week.
• It includes:
  • A complete travel-aware Fly Mode.
  • Interactive widgets.
  • Deterministic QA, unit tests, and UI tests.
  • App Store submission process completed.

• The description does not mention any competitors.
• No comparison to existing time-zone apps or travel tools is made.

Inference The competitive landscape is unknown. It is unclear whether the app addresses a gap in the market or competes with existing solutions like World Clock, Timezone Converter, or travel apps with built-in time zone features.

• The app is a solo project, which raises questions about:
  • Long-term maintenance.
  • Scalability of development.
  • Risk of abandonment.
• No evidence of:
  • User feedback.
  • Market testing.
  • Revenue or monetization.
  • Team expansion plans.

Inference The lack of traction, revenue, and team size raises concerns about the app’s viability as a commercial product. The author's solo development may limit long-term sustainability.

1. What is the current user base or feedback from early adopters?
2. Are there any plans to monetize the app, and if so, how?
3. How does the app handle edge cases in time zone logic (e.g., daylight saving transitions)?
4. Is there a plan for team expansion or external development support?
5. What are the key assumptions behind the vision of evolving into a shared connection network?