Project Limitations and Constraints

Some sacrifices we made along the way.

Where's Our Workout Section?

Starting out, we wanted Freshie to have two sections: one for nutrition and another for workouts.

Over the course of our development however, it became clear that we had underestimated the learning-curve of the frameworks and also the amount of work needed to go into each.

We thus decided to abandon the idea of creating a workout section entirely and focus our efforts on making the nutrition section better.

Limitations of User-Submitted Data

Inaccuracies

In our application, we allow users to submit data about food items that are publicly-accessible by others.

As such, there is potential for misleading or outright false information to be submitted (for example, a user may record a food item served by a restaurant as having far more calories than it actually has.)

We think there can be potentially 2 ways of solving this:

• As more users visit and record information about the restaurant, it may be the case that the information submitted will converge on the "true" value, thus becoming more accurate over time. In this ideal scenario, we think no action has to be taken on our end.

• We can restrict the system so that only personal-trainers can submit nutritional information about the food items. This may be effective due to the following reasons:

  • Personal-trainers can have professional certifications that allow them to more accurately assess the nutritional value of food items.

  • Personal-trainers have a reputation to uphold, and thus submitting poor nutritional information about food items will have a negative impact on their relationship with clients and prospective clients.

Regarding Incentives

Supported Mobile Devices

Due to constraints on time, we decided to optimise our mobile user-interface for the iPhone 12 Pro (and iPhones with similar screen dimensions.)

Therefore, the mobile interface may not render correctly on unsupported devices.