Go Transit Watch app icon

Go Transit Watch Independent product · 2025–2026

Making GO Transit feel as calm as checking a flight.

I wanted to know when to leave. Somehow, I was learning line codes. So I designed and built a calmer way to plan a GO trip and keep an eye on it.

App StoreiOS / iPadOSUX + SwiftUI
Download on the App Store

Visit the app website

My contribution

I designed and built the app.

I was the solo UX designer and native developer. I owned the information architecture, interactions, visual system, onboarding, Pro paywall, and SwiftUI implementation.

Testing on my commute and real devices.

I iterated through my own commute, real-device testing, TestFlight feedback, and diagnostics. Every interaction also had to work with Metrolinx’s data, native sheets, and background updates.

Role
UX Engineer
Team
Solo builder

How I worked

How I worked on my own.

I designed and built Go Transit Watch myself, so I could test each design decision in the working app and refine it through TestFlight.

I chose the references, framed the problems, and made the navigation and scope decisions. Cursor helped me implement changes faster, while I reviewed them and decided what was ready to ship.

The commute set priorities

Using GO myself brought platform information, delays, and train status to the top of my list. That gave me a starting point; I still need formal rider research to check those priorities.

References gave me a default

Flighty was my primary interaction reference. Mobbin helped with specific gaps: Calm-style reminders, Hatch-style time picking, and Too Good To Go-style pickup windows informed departure windows and weekday chips.

Context stayed with the work

Figma tracked the seven-step onboarding flow and marketing frames. Living product notes kept tabs, Pro gates, decisions, design tokens, and known gaps consistent across sessions.

Where AI helped

Using Cursor to implement and test changes.

I used Cursor for context-loaded SwiftUI implementation, parallel exploration, and search → patch → test loops. That helped me move from a chained-field idea to Add Route animations, resolve bus aliases, and trace theme and launch bugs.

I remained responsible for the problem framing, information architecture, visual design, and final review. I removed Ask GO, kept bus Live Activities out of scope, and moved Settings off the tab bar. I checked changes through TestFlight, diagnostics, and tests before keeping them.

V1 → V2

Moving from a tab-based app
to a persistent map.

V1 had working data, tracking, widgets, and StoreKit in a dark tab-based interface. The map sat in a separate tab, and planning and tracking competed for attention. I wanted riders to keep the route in view while working on their trip.

I migrated to a map-first shell behind a feature flag, reused the working trip engine, and kept V1 available in debug Settings for side-by-side regression checks.

01

Keep the map. Move the work into a sheet.

I replaced the custom container with native sheet detents and adaptive light/dark chrome. The existing dark V1 detail remained intact.

02

Revising the tabs

Tracking merged into My Trains. Trips gave way to Routes and Union; Settings moved to the Search gear. I tried these changes in stages.

03

Reverting the bus switcher

I reverted the bus-heavy Routes header. Routes stays a rail corridor board; Add Route handles bus numbers and stops. Bus journey UI shipped, while Live Activities remain train-only.

04

Reducing the scope

Bento, Solari, and metro-schematic departure concepts stayed prototypes. I removed Ask GO, ads, and the standalone Planner, while keeping deterministic Siri/Shortcuts.

V2 became the default, and I kept V1 behind a debug flag for comparison and regression checks. I reverted changes when needed. I did not run a production A/B test or measure conversion results.

01 / Planning and following a trip

Catching a train should
be the easy part.

“Brampton to Union. When’s the next one? Which platform? Will I still know what’s happening when I leave the app?”

My commute gave me the starting point: planning felt harder than it needed to. Wrong defaults and opaque line filters got in the way. At first, a better timetable seemed like the answer.

Then I realized the timetable was only half the job. Once I had picked a train, I still wanted to know what was happening without babysitting the app. I focused on recognizable places, readable status, and updates outside the app. I based the intended audience on my commute and research, and still need to validate it with riders.

How might we help riders plan and follow a trip using places and routes they recognize, in an interface that remains useful in the background?

What informed the design

