Golf Sparks 1.1 (9) is live on both the App Store and Google Play. I counted what changed since 1.0 (8), which went out two weeks ago, and I had to run the numbers twice.
The numbers
Between build 8 and build 9 (November 1 to November 13):
- 60 commits.
- About 30,500 lines of code added and 1,100 removed, across 142 files of app, web and backend code.
- That is roughly a quarter of the codebase. The app, the web tools and the backend went from about 89,000 lines to about 118,500. About one line in four did not exist two weeks ago.
- Another 24,700 lines of model training and video-labeling tools that never ship in the app but are why the Coach got better.
Where the new code lives: about 15,000 lines in the shared Kotlin app (both phones), 12,500 in the new Swing Studio website, and 3,000 in the backend.
These are git line counts, which is a blunt instrument. A line count says how much changed, not how much it is worth. I am including it because "a quarter of the code changed in two weeks" is a different sentence than "I fixed some bugs."
What those lines were
I would call it about ten headline features and fifteen smaller ones. The big ones:
A new look, in four rounds
Every home-screen spark got a designed icon, and the home screen went to two per row so each icon is bigger. Golf Sparks is for middle-aged golfers, and the icons have to be clear even without reading glasses. Getting there took four rounds. Tap a screen to see it full size.
A rebuilt swing player
Two swings side by side, lined up at impact, with the best match suggested. A scrubber for the positions of a swing. Tap to set the tee ball. A one-to-ten rating on every swing. Here is the A/B view with an indoor swing (top) and an on-course swing (bottom) synced to the same moment:
And more
- A ball flight tracer. Drag the landing spot and the apex and export a video with the flight burned in.
- Whole-day Coach reviews. The Coach now reads a day's swings together instead of one at a time.
- A web Swing Studio. Sign in at golfsparks.dyor.com to review and correct your swings on a big screen.
- Coach focus and tone, a practice plan tab, and a few smaller rewrites of the swing recorder.
It reached both stores the same night
Build 9 went to TestFlight and Google Play from one window. I added a Publish to both stores button to my release tool, Publisher, this week: one set of release notes, App Store Connect first and Google Play second, one after the other. Before that I wrote release notes into one store, waited, then wrote them into the other and waited again. Doing it once, in sequence, is the whole feature.
Here is Publisher before the release, with every check green and the release notes filled in from the commits (I forgot to screenshot the real one that day, so this is recreated):
And after, with 1.1 (9) shipped and live on both stores:
It also taught me something about the failure cases. An upload failed the first time because the Mac ran out of memory and killed the build ten minutes in. Publisher now checks for that before it starts, instead of finding out at minute ten.
A new batch is already waiting
The next set of changes is already in the repo, and I expect to ship it later this week. I am not going to pretend this was a one-time sprint. The new normal is a major release to both platforms once or twice a week.
Why I think that is possible now:
- The release is no longer the hard part. Version numbers, signing, release notes and uploads are a button, not a morning.
- Both stores stay in step. Same version, same notes, same day.
- Reviews are faster than I feared. Apple approved this one, and Google Play shows 1.1.
- Small batches are safer. Two weeks of changes is a lot to hold in your head. Three days of changes is not.
I will report back on how the pace holds up. The honest test is the second week.
If you play golf, Golf Sparks is free on the App Store ↗ and on Google Play ↗. The new features and icons are here ↗.






