Snooker Score AnnouncerBETA

To do

• P1 (this week): email Hendon to thank him for the second mention on the season-finale pod. Brief, warm, not gushing. Acknowledge Sam's feedback as useful, mention the inspiration loop closing satisfying. Don't be clingy - one note then leave him alone.
• P1 (this week): reach out to Sam if reachable. He met Hendon in person last October, so possibly known to Hendon - could ask the pod for an intro, or wait for Sam to get in touch via the contact form (he may already know it exists, having tried the tool). Sam has thoughtful, articulate, lived-experience opinions about the tool and the ecosystem. The user research interview you couldn't have arranged - if he's willing to talk, listen.
• P1 (this week): reach out to Ricky Stone (Snooker Live developer). Ecosystem hello. Frame as cooperative, not competitive - different platforms, different use cases. Mention Sam's feedback recommending both tools alongside each other. Could lead to: insights on iOS accessibility specifics, awareness of overlap/divergence, possible cross-promotion. Wait until you've actually used his app first - speaking from genuine experience matters.
• P2 (this weekend): download and use Ricky Stone's Snooker Live iPhone app properly. Things to observe: how VoiceOver handles it (Sam noted recent accessibility improvements - what are they concretely?), the live-activity / lock screen experience (the bit your tool can't do on iPhone), push notification cadence (frame-by-frame? configurable? match-end only?), what tournaments it covers (probably uses the same snooker.org API since Hermund's is the only public source), what it DOESN'T do (gaps your tool fills - Sam already named the laptop-background-listener case, may be others). Use this experience to inform the Ricky outreach and Info-page update.
• P2: update the Info page to mention Snooker Live as a sister tool for iPhone users. Sam framed it well on the pod: "iPhone with VoiceOver → Snooker Live; computer / laptop or background-while-watching → Snookerannouncer." Generosity costs nothing and reciprocates Sam's framing. Wording something like: "If you're on iPhone and want lock-screen notifications and live activities, also check out Snooker Live by Ricky Stone." Worth doing AFTER you've used the app yourself.
• P2: phone usability is broken in practice. Sam confirmed on the pod that the iPhone version works in theory but the screen-lock issue makes it impractical - you can't use the phone for anything else while it runs, and you'd need to disable screen lock. Two routes: (a) document the workaround clearly on the Info page (audio mode, Lock Mode, screen-lock-disabled), (b) build proper PWA with background audio so the page can run with the screen off. (b) is real work but solves a real problem - and Sam is exactly the user this would unlock. Worth investigating what's actually possible on iOS Safari for background audio (suspect it's quite restricted) before committing.
• P3: qualifying weeks are arguably the tool's strongest moment - Sam explicitly called out "multi-table sessions and qualifiers" as where these tools shine. Sighted fans also benefit because TV doesn't cover qualifiers, just live scoring. Worth thinking about how the tool communicates this strength: a dedicated "qualifiers mode"? Better multi-match readouts? Marketing copy on the Info page? Future post-on-FB topic? No urgent action, but worth noting that the qualifiers calendar (next major one TBD) is a peak-relevance moment.
• P3: wake-on-sleep cross-platform testing. Confirmed working on laptop. Still pending: iOS Safari (visibility events) and Android Chrome (pageshow.persisted). Tied to phone-usability work above - if PWA mode happens, retest wake.
• P3: social post acknowledging Ricky's app and the parallel ecosystem. Sam framed it well on the pod; doing it publicly cements cooperative framing rather than competitive. Possibly a Snooker Hub FB post via Margie, or Reddit. Wait until after the Seniors final on Sunday - timing-wise, mid-tournament is wrong for ecosystem posts.
• P4: consider enabling HSTS in Cloudflare SSL/TLS settings. Closes one of the Security Insights warnings. Held off because it's effectively irreversible (browsers cache the policy for the configured max-age) and the marginal protection over "Always Use HTTPS" is narrow. If enabling: start with max-age 1 month, do NOT tick preload, do NOT tick includeSubdomains until thought through.
• P4 (April 2027): refresh the Expires date in serveSecurityTxt() before May 2027. Currently set to 2027-05-05T00:00:00Z. RFC 9116 requires the date to be in the future; an expired security.txt reads as neglected.