Hi everyone — I'm building vibeGTOtrainer, a browser-based Texas Hold'em study project, and would love feedback from poker players.
You can try two guest drills without creating an account: identify the best five-card hand from seven cards, and calculate the break-even equity needed to call. The trainer shows the correct answer after each attempt; for pot odds it also shows the calculation. For example, if the pot after a bet is $30 and calling costs $10, the break-even equity is $10 / ($30 + $10) = 25%. Registered users can access more drills and save their progress.
The trainer is free while it's in development, with no paid checkout at present. It is a pet project, not a poker room. The GTO practice mode is still being built: the current drills teach fundamentals, and I'm not claiming they are solver-backed GTO strategy.
Try the guest drills here: https://vibegto.top/practice/?utm_s...tm_medium=forum&utm_campaign=community_launch
You're welcome to test and provide feedback here or at [email protected]. I'd especially appreciate reports of incorrect answers, confusing explanations, or awkward mobile interactions. I'm the developer and will respond to questions and bug reports in this thread.
You can try two guest drills without creating an account: identify the best five-card hand from seven cards, and calculate the break-even equity needed to call. The trainer shows the correct answer after each attempt; for pot odds it also shows the calculation. For example, if the pot after a bet is $30 and calling costs $10, the break-even equity is $10 / ($30 + $10) = 25%. Registered users can access more drills and save their progress.
The trainer is free while it's in development, with no paid checkout at present. It is a pet project, not a poker room. The GTO practice mode is still being built: the current drills teach fundamentals, and I'm not claiming they are solver-backed GTO strategy.
Try the guest drills here: https://vibegto.top/practice/?utm_s...tm_medium=forum&utm_campaign=community_launch
You're welcome to test and provide feedback here or at [email protected]. I'd especially appreciate reports of incorrect answers, confusing explanations, or awkward mobile interactions. I'm the developer and will respond to questions and bug reports in this thread.
