HealthHive

HealthHive

Know about what goes in your food

The problem HealthHive solves

As more and more people are becoming health-conscious, it is important to have access to accurate and easy-to-understand nutritional information for the foods we eat. However, finding this information can often be difficult, especially for packaged foods and homemade recipes. That's where HealthHive comes in.

Our inspiration for HealthHive was to create a simple and convenient way for users to access nutritional information for a wide range of foods, including packaged foods and recipes. By using a Barcode code scanner and a recipe analysis feature, we wanted to make it easy for users to quickly retrieve and view this information, without having to search through lengthy labels or websites.

HealthHive is a mobile app that allows users to scan the Barcode on the back of a packaged food to view its nutritional information. The app displays the information in a clear and easy-to-understand format, including details on the serving size, calories, and various nutrients. If the nutritional information for a particular food is not available in the app's database, users can also contribute by adding it themselves.

In addition to the Barcode code scanning feature, HealthHive also offers a recipe analysis tool. Users can enter the ingredients used in their recipe and the app will calculate and display the nutritional information for the entire dish.

HealthHive also has a user login and registration system. Users can create an account with HealthHive using their email address and password, or they can use their Google account to sign in. Once logged in, users have access to their own personal profile page where they can view and edit their account information.

Challenges we ran into

One of the main challenges we faced while building HealthHive was integrating the Barcode code scanner into the app. There were a few different libraries available to use, but finding one that was compatible with React Native and easy to set up took some trial and error.

Another challenge we encountered was making sure the nutritional information was displayed in a clear and easy-to-understand way. We wanted to avoid overwhelming users with too much information, so we had to carefully balance the amount of detail provided. Implementing the login and profile features also presented some challenges, as we had to make sure the user's data was securely stored and protected.

Developing the recipe analysis tool also required some research and development time. We had to make sure these features were reliable and seamless for the user.

Discussion