Mobile app — the product
Players and captains. RSVP, schedule, roster, board, lineups. Designed for a phone in a hockey bag — never blocked because the “real” tool is a laptop.
Get the phone appOlympia
Know who's in before you leave for the rink.
The phone app for beer-league teams. Two-tap RSVPs, live headcount, roster, schedule, lineups, and a board that isn't buried in group chat.
Built for ice hockey first. Captains can also use a desk console for season setup — the team still runs on phone.
The chat is not a roster
Amateur teams run on unread messages. That fails on Thursday.
The schedule is a spreadsheet screenshot from March. Lines live in the coach's head. By puck drop nobody knows if you have a goalie. Olympia replaces that patchwork with one phone app centred on attendance.
Who's coming?
In, Out, Maybe, Silent — with live counts and position alerts like “no goalie.”
What's next?
Next event on home. Full schedule by week. RSVP state on every row.
What's the call?
Pinned board posts and published lines — signal, not banter.
Attendance — the core loop
Two taps from cold. Headcount that captains can trust.
Players answer In / Out / Maybe from the home card — no navigation required. Captains see live tallies, silent players, and critical gaps like a missing goalie before they leave for the rink.
- 56px RSVP control — the most-used target in the product
- Four states with hue, glyph, and fill (reads without colour)
- Captains can set RSVP on behalf when someone won't reply
- Optimistic, reversible until puck drop — changing minds is normal
Schedule
Games, practices, and the rest of the season — not a photo of a spreadsheet.
Upcoming events grouped by week. Each row shows type, time, location, and your RSVP. Captains add one-off games from the phone; season building can happen at a desk when you need it.
- Games, practices, and other events
- Home / away, venue, opponent, notes
- Attendance fraction and your own RSVP rail on every row
- Quick-add from schedule when a game gets moved
Roster
Names, numbers, and positions — not a spreadsheet tab.
Filter by forward, defense, or goalie. Players own their jersey and positions; captains can fix anything. Invite by share link or email so new skaters land on the next game, not a 400-message thread.
- Hockey positions from the sport catalog (soccer-ready later)
- Jersey uniqueness enforced per team
- Spare / sub flag when you need a call-up
- Roles: owner, manager, player — enforced server-side
Bulletin board
The signal channel group chat destroys.
Captains post announcements — dues, jersey colour, parking — and pin what matters. Optional link to an event so “white jerseys Thursday” stays attached to the game.
- Pinned posts first, then newest activity
- Manager-authored; players read on phone
- Event-scoped posts for pre-game calls
- Compose from phone or the captain web console
Lineups & strategy
Build lines from who's In. Players see their line on the event.
Tap-to-assign over the players marked In — forward lines and D-pairs from the hockey catalog. Save a draft, publish when ready. Each player gets “your line” on game detail instead of a screenshot in chat.
Seeded from Ins
Only available players enter the builder — no ghost names.
Sport catalog units
Lines and pairs come from config, not hardcoded hockey UI.
Publish to the team
Players open the event and see where they play.
For captains
Run game night from the rink.
Nudge silent players, set RSVPs on their behalf, publish lines, and post to the board — all on the same phone. A desk console exists for bulk roster and season work; it never blocks a captain who only has a phone.
- Attendance rollup with position breakdown
- Nudge non-responders / set-on-behalf
- Quick-add events when the league rewrites Thursday
Join the team
Invite link in, first RSVP out.
Share a multi-use invite link or send email. New players confirm name, jersey, and positions, land on team home, and answer the next game. Done means they RSVP'd — not that an account exists.
- Share link for WhatsApp and group chats
- Email invites when you have addresses
- Join code fallback if the link gets lost
How it works
Captain adds a game. Players tap In. Gaps show up early.
Step 1
Invite the roster
Share a link or email. Players confirm jersey and positions.
Step 2
Put games on the schedule
One-off from phone, or bulk at a desk when the season lands.
Step 3
Everyone RSVPs
Two taps from home, schedule, or a push into the event.
Step 4
Captain reads the board
Headcount, silent list, no-goalie alerts — then publish lines.
On the phone
The product is phone-sized. Every player action lives here.
Surfaces
Phone for the team. Desk only when volume demands it.
Captain console — optional bulk
Managers only. Dense roster edits, schedule, attendance rollups, and bulletin compose when you have a keyboard. Same data as the phone — never a player surface.
Captain sign inTeam messaging is in MVP scope and ships after attendance, roster, schedule, and lineups — once realtime transport is decided. Game-day check-in, scorekeeping, and league standings are later, gated on league partnerships.