gzl.dev/blog
field notes, mostly
18 posts
August 27, 2026
7 min
Nine ways to say yes
I taught a Light Phone to speak an Oura ring's protocol over BLE. Then I spent a week failing to tap a button that doesn't exist.
Light PhoneBrightOuraBluetoothAndroid
August 21, 2026
6 min
Field notes on LightOS
What the Light Phone III's OS actually is underneath: Android with the Google removed, hardware that talks in key events, and conventions nobody voted on.
Light PhoneLightOSAndroid
August 21, 2026
1 min
A tape recorder, not a voice recorder
BrightRecorder: clips named for where and when, tapes that are just folders of WAVs, and the wheel finally doing the job it was born for.
Light PhoneBrightRecorder
August 18, 2026
2 min
Why I put an app store on a phone designed to have none
Yes, I see the irony. The argument for building it, why there's no server behind it, and the afternoon I accidentally dropped everyone's apps from the index.
Light PhoneBrightMarket
August 14, 2026
2 min
A good fork says thank you
A lot of what I ship is other people's work with my name nearer the top than it deserves. Some rules I try to fork by.
Light Phoneopen source
August 11, 2026
2 min
My bug reports file themselves
Shake the phone three times and the app files its own GitHub issue. Then an AI triages the queue every hour — under strict instructions that guessing is worse than waiting.
Light PhoneAItooling
August 8, 2026
2 min
Fifteen copies of the same file
The least interesting code I maintain is the code I'd save first in a fire. On finally building the shared library.
Light PhoneKotlin
August 8, 2026
2 min
BrightMarket is out
The app store ships: browse on a desktop, install by QR, track updates on the phone, and get your own app into the catalog.
Light PhoneBrightMarket
August 7, 2026
2 min
One column of scores
Twenty-two leagues from four keyless public APIs, in one grayscale column. How BrightSports gets scores with no account and no push.
Light PhoneBrightSports
August 6, 2026
3 min
The MetroCard inside my phone
I dissolved a transit card in acetone and moved its nervous system into the battery compartment. Tap-to-pay is back, sort of.
Light PhonehardwareNFC
August 6, 2026
2 min
Every button does what you tell it to
The follow-up to the keylayout post: BrightControl itself, why the defaults took longer than the code, and the trust problem with accessibility services.
Light PhoneBrightControldesign
August 5, 2026
1 min
Roll is out
The camera app ships: a filter wheel on real hardware, purikura with four-shot strips, date backs, and a privacy lesson from launch day.
Light PhoneRoll
August 4, 2026
2 min
The keylayout file Light left behind
The scroll wheel is just key events. Everything I learned reading Generic.kl off the phone, and the accessibility service that became BrightControl.
Light PhoneAndroid
August 2, 2026
3 min
Rewriting the camera
Roll's whole design is one gesture, stolen from a contact sheet. Plus the filters that got away from me — purikura on a monochrome phone, and datamoshing experiments that mostly produce mud.
Light Phonedesign
July 29, 2026
1 min
A QR scanner, and its desktop twin
The modern world hands you addresses as QR codes and the Light Phone couldn't read them. A scanner for the phone, a generator page for every other screen.
Light PhoneLightQR
March 22, 2026
1 min
BasilNet, a year later
What broke, what I'd trim, and how the media server quietly became infrastructure for everything else I build.
Dockerhomelabself-hosting
March 8, 2026
1 min
I built a bad DSLR on purpose
It took worse pictures than my phone. It's one of the most useful things I've ever built.
hardwarephotography
January 10, 2025
1 min
Building BasilNet: My Home Server Stack
How I built a 15-service media server with Docker Compose, Gluetun VPN, and Home Assistant integrations.
Dockerhomelabself-hosting
← all posts
August 7, 2026 · 2 min

One column of scores

Light PhoneBrightSports

I follow too many teams for a phone with no scores app. LightOS has no sports surface at all, and refreshing ESPN’s mobile site on a 3.9-inch grayscale screen is a punishment I kept choosing anyway. So: BrightSports. One column of scores, grouped by day. Standings, one tab per league. A game page with first pitch, venue, TV listing, and both records. A notification when something happens to a team you follow. That’s the whole app, and the restraint is the feature — on this screen, a second column is a design failure.

Twenty-two leagues, zero API keys

The part I’m actually pleased with is the data story. The app covers MLB, NFL, NBA, NHL, MLS, five European soccer leagues plus the two UEFA cups, FBS college football, four women’s leagues, four levels of minor league baseball, and Formula 1 — and there is no account, no API key, and nothing to paste in, ever. Four public JSON providers carry all of it:

ESPN’s site API does the heavy lifting: every major, the European soccer, college football, most of the women’s leagues, and F1. The lovely thing about it is that the scoreboard response shape is identical across team sports, so one parser covers everything. The unlovely thing is standings, which nest differently per league — the fix is to walk the response’s children tree recursively instead of indexing into it and hoping.

MLB StatsAPI covers the four minor league levels, selected by sportId (11 through 14 for Triple-A down to Single-A). ESPN publishes no minor-league scoreboard at all; this is the same feed MiLB.com itself runs on, which is as close to the source as you can stand.

HockeyTech/LeagueStat carries the PWHL, and the fourth provider fills the last gaps. College football needed one extra trick: ESPN’s feed returns roughly 750 schools, so the app filters it down to the ~140 FBS programs, because nobody following Alabama wants to scroll past every Division III scoreline to find them.

Boring on purpose

Under the hood this is the least clever app I ship, deliberately. Follows are a SharedPreferences string set. Caches are plain files. There’s no database, no Room, no annotation processing in the build at all — clone it and it compiles fast and dumb. After a year of building increasingly elaborate plumbing for the other apps, there was real pleasure in writing one where the complete persistence layer is “a set of strings.”

Notifications work the way everything works on a phone with no push services: the app checks the feeds itself on a schedule and posts ordinary local notifications when a followed team’s game changes state. No server of mine in the loop, nothing tracking what you follow. If the phone is off, you find out the score the way people did in 2004, which frankly suits this phone.