I was intrigued when I ran across this but very quickly decided that it’s not what I wanted. In my opinion it has room to grow. Here’s why. What’s your definition of “drink”? Typically a drink is determined based on the number of shots in it. Different drinks are given different weights based on the amount of alcohol. My typical “drink” is 4oz of whiskey over a single ice cube. While I classify that as 1 “drink” it’s technically 4! If I have 2-3 then you can see where we get very quickly. This app needs the ability to put in drink recipes (or have pre-loaded drink types) so that the user has the opportunity to reliably enter an honest record. The whole basis of this app is for the user to be honest with themselves about their consumption, but knowing what their actual count is starts with understanding the ACTUAL numbers. ESPECIALLY if that number is going into Apple Health!!!
Hello Eric,Thank you very much for your feedback. This was actually a deliberate design choice: we wanted to keep drink logging simple rather than making it overly sophisticated.I completely understand your concern, but I’d like to clarify the Apple Health point. Drylendar saves data using Apple Health’s numberOfAlcoholicBeverages record, which Apple defines as “a quantity sample type that measures the number of standard alcoholic drinks that the user has consumed.”Because of that, there is no approximation or custom interpretation on Drylendar’s side ; the value is stored exactly in the format provided by Apple Health.