My commute and dogfooding, competitor and interaction-pattern research, real-device testing, and documented product gaps.

What success would mean

Plan a trip in roughly 30 seconds, save it to My Trains, and optionally start a Live Activity. This is a design target, not a measured result.

What v1 would not do

Replace GO ticketing, add accounts, or promise address-to-address planning. Ticket purchases link out; walking legs were deferred.

02 / Research & inspiration

What I learned from other GO apps.

I tried three GO apps while planning trips, looking at how easily I could change routes, find a platform, and keep track of a train after leaving the app.

GO Train Track

The timetable was easy to scan, but the version I reviewed did not show platforms. I wanted riders to see where to board alongside when to leave.

GoTrack

Changing stations or train lines took extra steps. I wanted those choices within immediate reach, while keeping platform and disruption information prominent.

GO Rider Train Schedules

The interface felt like an Android design system brought to iOS. I wanted larger, clearer priorities and familiar iOS controls so riders could find the next departure quickly.

The journey stopped at the app.

In the versions I reviewed, none of the three offered notifications, Live Activities, widgets, or CarPlay. Riders had to reopen the app to check their train. That also left a gap for people driving to a station who needed updates before catching it.

This helped shape my focus on notifications, widgets, and Live Activities. CarPlay was another opportunity for the drive to the station.

Learning from Flighty

Adapting Flighty’s approach to GO trips.

Flighty’s experience inspired three principles: treat a trip as a tracked object, make status glanceable, and continue the experience on the lock screen. I adapted those patterns and their language to commuter rail and bus travel.

Map + planning sheetSaved trip + current statusLock-screen continuity

03 / Design decisions

Keeping the map visible during planning.

01

Keep the route in view

I kept the map visible and placed trip work inside a native sheet. Riders can orient themselves without abandoning their plan.

02

Search in the rider’s language

I designed entry through a route number, a station pair, or a single stop. Chained fields shrink into chips so attention stays on the active field.

03

Keep the basics useful

I kept schedules, maps, alerts, and favorites in the free experience. Pro focuses on widgets, platforms, reminders, and tracking.

04

Explain unavailable data

I used honest unavailable-data states and mode-specific language: Gate for buses, Platform for trains. Live Activity tracking remains train-only.

04 / The experience

Planning a trip and following its progress.

01. Orient, then plan.

I built light and dark map surfaces around the same hierarchy. A sheet lets the rider move between geography and departures while keeping the route in view.

02. Find a route without learning the data model.

I brought train lines, bus routes, and stops into one search direction. Mode-aware badges and gate/platform language help the selected journey make sense.

03. Decide, then save.

I grouped timing, platform information, ticket links, and alerts in trip detail. Saving a train gives it a home in My Trains, separate from the browsing experience.

04. Keep the journey present.

I designed boarding and arrival phases to change with the journey. Widgets and Live Activities make the next important detail visible without reopening the app.

05. Remind riders to tap off at their destination.

I designed a destination notification to remind riders to tap off their PRESTO card and show the weather as they get ready to step outside. The reminder keeps that last task visible when the rider arrives.

I changed the welcome reminder from a fixed “three minutes before arrival” trigger to a proximity-based trigger within 1.5 km of the destination, or confirmed at the platform. Scheduled arrival is the fallback when live train coordinates are unavailable.

A delayed train should not welcome someone to a station they have not reached. I covered the arrival logic with unit tests and added a live server arrival milestone to handle stale scheduled notifications.

06. Your next train, on your home screen.

I designed home-screen widgets so riders can check their next departures without opening the app. Time, platform, and live status form a compact hierarchy across widget sizes. When no departures are available, the widget says so clearly instead of showing an empty or misleading board.

05 / Test & iterate

Bugs I found through testing.

I used API-fixture unit tests, shell UI tests, TestFlight, real-device checks, and diagnostics correlated with server logs. These checks covered the implementation and beta experience. I did not conduct formal user research for v1.

A bus search returned trains

A bus terminal code was being resolved through a rail alias.

I made the catalog’s stop kind authoritative so a bus request stays a bus request.

