Platform

The description states that Platform is a native SwiftUI transit companion for iPhone, iPad and Apple Watch, with widgets and Live Activities. It is backed by a production proxy for Transport for NSW Open Data and designed as a network control room for ordinary riders rather than another timetable list.

It includes:

• A live map of over 3,700 vehicles across Sydney’s train, Metro, bus, ferry, and light-rail networks.
• Multimodal journey planning with Leave now/Leave at/Arrive by options.
• GPS-driven journey tracking that uses Core Motion hints and live vehicle evidence.
• Departure boards for all five transport modes, including platform filters and capacity where available.
• Lock Screen and Dynamic Island Live Activities showing actionable information.
• Privacy-bounded trip sharing via expiring codes or universal links.
• Service alerts with Apple Intelligence briefs on supported systems.
• A self-collected carriage-load dataset (not yet enabled in production).
• Features like a first-run introduction, minimisable tracking, VoiceOver support, and large-text hardening.

The app is built using Swift/Xcode, MapKit, Core Location, Core Motion, ActivityKit, WidgetKit, WatchConnectivity, and Node/Express backend with Redis caching. It uses Codex for AI-assisted development but maintains strict engineering discipline through protected release lanes and human acceptance checks.

Inference The app is designed to be a cross-device experience that integrates real-time data into actionable insights, with emphasis on privacy, accessibility, and accuracy over certainty.

The author describes the inspiration behind Platform as being driven by personal frustration with existing apps that give “fake ‘on time’ claims.” The working name was once “unshitty transport,” which reflects a strong anti-establishment positioning — rejecting the status quo of misleading or incomplete transit information.

Key claims in the description:

• The app stops wasting data by presenting it honestly.
• It preserves uncertainty inside the data and does not fabricate confidence.
• It uses real-time occupancy, GPS-tracked journeys, and live vehicle evidence.
• It avoids “timetable dressed up as certainty.”
• It treats service alerts as untrusted source material and summarizes only facts.

The positioning has evolved from a personal hackathon project into a user-focused tool for everyday commuters, emphasizing transparency, accuracy, and usability over marketing or hype.

Inference The product positions itself as a truthful, data-driven alternative to traditional transit apps, aiming to reduce user anxiety by showing what’s actually happening rather than what might be predicted.

The description states that the app is designed for ordinary riders of Sydney’s public transport network. It targets users who:

• Commute daily on Sydney trains, Metro, buses, ferries, or light-rail.
• Need to know real-time information about vehicle positions, occupancy, and platform details.
• Want accurate journey planning and tracking, especially in situations like tunnels where GPS is lost.

The ICP appears to be:

• Daily commuters in Sydney.
• Tech-savvy users who value precision and honesty in data.
• Apple ecosystem users, particularly iPhone, iPad, and Apple Watch owners.

There is no mention of enterprise customers or B2B use cases. The focus remains on the individual rider experience.

Inference The target customer is a single-user, local commuter, not a broader market or business audience. There is no evidence of segmentation beyond this.

There is no mention of pricing, monetization, or business model in the description. The app is described as being built by one person without funding, and there is no indication that it has any revenue streams or commercial partnerships.

Inference The business model is unknown, and the app appears to be a personal project without any commercial intent at this stage.

The author describes a highly disciplined engineering approach:

• The app is built in Swift/Xcode with SwiftUI, MapKit, Core Location, Core Motion, ActivityKit, WidgetKit, WatchConnectivity.
• Backend is a Node/Express proxy with Redis caching and one dedicated poller to manage TfNSW API quota.
• Uses Codex as part of the engineering system but with strong boundaries — agents are used for implementation, adversarial review, regression tests, etc., but output must be supported by build/test/evidence.
• Release process includes protected internal TestFlight lanes, pull requests, required checks, and physical-device acceptance before external release.
• The app is unit-tested and passes hundreds of Swift tests, static analysis, privacy checks, and simulator smoke tests.

Inference The technical delivery signals suggest a well-engineered, disciplined solo project, with attention to scalability, correctness, and quality control — despite being built by one person.

There is no evidence of traction or adoption beyond the author’s own usage. The app:

• Is in a release candidate stage.
• Has passed internal testing (Xcode Cloud, Swift tests, privacy checks).
• Has not yet been released publicly.
• Has no mention of users, downloads, or feedback.

Inference There is no traction or maturity evidence beyond the developer’s own use and testing. The project is still in development and not yet available to users.

The description does not provide any information about competitors or how Platform compares to existing transit apps. It only states that the author was tired of apps that give fake “on time” claims, but does not name specific competitors or describe their offerings.

Inference The competitive landscape is unknown, and there is no evidence of how Platform differentiates from or competes with existing apps in the market.

Key risks and red flags based on the description:

• No traction or user feedback: The app has not been released to users, so there is no evidence of real-world usage or demand.
• Solo development constraint: Built by one person with no funding, which may limit scalability or long-term maintenance.
• Limited market scope: Focused only on Sydney’s transport network and Apple ecosystem, limiting potential for broader adoption.
• Unclear monetization strategy: No business model or pricing is described.
• AI dependency without clear governance: While Codex is used, the author notes that agent output must be supported by evidence — a potential risk if not properly managed.

Inference The project is highly experimental, built by one person, and lacks any commercial traction or evidence of market demand.

1. What is the actual usage rate of the app among users?
2. How many people are currently using it beyond yourself?
3. Have you considered how to scale beyond Sydney’s transport network?
4. What are your plans for monetization or commercial viability?
5. How do you plan to handle data quality issues that arise in real-world use?
6. Are there any legal or compliance concerns with using TfNSW data under CC BY 4.0?
7. Do you have a long-term roadmap beyond the current features?