Project · Web App
Poker Hand History Tracker: a fast-entry, mobile-first Bubble.io app
A web app for poker players who want to record complete hand histories on their phone, right after leaving the table. It's designed so a full hand takes under a minute to log, almost entirely by typing and tabbing: one page, no dropdown hunting, and a form that clears itself for the next hand. Built by Webziper in Bubble.io, as a web app designed only for the mobile view.
- Stack
- Bubble.io (web app, mobile view only)
- Type
- Fast-entry web app
- Industry
- Poker, personal tracking
What does it do?
Serious players review their hands later, to find leaks and spot patterns. The hard part is capturing the hand in the first place: in a live session, the next hand is already being dealt, and every second spent fiddling with an app is a second not paying attention.
This app records each hand for personal review: positions, stacks, cards, the action on every street, the result and a short note. It's private by design. Nothing is shared or posted.
Why is speed the whole spec?
Three rules shaped every decision in this build:
- Speed is everything. Every extra click or scroll costs real money in a live session.
- Typing beats clicking. Anything that can be typed is typed. Cards use standard notation, such as "As Kd" or "77".
- Free text is a last resort. Notes are only for reads and thoughts that don't fit anywhere else.
How is the page laid out?
Everything sits on one page, in the order a hand actually happens. Tab moves from one field to the next, so a player can fill the whole form without lifting their thumb to aim at small targets.
| Section | Fields | Input style |
|---|---|---|
| Setup | Session name, stakes, hero position, hero effective stack | Short text; position can be picked or typed |
| Villains | "Add villain": position + stack, up to 8–9 villains | Repeating group |
| Preflop | Hero hole cards, preflop actions | Card notation; one action per line |
| Flop, turn, river | Board cards and actions for each street | Card notation; one action per line |
| Result | Showdown line, net result in chips or BBs, notes | One line, a number, a small notes box |
Here's what a hand looks like while it's being entered:
Hero 3bets 35
UTG calls
What happens when you save?
The big Save Hand button is always visible at the bottom of the screen. After saving, the form clears and the cursor goes straight back to the first field. The player can start typing the next hand immediately, without scrolling up or tapping into a field.
It's a small detail, and the one that matters most. Logging five hands in a row should feel like one continuous flow, not five separate tasks.
What made it tricky?
- Field order and focus. Tabbing has to follow the hand exactly, and focus has to land in the right place after every save.
- Flexible inputs. Position works as a quick pick or a typed value, and stacks accept chips or big blinds.
- A repeating villain group. Players add as many villains as the hand needs, up to a full table, without the page getting in the way.
- Multiline actions. One action per line keeps entry fast while still capturing the full sequence on each street.
- Mobile view only. The web app is designed for one screen size, the phone, so every pixel goes to the form.
Why build it in Bubble.io?
The app is one carefully ordered form and a database of saved hands. Bubble.io builds that fast, and as a web app it works in any phone browser without an app store release. Designing only for the mobile view kept the scope tight and the experience focused.
A mobile-first web app fits when:
- The core job is fast, repeated data entry on a phone
- You want users on it today, without waiting for App Store or Google Play review
- The interface is mostly forms and lists, not device features
Consider a native app when:
- You need offline entry, push notifications or deep device features. See our CrossFit Programming App for a native Bubble.io build.
We build apps like this as Bubble.io development projects, often as a focused MVP. If you have a tool your users need to fill in fast, tell us about it.
Frequently asked questions
Can a Bubble.io web app work like a mobile app?
Yes. A Bubble.io web app can be designed for the mobile view only, so it fills the phone screen and works in any mobile browser. It can be added to the home screen and used without an App Store or Google Play release, which suits tools built around forms and lists.
How do you design a form for fast data entry on a phone?
Put every field on one page in the order the information happens, let users type instead of picking from dropdowns, make Tab move through the fields in that order, keep the main button always visible, and after saving, clear the form and put the cursor back in the first field.
When should you build a mobile-first web app instead of a native app?
When the core job is data entry, forms and lists, and you want users on it straight away without app store reviews. Choose a native app when you need offline use, push notifications or device features that a browser can't reach.
Can Bubble.io handle repeating groups of inputs, like adding several players?
Yes. Bubble.io supports repeating groups, so users can add as many entries as they need, such as a position and stack for each opponent, and the app saves them together with the main record.