An express train showed the wrong next stop

The Live Activity used the full line geometry, including skipped stops.

I built the journey spine from served stops only and added a unit test.

Favorite alerts became a notification storm

Each newly received alert generated a separate push.

I batched updates into one summary to reduce repeated notifications.

Light-mode onboarding disappeared

The paged presentation did not respect the intended appearance.

I used a UIKit appearance override so onboarding text remained visible in Light Mode.

The app stalled on cold launch

MapKit and tab tasks competed at startup; an internal report described a 3+ minute hang.

I gated launch, deferred tab mounting, and delayed catalog refresh.

Still open: better picker defaults for line-unaware riders, and a formal accessibility review beyond spot VoiceOver checks.

06 / Brand & delight

App icons for Ontario’s seasons.

I wanted the home-screen icon to change with Ontario’s seasons. The rider also needed to choose when it changed so the app stayed recognizable on their home screen.

I designed and implemented four icon variants, a seasonal picker, and consent-first offers. The icon changes only when the rider chooses to switch.

Default Go Transit Watch app icon
DefaultSummer classic · June–September
Fall Go Transit Watch app icon
FallOctober–November
Winter Go Transit Watch app icon
WinterDecember–March
Spring Go Transit Watch app icon
SpringApril–May

Working with iOS’s icon confirmation.

iOS shows a system confirmation saying “You have changed the icon…” after an alternate-icon switch. That wording feels misleading if the app made the decision silently. I kept seasonal changes out of the background.

“Automatic (Seasonal)” is on by default, but it enables an offer, not a silent swap. On launch, a new season triggers a toast: “🍁 It’s fall! Switch to our cozy Fall icon?” Tap to accept; dismiss to keep the current icon. Settings also offers a manual override, month ranges, and a “Current season” badge.

One set, every surface

I used matching AppIconPreview assets in Settings, onboarding’s notification mock, and marketing, so the notification uses the app’s actual icon.

A tiny web easter egg

On gotrainwatch.ca, tapping the nav icon cycles Default, Fall, Winter, and Spring. The choice persists locally and updates the favicon too.

Making routes recognizable

I used a custom CN Tower tab for Union, GO roundels tinted to line colors with abbreviations, and bus capsules using GTFS route colors. UP Express gets its own wordmark chip: so riders can distinguish it from GO.

Seasonal icon build notes

AppIconManager centralizes setAlternateIconName, current-icon synchronization, and the Ontario season calendar. AppIconManagerTests cover that calendar, including a one-time 2026 rule keeping September on Default before Fall starts in October.

07 / Outcomes and next steps

The app is live on the App Store.
Rider research comes next.

I designed and implemented a native product covering trains, buses, UP Express, Union departures, onboarding, and Pro follow-through. The app is live on the App Store.

I also shipped seasonal app icons with opt-in offers, a manual Settings override, a web favicon easter egg, and a tested season calendar.

I shipped V2 as the default while preserving V1 for regression checks. The dated changelog records ongoing tab experiments, bus scope changes, alert fixes, and tracking corrections. Figma, Mobbin, Cursor, TestFlight, and diagnostics each served a different part of that loop.

The iterations corrected known mode-resolution, notification, and tracking defects. Without an in-app analytics dashboard or a formal study, I cannot claim measured gains in planning speed or rider confidence.

Cursor helped me implement changes faster while keeping the product context available. That left more time for information architecture and the decisions riders need to make. I used Mobbin to study how other apps handled specific interactions, then tested which patterns fit this app.

Reusing the trip engine let me change the V2 interface without rebuilding the core. Feature flags and the option to revert helped me manage the redesign.

Alternate icons taught me that platform copy is part of the design. Apple’s confirmation string cannot be customized, so I designed the seasonal toast around it.

Observe the commute

Next, I would interview 5–8 riders at Union and Brampton GO during peak travel.

Measure the planning task

Test Add Route against the official GO flow using time to a first correct itinerary.

Audit the experience

Run a structured Dynamic Type and VoiceOver pass on Routes, trip detail, and the alerts sheet.