Menu
Get BowlSheet

Changelog

All notable changes to BowlSheet are documented here. The format follows Keep a Changelog, and BowlSheet adheres to Semantic Versioning.

[1.0.0] - 2026-06-07

First public release of BowlSheet.

Added

  • Offline competition scoring for Baker and individual games on iPhone, Android, and macOS, with automatic sync when back online.
  • Baker scoring with frame ownership, mid-game substitutions, and rolloff games.
  • Coach analytics: frame averages, spare conversion, Baker role stats, score averages and highs, match-play record, and handicap.
  • Per-throw capture: ball speed, lane alternation, pocket and strike quality, half-board targeting, and automatic split and leave detection.
  • Ball drilling and equipment tools, including dual-angle hand-layout math.
  • Preloaded oil-pattern reference data (PBA, NCAA, Kegel) with pattern markup.
  • USBC member and average lookup.
  • Web dashboard for coaches: magic-link sign-in, team and bowler analytics, CSV export and import review, and organization admin with role-based access.
  • Legacy BowlSheet CSV format preserved for export and import.
  • Team and season management.

Changed

  • Pricing moved to a per-team-seat model billed through Stripe in the web dashboard. The mobile apps are free to score with and have no in-app purchases.
  • Marketing site content was reconciled against the shipped product so every advertised feature reflects what is actually available today.

Removed

  • Removed claims for features not yet shipped: NCAA progressive tie-breaking, single-vs-multi-pin spare breakdown, in-app filter chips, in-app CSV share, App Store subscriptions, 30-day Trash recovery, and pull-to-refresh on the events list.

How releases are recorded

Each release gets its own section directly above the <!-- Add new releases above this line. --> marker, newest on top. Use a heading of the form ## [VERSION] - YYYY-MM-DD (for example, ## [1.0.0] - 2026-07-01), then list changes under the relevant category subsections:

  • Added — new features.
  • Changed — changes to existing behavior.
  • Fixed — bug fixes.
  • Removed — features that were taken out.
  • Deprecated — features slated for removal in a future release.
  • Security — fixes for vulnerabilities.

When cutting a release, move the relevant entries out of [Unreleased] into the new version section and leave the [Unreleased] category headings empty for the next cycle. Omit any category that has no entries for a given release.