Product Review; Heyfood

5 min readAug 29, 2022

Overview

In this review, I conducted research on a food delivery app in Nigeria which is Heyfood. Heyfood is a food delivery app that operates only in Ibadan where you can place order for your food preference from any available vendor on the app. I wanted to know the problems users face when using the app, pain points, needs, and recommend solutions to them. In addition to that, I also did a competitor analysis for other food delivery apps. I carried out a user survey with active users of Heyfood and non users of Heyfood. There are six (6) main problems that I found which includes a real-time tracking feature, chat with vendor feature, review feature, withdraw from wallet feature, additional OTP generating option feature, and theme feature. I then came up with solutions regarding these problems.

Research Plan

Background

Heyfood is a food delivery app that operates only in Ibadan where you can place order for your food preference from any available vendor on the app. Having 10k+ downloads on Google playstore, Heyfood clearly is going to be a successful food delivery app as an app that only operates in Ibadan but the success can even be more if there’s an improvement in the features of the app. Based on the findings I did by reading some of the reviews on Playstore and Apple store as well as responses gathered from a google form I created and Twitter survey that was carried out.

To further understand the user problem and needs when they use the Heyfood app, a competitive analysis was carried out to compare the features of Heyfood with some of its competitors such as Jumia food, Bolt food, and Glovo food which were later used as guides in proffering solutions to the problems of Heyfood identified.

Objective

Understand the user’s pain points when they use Heyfood.
Understand the needs that Heyfood users have that haven’t been fulfilled by Heyfood service.
Understanding the competitors; Jumia food, Bolt food, and Glovo food
Understand the user’s behavior while using the app.

Methodology

Qualitative: Google forms and Twitter posts were used to obtain information about user behavior while using the Heyfood app based on the points from the objectives. A face-to-face interview method was also used to get more information from Heyfood users and its competitors.
Qualitative: Competitor Analysis was used to gain insight from the competitors and compare the Heyfood app to Jumia food, Bolt food, and Glovo food.

User Research

Information was gathered from two types of users- Heyfood users and non-Heyfood users. Heyfood users are the users that fall into one of these categories; Those who have used Heyfood for four times or more in the last one month and those that use Heyfood at least once in a week. Non-Heyfood users are the users that prefer the other competitor apps (Jumia food, Bolt food, and Glovo food). The users had to meet certain criteria as users of Heyfood and Non-users of Heyfood which are:

Located in Nigeria and Ibadan
Men and Women
Age 18–70

User Persona

Problems Identified

Users can’t track their orders in real-time; the user can’t see exactly where their rider is on the map.
The users can’t interact with the vendor in case there is an additional note about their order.
The app only allows users to rate the riders and vendors but there is no room to give reviews about them.
The users of Heyfood cannot withdraw excess funds from their wallet into their bank accounts, they can only use those excess funds to buy more food on the app.
Some users have experienced difficulty in the process of generating OTP during sign up processes.
The app doesn’t give its users the opportunity to change the themes settings i.e to switch between dark mode and light mode.

Prioritization

I introduced the MoSCow prioritization method to manage the solutions being recommended. MoSCoW however is an acronym for Must have, Should have, Could have, and Won’t have. The features that fall under the category of must have are the features that are very important to the success of the product, the features of should have are the ones that are important but not as the must have, the could have features are the features that even without them, the product might still be successful, the won’t have are the ones that are not needed at the moment for the success of the product.