Bus Widget

Live arrival times for your Singapore bus stops in the Mac menu bar, and a nudge when it’s time to walk. One glance, no phone, no sign-in.

Type
Side project
Platform
macOS 15+ menu bar app
Role
Product design, directed the build
Status
v0.3.1, signed auto-updates

The menu bar above is drawn, with a staged time. Click the bus to open or close the dropdown.

The Bus Widget dropdown: two saved stops, Going to work and Going to Mom's, each with a row per bus showing the service number, the next arrival large and the two after it in grey, plus a one-line legend.

“Put the buses I care about on my Mac’s menu bar, and tell me when to leave.”

Checking a bus app on my phone while working at my Mac meant switching devices and doing the timing in my head. I built Bus Widget for my own commute, and to see how far I could take a native app by directing an AI coding agent. It started as an open question, not a spec, so I opened with four.

  1. What belongs in the menu bar, and what in the dropdown?

    One number in the menu bar: the next arrival of one pinned bus or stop. Everything else lives in the dropdown.

  2. Web-based, or a download?

    A native SwiftUI app. A website can’t put an item in the menu bar, and native gives always-on data and system notifications. Direct download first, App Store later.

  3. Sign-in, or guest mode?

    No account at all. Stops, names, pins and alerts stay on the Mac, so there’s nothing to sign up for and no personal data to hold.

  4. How does it work with Singapore’s bus data?

    Through a small server of my own that holds the LTA DataMall key, caches each stop and rate-limits. The app never calls LTA directly.

One number, however much it shows

Every feature added something to the dropdown, and every time it got harder to read. Each time, I pushed it back toward one thing: when the next bus comes.

“Possible to make it easier to scan? Seems a bit messy with more and more info.”

  1. Your name first

    Custom names like Home or Office sit on top. The official name and stop code sit beneath, smaller and lighter, with the walk time on the right.

  2. The next bus, large

    Every row is the same: a service badge, the next arrival large, and the two after it in grey.

  3. Only exceptions are marked

    An arriving bus turns green. Double-deckers get a small icon, with wheelchair access in its tooltip.

  4. Crowding, only when it matters

    A dot appears for Standing or Limited. Seats are the normal case, so marking them only added noise. The pin puts this bus in the menu bar.

  5. A tilde for scheduled times

    When a time isn’t live tracking, a ~ says so without spending a column on it.

  6. A legend on one line

    I asked whether the legend should collapse. A collapsible legend is one nobody opens, so it fits on one line instead.

“Bus in 12 minutes” becomes “leave now”

Each stop has a walking time. Ring the bell on a bus and the alert is timed to your walk, so it arrives as a notification when it’s time to go. No more doing the sum in your head.

Add Bus Stop window in Map view: Bedok Int on the map, buses 7 and 14 ticked, an optional name field and a walking time of 5 minutes.

Set up once, in the order you think

I rewrote the flow as: official name, then buses, then your own name, then your walk.

  • Find the stopBy number, name or road, on a map, or with Near Me. Location stays on the Mac and is used only when you tap it.
  • Pick only your busesNothing is ticked to start. “Don’t preselect all services” was my first note.
  • Name itHome, Office, Going to work. The name field got its own labelled section after I missed it the first time.
  • Set your walkMinutes to the stop, with a tooltip on why: it’s what times the alert.

I directed. The agent built.

Claude Code wrote the code. I made the product calls, and reviewed every change through screenshots, in about 20 rounds of short notes. The next build changed.

~2 days
From an open question to a signed app with its own server, analytics, privacy policy and automatic updates.About two days, from 5 November 2026. Version 0.3.1 reached my Mac as its first automatic update.
  1. “Possible to make it easier to scan? Seems a bit messy with more and more info”

    Rebuilt the row: badge, next bus large, later buses grey, only exceptions marked.

  2. “After adding a stop, keep the widget open to show the new stop has been added”

    Saving reopens the dropdown and tags the new stop ADDED.

  3. “Too clunky, user should be able to reorder from the dropdown”

    Reordering moved out of Settings and into the dropdown.

  4. “Dragging interaction is broken”

    System drag-and-drop fails in menu bar windows, so drag-to-reorder was built from scratch.

  5. “Make the official name smaller and lighter and placed below the custom name”

    Custom name on top, official name and code beneath.

  6. “Have a meatball menu to house: add bus service, delete bus service, delete bus stop”

    A ••• menu per stop, with a confirmation before deleting.

  7. “The pin icon should be in line with the bus service pins”

    Header buttons now share the bus rows’ column, so every pin lines up.

  8. “Very messy. Remove drag to reorder.”

    The hint went, and the legend fit on one line.

Where the menu bar pushed back

A menu bar window doesn’t behave like a normal one. Most of the hard problems came from there.

  • Notifications did nothingmacOS ignores notification requests from unsigned apps. Signing it properly fixed it, and a status row now explains any problem.
  • The widget crashedHover states that changed the layout’s size looped the menu window. Every button is now always laid out and fades in, so sizes never change.
  • Add Stop kept the last selectionThe window held its state after closing. It now resets whenever it closes or a stop is saved.

Trust, built in from the start

Planning for public release set three rules from the start: keep the data key secret, credit the data source correctly, and never look official.

  1. Bus Widgeton your Mac
  2. My serverholds the key, caches, rate-limits
  3. LTA DataMalllive arrivals and stops
  • The key stays on the serverLTA DataMall needs an account key. It’s never in the app or the repo, only a server secret.
  • Credit, done properlyAbout carries the Singapore Open Data Licence attribution, linked to the licence. DataMall is linked nowhere else.
  • Never looks officialNo LTA logos or wording. About says it’s an independent app, not affiliated with LTA.
  • Private by defaultAnonymous analytics never include stops, names or location, and one switch in Settings turns them off. A privacy page opens with a five-point summary.
  • Signed updatesEach update is cryptographically signed through Sparkle, and the app rejects anything that isn’t.
About tab: the Bus Widget icon, version 0.3.1, a line saying it's an independent app not affiliated with any transport authority, a Privacy Policy link and the data licence attribution.
General settings: open at login, automatic updates, version 0.3.1, a switch to share anonymous usage data, and notifications on with a Send Test button.

What’s next

  • Join the Apple Developer Program to notarise public downloads.
  • Switch between home and office stops by time of day.
  • iPhone and Apple Watch widgets on the same server.

Hiring, or have a product that needs simplifying?

Tell me about the role or the project.