

I made a calculator website and it had a BAC calculator, but when I was speaking with some coworkers about their weekends, I realized that I needed a better way of tracking actual drinks and how people drink. So I added a new calculator to that website with actual drinks with actual pour sizes, and thought that it would make a good stand alone app. Please download if you have a drink every now and then.
Showing the BAC estimate as a Widmark curve with an uncertainty range, and stating it isn't a breathalyzer, is a more honest approach than a single number. How does the model handle body weight, sex and food eaten, and are those inputs optional? I'd also be curious whether the standard-drinks tally can switch to UK units for users outside the US.
Showing US standard drinks next to the plain drink count is a smart touch, since a tallboy or a cocktail is rarely one standard drink. I like that the BAC curve is labeled as a Widmark estimate with uncertainty and that safety tools like ride-home links stay free. Do you plan to let users add custom ABV for homemade or draft pours?
The decision I respect most here is keeping the safety tools — ride-home links, emergency contact and helplines — always free rather than putting them in Pro. That is exactly the moment people need them, and paywalling them would be wrong. The real-pour logging (actual size and ABV rather than a generic drink count) also makes the standard-drinks figure far more honest. One question: does the morning-after recap bring the water logging and spend tracking together with the BAC curve, so the whole review of the night sits in one place?
Logging real pours instead of a generic drink count is the right call: a 16 oz tallboy at 5% is already 1.33 US standard drinks (16 x 0.05 / 0.6). Two ideas from building calculators: show that working line under each tally so people can check it, and say which body-water factor the Widmark estimate uses. The classic 0.68 and 0.55 values can be well off for some builds, and the Watson formula (height, weight, age) narrows it.
Logging real pours instead of generic "drinks" makes a lot of sense. Two ideas from a European user's point of view: pours here are very different from US ones (0.2 / 0.3 / 0.5 l draft, 2 cl or 4 cl shots), so metric presets for those would make logging much faster outside the US. And Apple Health has a "Number of Alcoholic Beverages" data type, so writing the standard-drinks tally there would let sleep and HRV apps line up a heavier evening with the next night's recovery. That could make your morning-after recap even more useful. Is an Apple Health integration on your roadmap?




I made a calculator website and it had a BAC calculator, but when I was speaking with some coworkers about their weekends, I realized that I needed a better way of tracking actual drinks and how people drink. So I added a new calculator to that website with actual drinks with actual pour sizes, and thought that it would make a good stand alone app. Please download if you have a drink every now and then.
Showing the BAC estimate as a Widmark curve with an uncertainty range, and stating it isn't a breathalyzer, is a more honest approach than a single number. How does the model handle body weight, sex and food eaten, and are those inputs optional? I'd also be curious whether the standard-drinks tally can switch to UK units for users outside the US.
Showing US standard drinks next to the plain drink count is a smart touch, since a tallboy or a cocktail is rarely one standard drink. I like that the BAC curve is labeled as a Widmark estimate with uncertainty and that safety tools like ride-home links stay free. Do you plan to let users add custom ABV for homemade or draft pours?
The decision I respect most here is keeping the safety tools — ride-home links, emergency contact and helplines — always free rather than putting them in Pro. That is exactly the moment people need them, and paywalling them would be wrong. The real-pour logging (actual size and ABV rather than a generic drink count) also makes the standard-drinks figure far more honest. One question: does the morning-after recap bring the water logging and spend tracking together with the BAC curve, so the whole review of the night sits in one place?
Logging real pours instead of a generic drink count is the right call: a 16 oz tallboy at 5% is already 1.33 US standard drinks (16 x 0.05 / 0.6). Two ideas from building calculators: show that working line under each tally so people can check it, and say which body-water factor the Widmark estimate uses. The classic 0.68 and 0.55 values can be well off for some builds, and the Watson formula (height, weight, age) narrows it.
Logging real pours instead of generic "drinks" makes a lot of sense. Two ideas from a European user's point of view: pours here are very different from US ones (0.2 / 0.3 / 0.5 l draft, 2 cl or 4 cl shots), so metric presets for those would make logging much faster outside the US. And Apple Health has a "Number of Alcoholic Beverages" data type, so writing the standard-drinks tally there would let sleep and HRV apps line up a heavier evening with the next night's recovery. That could make your morning-after recap even more useful. Is an Apple Health integration on your roadmap?
Find your next favorite product or submit your own. Made by @FalakDigital.
Copyright ©2026. All Rights Reserved