Aside from the obvious great graphics and smoothness by which your finger moves around entering data you will notice that there is no category for setting the time line relationship with a meal. You do not need to spin a wheel to select; Before Breakfast, After Breakfast, Before Lunch, After Lunch and so on and so on. When entering glucose levels, you enter the level using a direct entry circle keypad and press next. The meter shows a big save button with the current date and time. From here you can press SAVE, or you can spin the wheel counter clock wise to backup time. If you need to backup by days you swipe your finger over the date and it backs up 24 hours.
At first I was missing my ten digit keypad but I soon found that I could enter numbers without searching for the right digit. You adapt to the round keypad. It may or may not be as fast for some but it was not designed to be faster. The GUI was meant to be more fun to use. In this interview (opens new window) with the co-founder of the program you learn this app was intended to be less clinical for his fiancé to use in managing her diabetes. I think the new design is faster than most if you give it a chance.
Now some of you are wondering about the lack of the “Before Breakfast”, “After Breakfast,” and so forth ability to tag a glucose level. LogFrog DB does it for you. If you record eating breakfast carbs at 7:00am, any glucose reading entered two hours or less than that entry is tagged as after breakfast. If you enter a glucose reading two hours and ten minutes later, that reading is not associated with a meal. This can cause problems if you enter glucose readings after that two hour window. Even five minutes late and your post meal glucose reading will not be association with a meal. That might be an issue in exporting of data to Google Spreadsheets (more on that later) and the time line log or graphic log.
You can quickly see how LogFrog DB is going to associated data entries by looking at the text log. Associated data will be grouped or bound together and data outside the time lines bindings will be standalone. If you make an entry and see that a glucose reading is not grouped with a meal record, you can easily back up the time a few minutes to bind those entries together, however recording glucose levels taken three hours after a meal and backing that time up to two hours is not a good idea. The two hour post meal blood sugar reading is important to tracking your diabetes. Manipulating the time stamp is a bad idea. On the other side, having to make a "Before Meal" or "After Meal" selection on other apps can be just as bad if you make a wrong selection or leave it open. LogFrog DB removes that variable, leaving you with better data to evaluate your post meal glucose levels.
Understanding how data entries of different types are grouped or bound together and making sure your entries keep the association you desire may seem confusing, but it does not take long to see the relationships in the text log and adjust accordingly. LogFrog DB also provides built in timers (ios4) and reminders you can configure to help you remember to take glucose readings or meds.
LogFrog DB is not a meal log book per se. It only lets you track carbs, but it does it very well. Instead of trying to be a food tracking program and failing, like many other leading apps, it tracks what is the most important food detail for a diabetic, carbs. I am a type two diabetic so I have no experience with the management of type one diabetes but I am pretty sure they need to track carbs far more diligently than type 2. This app is to-date, the fastest app I have seen for entering straight carbs.
LogFrog DB lets you log weight, blood pressure readings and A1C levels with the same ease as what has been covered so far. During my review I did not find medical notes section that beneficial. On an iPad you have a large keypad for typing. The iPhone does not. I have a hard time entering text for something as large as medical notes might be, unless I can use the keypad sideways. You cannot do that with this app. That said, the ability to enter medical notes is there and it does not get in the way of why I use the app.
LogFrog DB on my iPhone has been a valuable tool for helping me manage my diabetes. Regular blood glucose testing is very important for any diabetic. Recording those readings and events that affect glucose levels can greatly improve your understanding of what steps you need to take to improve your health.
When entering data is inconvenient, cumbersome or boring, I have a hard time recording the information I know I should. This app is not inconvenient, not cumbersome and not boring.
LogFrog DB Website (opens new window)
Each year in the U.S. diabetes results in the amputation of about 65,700 legs or feet. About 85% of those began with a diabetic foot ulcer. And for Dr. David Schwegman, the mission to educate people about the issue is personal.
His father, a diabetic, had a foot ulcer that resulted in the amputation of his left leg, which contributed to his death, his son said.
"He became a statistic," Schwegman said. "He was one of the 50% of people that died within five years after having an amputation."
FATWORLD is a video game about the politics of nutrition. It explores the relationships between obesity, nutrition, and socioeconomics in the contemporary U.S.