Food Diary Software

It is not technically difficult programming making a food diary. It is a tremendous amount of work load to program it. There are many screens that needs to be programmed. Each screen has to be visually attractive. Easy-to-use. And powerful.

It took nine months to fine tune the graphical interface of the food explorer.

The third most challenging aspect of programming a food diary is the food database. They are tens of thousand of foods entered into the database. It’s not enough, on one hand, and too much, on the other hand.

It is not enough because there are so many foods and combinations of foods that unless a person enters each ingredient, there is not enough foods in database. But then when we enter more foods into the food diary database, the database becomes huge an unusable.

So it is either too big or too small. This is a long-standing problem with food diary. Personally, I still have not come up with a solution.

I have spent months and months and months perfecting the food diary. There are something like 30 screens in the food diary. Each screen has to be beautiful and functional. That’s a difficult task.

The sheer amount of work because of the number of screens is daunting.

Another big problem is how to represent the food database to the user. The user wants quick access to the foods. But it appears that unless the user familiarize himself with the database, there is no way to achieve quick access.

About 5% to 10% of the people who use the software don’t want take the time to learn database. Most people take the time to learn the database, and these are the most successful users.

I would very much like to hear from users what functions they want in the software. It would be wonderful to hear from you about new features and new screen designs that you would like to see in the food diary.