Every lane is coated with oil you can't see. It protects the lane — and it decides where your ball skids, where it hooks, and whether a good shot carries. A pattern sheet is the map. Here's how to read it.
The ball skids on the oil, then grabs the dry boards and hooks toward the pocket. Almost everything on a pattern sheet is telling you where that handoff happens and how much room you get.
The single biggest number. It's where the oil stops, so it's where your ball can finally start hooking.
Short (under 36 ft): ball hooks early, breakpoint is out near the gutter. Play more direct, keep it right.
Medium (37–42 ft): the common range; breakpoint usually boards 8–12.
Long (43 ft+): less room to hook. Play straighter and closer to the pocket, breakpoint boards 13–16.
Treat it as a starting point, not a law. It's most reliable on sport patterns and in the 37–42 ft range, and it drifts on very short or very long patterns. It tells you where motion can happen — your ball, speed, and rev rate decide the rest.
The side-to-side comparison of oil in the middle vs. the outside. This is what makes a shot forgiving or brutal.
House shot (roughly 8:1 or higher): lots of oil in the middle, dry outside. That difference acts like a
funnel — miss right and friction hooks it back, miss left and the oil holds it. Very forgiving.
Sport (3:1 or less): oil is nearly flat across the lane. No funnel, no bail-out. Miss two boards and
you'll see it in the pin count. This is why Junior Gold scores look nothing like league scores —
the same bowler, on a flatter ratio.
Total conditioner, listed in millilitres. More volume means more skid, so you'll generally want a stronger ball or a duller surface to get the same shape. Less volume means the lane grabs sooner — often the moment to go weaker or shinier before it over-hooks.
The bar chart shows how many units of oil sit on each board, and the pattern is applied going down the lane and then back. Tall bars in the middle with short ones outside is that house-shot funnel drawn out. Bars nearly level across is a sport pattern. You don't need to read every number — look at the shape: where's the wall of oil, and where's the friction?
Oil moves. Every shot carries a little downlane and scrubs a little off the front. Over a block the ball starts hooking earlier, then the fresh friction lines burn up. This is why bowlers move left across a set. Coaching note: if a kid's first game is strong and the third falls apart, that's usually transition, not mechanics — and Strikebook's game-position averages will show it as a pattern across many sessions.
Length tells you where to play. Ratio tells you how badly a miss will hurt. Volume tells you how much ball to throw. Everything else is detail.
Strikebook is a single self-contained file. Everything — sessions, history, analytics — is stored on this device, in this browser. No bowling data is ever uploaded anywhere unless you turn on cloud sync (see §5) — and even then it's locked on this device with your private sync ID before it leaves, so the server can't read it. The other optional exception is a visit counter (see §13) that a coach can turn on to see rough usage over time; it's off by default, and even switched on it never carries names, scores, or anything else personal — just "the app opened, on this version." That means privacy by default, and it means backups are your responsibility (see §5). New users see a short welcome tour the first time they open the app, covering home-screen install, backups, and where to find this manual.
Opening the app lands you on a menu — one tap to 🎳 Start a session, plus History, this manual, the How To guide, and feedback, all in one place. Tapping Start a session takes you to a dedicated screen for picking bowlers, turn order, session type, and lane condition before you begin; ← Menu there takes you back without starting anything. For quick "how do I do X" lookups without reading the whole manual, the 📋 How To guide on the menu has short numbered steps for every feature.
Pin rack mode (default): tap the pins left standing after each ball, then hit the big count button. Tap nothing = strike. This mode feeds all leave/spare analytics.
Keypad mode: faster, counts only — those frames score perfectly but can't appear in the practice rack or spare ledger.
F records a foul (scores zero, full rack respotted per rule). MISS records a ball that knocked nothing down (scores zero, shown as –) in one tap. To correct a ball, press and hold its frame (see Fixing a mistake below). The announcer and share cards run themselves.
Turn order: once 2 or more bowlers are selected on the setup screen, a TURN ORDER list appears — drag a name by its ☰ handle to change who bowls first, second, and so on. This sets both the normal rotation and, for Baker sessions, the frame-by-frame throwing order.
Reordering mid-game: a ⇅ Reorder turns button sits above the scoresheet any time 2+ bowlers are in the session — a late arrival, a kid who needs a break, anything. Drag to reorder the same way. Whoever is mid-frame right now keeps their turn; the new order takes over starting with the next bowler up. In Baker mode, any frame that's already been thrown keeps the bowler it was thrown by, permanently — reordering only changes who's next, never who threw what.
Fixing a mistake: press and hold any frame on the live sheet — even one from several frames back — to re-enter it. Every score from that point forward recalculates automatically, and wherever the bowler currently is in the game is completely undisturbed. The editor opens on the same pin rack used for live scoring, so tapping the exact pins left standing keeps that frame's leave detail fully accurate in the practice rack and spare ledger. There's also a 🔢 Quick numbers toggle for when you just need the score fixed fast and don't care about pin detail for that one frame.
Clearing a frame: on a bowler's most recent frame, the editor also offers Clear this frame. It removes every ball in that frame so it's bowled again from ball 1 — use it when a ball went on the wrong bowler's tab, or when ball 1 was entered wrong and ball 2 hasn't been thrown yet. Earlier frames can't be cleared (that would leave a gap mid-game); re-score them instead.
When the night's games are done, tap 🏁 Finish session. That permanently banks everything into History and returns to the menu. Reset is the destructive one — it discards the current session without saving. Rule of thumb: Finish always, Reset only for do-overs.
Forgot to score something live? In History, tap 🗓 Log a past session — pick who bowled, the date it actually happened, and each game's score. Type a final total for a quick entry, or tap the 🎳 next to any game to walk through it frame by frame on a number pad — same rules as live scoring, strikes and spares included, just no pin rack, so exact pin leaves aren't captured for these games (the scoresheet, strike count, and spare count all are). Mix and match freely: some games quick, others frame by frame, in the same session. Everything counts fully toward averages, highs, and session history either way. Any saved session's date can be changed too — open it and tap ✎ Edit label. Session lists sort by that real date, so a backdated entry lands where it actually happened, not at the top just because it was typed in today.
Tap 🏆 Leagues on the menu to set one up: name, number of weeks, start and end dates, and Scratch or Handicap. For Handicap, pick one of three real-world presets — 90% of 220 (most common in adult sanctioned leagues), 90% of 200 (typical for youth leagues), or 80% of 220 (more competitive) — or Custom to set your own basis and percentage.
Bowling in it: pick League as the session type when starting a session, and a WHICH LEAGUE? list appears showing every open league — tap one before you can bowl. No open leagues yet? A shortcut drops you straight into league setup and brings you right back with it selected, no detour required.
Closing a league (from its card in the Leagues list) moves it to a separate closed section — it drops off the picker for new sessions, but every session already linked to it stays exactly as it is in History. Closed leagues can be reopened any time from the same screen.
Tap into any league to see its own numbers, separate from every other league or practice game: standings — everyone who's bowled in it, their average using just this league's games (the same 21-game window as everywhere else in the app — a growing average until 21 games, a trailing 21 after), and their handicap if the league is scored that way; league records — the high scratch game and high scratch series set in this league specifically, kept apart from a bowler's career-wide Personal Records; and an average trend by week for whichever bowler you tap in standings, once they've played 2 or more weeks. ✎ Edit league from the same screen changes any setting, including closing or reopening it.
Deliberately not tracked per league: the practice rack, Nemesis Pin, spare-class tiers, the drill list, and game-position average all stay pooled across every game a bowler has ever played, not split up by league — they're skill-development numbers that are more useful with the biggest sample size available, not fragmented by which league a game happened to be part of.
While bowling in a handicap league, the scoresheet shows a scratch + handicap row right below MAX POSSIBLE — the handicap is set once, from that bowler's entering average going into tonight, and never changes mid-session, same as a real league sheet would work. It only shows up once a bowler has an established average from a prior night in that league; their very first night, it's scratch-only until next time. The same scratch + handicap breakdown appears again on the session recap afterward.
Auto-backup (desktop Chrome/Edge only): on the menu, tap the backup status pill and choose
a folder — ideally your synced Google Drive/iCloud/Dropbox folder. From then on, every Finish session
writes a dated backup file there automatically. This isn't available on iPhone or in most mobile browsers —
the pill will say so plainly rather than pretend it works.
Manual backup (works everywhere): History → ⬇ Save backup file → store the JSON in a cloud
folder you keep. To restore or move phones: open Strikebook on the new device → History → ⬆ Load
backup. Imports merge safely — loading the same file twice never duplicates. Why this matters:
clearing browser data (or iOS storage housekeeping) can erase on-device history without warning. A backup
file — auto or manual — cannot be erased by a browser.
Cloud sync (optional, set up once): keeps saved history and leagues the same on every device that
uses the same sync ID — a new phone, or a second device. It's hidden until it's set up: on the menu,
tap the backup status pill, then Cloud sync › at the bottom. Tap New ID (or type the ID from
your other device) and Turn on. While the coach has the admin gate on, New ID first asks
for the admin passcode — it's checked by the sync server, never saved in the app, and only needed
once per new ID; a device joining with an existing ID never needs it. Write the ID down — it's the only key to that synced copy;
nobody can recover it for you. Everything is encrypted on the phone with that ID before upload, and the
server only ever sees a scrambled file under an anonymous name. Once on, History shows ☁ Sync now
and when it last synced; it also syncs by itself after every change and each time the app opens, and
catches up when you're back online. Only saved sessions sync — an unfinished session stays on the
phone it's being scored on until you tap Finish. With sync on, deleting a session or removing a bowler
applies to every device using that ID. Sync needs a free Cloudflare Worker that the coach sets up once
(strikebook-sync-worker.js in the repo has the steps — the admin passcode is set there as the
ADMIN_CODE secret, and adding OPEN_ENROLLMENT = true later lets anyone make an ID); put its address in SYNC_SERVER near
the top of the app file, or type it in the Cloud sync screen. Cloud sync is in addition to backup files,
not a replacement — keep saving those.
Career stats group by a hidden bowler ID, so renaming a bowler never splits their history. Leave percentages count only pin-rack entries. A leave needs 4 attempts before it's ranked (under that, it's held in the "keep bowling" note). Splits are tracked separately so they don't drag down the makeable-spare percentage. The drill list estimates ~11 pins of scoring cost per missed spare — an approximation, flagged as such. Game Craft adds Clean Frame % (marks per frame, works even for keypad games) and Bounce-Back % (how often a mark follows an open). Spare Classes rolls every leave into three difficulty tiers — singles, makeable multi-pin, splits — and the Nemesis Pin is simply the single-pin leave you see most. The Ball-by-Ball block adds first-ball average (the strongest predictor of scoring), strike rate, double rate (strikes that follow strikes), clean-10th %, and a consistency figure (± your game-to-game swing). Game-Position Average compares your 1st vs 2nd vs 3rd game to reveal warm-up or fatigue patterns; it needs a few multi-game sessions before it appears. Progress is the AVERAGES card near the top of a bowler's page — switch between Score, Strike %, and Spare % to see a 21-game rolling average (growing under 21 games, trailing 21 after) for Overall, Tournament, and every league they've bowled in by name. It always shows the bowler's full history regardless of the Career/Last 5/Tonight scope above it, since a trend needs the long view. Strike % and Spare % use the same per-frame math as the Ball-by-Ball and Game Craft numbers elsewhere on the page, so a line here never disagrees with a number shown anywhere else. Lane condition (House / Sport / Challenge, plus an optional pattern name) can be set on the setup screen or added later by editing any session's label — it's stored so future analytics can compare how a bowler scores across easy house shots vs tough sport patterns. You can pick a known pattern from the list or free-type any name, which matters because tournament patterns like Junior Gold are kept secret until after the block. When a pattern name is set, the session page shows a 🔍 Look up in the Kegel pattern library link that opens Kegel's official library (and copies the name so you can paste it into their search) — handy for pulling the actual pattern sheet before practice.
Baker mode: pick "Baker" as the session type on the setup screen with 2+ bowlers. You'll score one shared sheet where bowlers alternate frames (lead-off throws frames 1, 6; second throws 2, 7; and so on). The app shows whose turn it is on every ball. Baker games don't produce individual game scores, but each frame's pin leaves are still credited to the bowler who threw it — so a kid's spare practice data keeps building even from Baker play.
Spare drill: on any bowler's page, tap 🎯 Start spare drill. The app deals target leaves weighted toward that bowler's weakest spares, you set them up (or shoot them on a full rack) and tap made/missed. Drill results are stored separately from match play, so they don't inflate real game stats.
Coach report card: tap 📋 Coach report card to generate a one-page image of a bowler's key stats — perfect for texting a parent or printing for a practice folder. It uses the phone's share sheet, or downloads if sharing isn't available.
Score a kid on your phone, then hand off just their games so they land on the kid's own device — separate from the all-in backup. On any bowler's page, at the bottom, tap 📤 Send [name]'s data. That produces a small file with only that bowler's sessions; send it however you like (text, AirDrop, email). On their phone, they open History → ⬆ Load / import and pick the file. Strikebook detects it's a single-bowler file and asks whether to merge into their existing history or import as new — always a confirmation, never automatic. Sessions already on their phone are skipped, so sending the same file twice never duplicates anything. After the first merge, both devices share that bowler's hidden ID, so future handoffs line up automatically.
Remove from this device: the red button beside it deletes only that bowler's data from your phone — useful once you've handed a kid off and don't need to carry them anymore. It never touches their copy. If the bowler shared a session with others, only their part is removed and the rest stays.
Backup vs handoff — the difference: Save backup file is everyone at once, for protecting your data. Send [name]'s data is one person, for giving it to them. Load / import accepts either kind.
Keep one master copy of strikebook.html in your cloud drive. Your data is keyed to where the file lives — browser storage belongs to the page's location. So: replacing the file at the same location with a newer version keeps all history; moving it (new folder, new host, new domain) orphans the old data. Before any move: export a backup, move, then import. To modify the app, give the current file to Claude and describe the change; test with a throwaway session before trusting a new version at a tournament.
Strikebook lives at a web address, so there's no app store and no download — you "install" it by saving the page to your home screen. It then opens fullscreen with its own icon, works offline, and stores history right on the device. Send your team the Strikebook URL and these steps.
iPhone / iPad (must use Safari):
1. Open the Strikebook link in Safari — not Chrome, not the in-app browser inside Messages or Instagram. If it opened somewhere else, copy the link and paste it into Safari's address bar. This step matters most on iPhone: only Safari can add to the home screen, and home-screen apps get more durable storage than a regular tab.
2. Tap the Share button (the square with an up-arrow, at the bottom or top of Safari).
3. Scroll down the share list and tap Add to Home Screen.
4. Tap Add in the top corner. The bowling-pin icon appears on the home screen — open it from there from now on, not from Safari.
Android (Chrome):
1. Open the Strikebook link in Chrome.
2. Tap the ⋮ menu (three dots, top-right).
3. Tap Add to Home screen (on some phones it reads Install app).
4. Confirm with Add / Install. The icon lands on the home screen; some phones may pop up a one-time "install" banner you can just accept.
Why bother installing vs. just bookmarking: the home-screen version launches fullscreen with no browser bar, works with no signal (handy in an alley with bad wifi), and — on iPhone especially — its saved history is far less likely to be cleared by the browser's storage housekeeping. A plain Safari tab can lose data after a week of not being opened; a home-screen app doesn't.
First-launch note: because the app runs from a web address, the very first open needs a connection (after that it works offline). If nothing loads at an alley, it's almost always wifi — try again on cell data.
Strikebook is hosted at a GitHub Pages URL — that's the address you send people to install (§9).
To publish an update: in your GitHub repo, upload the new index.html and click "Commit changes" — same filename, same repo, so it replaces the old version at the same URL. That's what keeps everyone's on-device history intact (see §9): the URL never changes, only the file behind it does. Pages usually rebuilds within a minute; hard-refresh the phone to see the new version. Never rename the repo or change the URL once the team is using it — that's the "moving the file" scenario in §9, and it orphans history until everyone re-imports a backup.
Share button does nothing: some in-app browsers block the share sheet — the card downloads instead; share the PNG manually. History looks empty: you may have opened the file from a different location — import your latest backup. Buttons unresponsive after an update: fully close and reopen the browser tab. When in doubt: export a backup first, then investigate.
Strikebook can send one anonymous ping each time it opens — "the app was opened, running v1.17.0" — to a free counter you'd own, so you can see rough usage over time without asking anyone. It carries no names, no scores, no bowler data of any kind, and apart from cloud sync (only if you set it up, §5) it's the only network call the app ever makes besides loading itself.
Turning it on: create a free account at goatcounter.com (no credit card, non-commercial use is free), which gives you a short "site code." Put that code into VISIT_COUNTER_CODE near the top of the app file. Leave it blank — the default — and the app never makes this call at all; nothing about its behavior changes.
Reading it: your GoatCounter dashboard shows visits over time automatically. Because every ping is tagged with the version number, its "Pages" view breaks visits down by version too — so you can see, for example, how many opens happened on v1.16.0 versus v1.17.0 as people update.
On the menu, 💬 Send feedback or request a feature opens a short form: pick the area it's about (scoring, analytics, Baker mode, and so on — or Feature request), mark it as a bug, idea, praise, or question, and write your message. Leaving the include app version & device info box ticked attaches the version, phone type, browser, and whether it's running as a home-screen app — that context solves most bug reports without a round of questions. Untick it if you'd rather not send it.
Where it goes: tapping Send opens your mail app with everything already filled in and addressed to the coach — you just hit send. If that doesn't work on your device — some phones have no mail app set up — tap 📋 Copy instead and paste it into a text message. Copy always works, including with no signal.
For the coach (setup): the destination is two lines near the top of the app file — FEEDBACK_EMAIL (currently set) and FEEDBACK_FORM. Swap in a Google Form URL in the second if you'd rather collect responses in a spreadsheet; the form takes priority if both are filled. If both are ever emptied, the Send button hides and only Copy is offered, so nothing breaks.
The version you're running shows at the bottom of the menu. To confirm everyone's current, have them check that number against the top of this list. After an update, the first launch shows a What's New screen listing only what changed since the version that device was on — so nobody has to read the whole history to catch up. A brand-new install skips it.
Older layout and reliability fixes were folded into 1.0.0 and aren't listed separately.