← Back to Build Log
Aug 21, 10:10 AM PSTMorning Launchfix

The scrolling bug that started three waves of work is closed

For weeks, scrolling to the bottom of the day's plan could just stop responding — you'd drag, nothing would move, and the third try would work. It was the single most disruptive thing left in the app, and it was hard to pin down because it wouldn't happen on demand. It's now closed after three separate hands-on sessions across three different days, every one of them clean, all run against the same build so the results could actually be compared. What made the close honest rather than hopeful is that we knew where the fault lived: earlier measurement had shown the dropped drags never reached the part of the system that handles scrolling at all, and the code responsible for that routing was replaced wholesale in the recent rebuild of how days are paged through. So the fix isn't 'we couldn't reproduce it' — it's that the thing it lived in is gone. One session did turn up something that looks identical from the outside and isn't, which is worth saying out loud: a stray tap being swallowed and a dead drag are indistinguishable in a screen recording, because recordings don't show where a finger is. That got settled by asking the person holding the phone, before writing down a verdict rather than after.

#ios#usability#reliability
Friday, August 21, 2026 at 5:10 PM UTC
View commit

Share This Ship

Post 1/875/280
🔧 Shipped: The scrolling bug that started three waves of work is closed 🧵
Post 2/8266/280
For weeks, scrolling to the bottom of the day's plan could just stop responding — you'd drag, nothing would move, and the third try would work. It was the single most disruptive thing left in the app, and it was hard to pin down because it wouldn't happen on demand.
Post 3/8182/280
It's now closed after three separate hands-on sessions across three different days, every one of them clean, all run against the same build so the results could actually be compared.
Post 4/8319/280
What made the close honest rather than hopeful is that we knew where the fault lived: earlier measurement had shown the dropped drags never reached the part of the system that handles scrolling at all, and the code responsible for that routing was replaced wholesale in the recent rebuild of how days are paged through.
Post 5/886/280
So the fix isn't 'we couldn't reproduce it' — it's that the thing it lived in is gone.
Post 6/8252/280
One session did turn up something that looks identical from the outside and isn't, which is worth saying out loud: a stray tap being swallowed and a dead drag are indistinguishable in a screen recording, because recordings don't show where a finger is.
Post 7/8105/280
That got settled by asking the person holding the phone, before writing down a verdict rather than after.
Post 8/889/280
Follow the build → build-log-five.vercel.app

#ios #usability #reliability #buildinpublic
← Shared map links now reach the arrival planner, even when they arrive shortenedThree fixes so the same gesture means the same thing everywhere→