Last Week Week 47 was recorded at the gate, squeezed in between boarding calls on the final leg of the trip home. I didn’t open the Shokken repo, didn’t touch the feature list, and didn’t change a single line of code. Instead, I used that short update as a promise: once I was back at a real desk, I would stop issuing travel postcards and start delivering actual progress again....
Travel Day Check-In I am squeezing in this entry between boarding calls. The camera only captured a few sentences because there is still nothing meaningful to report on Shokken itself—I’m wrapping up the last leg of travel and staying disciplined about keeping the weekly commitment alive even when the laptop stays zipped. Last week you heard about the international leg; this time I am pointing back toward the States....
Dispatch from Another Country “Week number? I don’t know.” That line opens the video and sums up the whole situation. I have not looked at the Shokken app in quite a while because travel has me bouncing into yet another noisy but fun country. The laptop is staying zipped, so nothing changed this week beyond keeping the weekly promise to say hello. Thanksgiving Target In the clip I reiterate the travel plan: I will not touch the app for another two weeks....
Last Week Week 44 was sent from a rainy West Lake balcony where I promised to keep publishing even if the laptop stayed zipped up. I kept the Shokken alpha exactly where it was, let the CI pipeline recycle screenshots on its own, and mostly used my phone to confirm that tester messages were getting answered within a day. That check-in was really a travel postcard that said, “all systems nominal, founder temporarily offline....
A Quick Postcard From Hangzhou Week 44 is a short check-in from a borrowed desk overlooking West Lake. I kept the weekly promise, but the laptop stayed in the bag aside from making sure the Week 43 builds kept publishing and that tester feedback still lands in the inbox. The alpha release notes remain unchanged, shokken.rsvp keeps pointing people to the right install links, and the Play Console graphs look exactly like they did before I boarded the plane....
On The Road Week 43 found me bouncing between old haunts with my travel kit and a laptop that rarely left the bag. The wind hammered the camera, I forgot the microphone at home, and shipping time narrowed to minutes between family visits. Instead of forcing half-finished code, I treated the week as a checkpoint: the product is stable enough to hand to new people, the pipeline keeps publishing builds, and I get to absorb how the app feels after stepping away for a few days....
Android Test Mission Brief Thank you for lending your time to shape Shokken. This guide turns the Android testing session into a predictable checklist so every report lands with the details I need. Who Should Use This Guide Android devices only; the iOS flow lives in a separate briefing. You’ll need a Google account that can join testing groups and access Google Play. Keep shokken.rsvp handy—it is the single source of truth for builds, FAQs, and issue tracking....
Last Week Last week I recorded the update from a parking lot while the houseguests I was hosting rotated through the city. I used the downtime to map Google Play’s closed testing requirements, built a checklist for the fourteen testers I need to keep the track alive, and rewrote my dogfooding playbook so the first bug hunts have scripts instead of improvisation. Most of my energy went into people logistics: scheduling those friends and family members for thirty-minute screen-sharing sessions, documenting how to install from the Play Console instead of sideloading, and figuring out how to capture their feedback without asking them to learn SQL....
Last Week Last week I finally coaxed the Supabase cron job into draining the email outbox without manual babysitting. I replayed 500 queued notifications, watched the Kotlin client hand them off to Postgres, and confirmed Resend responds within the same edge invocation. With that loop stabilized the admin dashboard now reflects message success within seconds, and I officially declared the infrastructure feature complete. I did try to finish the Resend webhook, but Supabase keeps rejecting the callback with a 401 even after I disabled JWT enforcement....
Last Week Last week I finally pried open the Supabase email pipeline that had been stuck in limbo. I rewired the outbox drainer so it writes to a dedicated log table before and after each batch, captured the payload that Resend expects, and added defensive retries around the queue reader. Most of that effort went into proving the cron job could wake the Edge Function reliably; I ended up setting up a cron_debug_log table, replaying scheduled jobs, and verifying Supabase’s pg_cron extension was actually firing once a minute....