About HomeBite.

HomeBite (www.homebite.com.au) is a start-up which I co-founded. The concept was initially a marketplace having 2 types of users, the sellers (Home Chefs/Cooks/Bakers) and buyers (The eaters); however, there is a pivot in progress. HomeBite will become more like a online order management platform for the sellers.

You can download the app on either Apple App Store or Google Play Store.

The need for an admin console (this case study).

This case study will only cover the addition of Admin console.

Problem statement.

HomeBite as a start-up is gaining traction, more app downloads, new chefs on boarded and transactions are flowing through.

Chef’s are getting in touch with our support team member and they don’t currently have a quick way to identify or assist the chef. Some of the requests are actually straightforward however this requires members of the team to view the database directly which is risky and more time consuming as it sometimes involves a technical team member to assist.

Quantifying the type of support enquiries.

There were 2 digital portals that were part of the project which effectively served 2 sets of users.

Potential features to address enquiries.

After gathering the requirements and admin users needs I began sketching possible solutions to help them perform their role.

Priorities: Admin Portal vs Customer facing features.

Explored and tested alternatives when it came to the home page (dashboard) and navigation. Alternative 3 performed the best overall.

The minimal viable product (MVP) of the admin portal.

As this is an admin portal, we did need to take a minimal approach as the same development team was going to work on the admin portal and the customer portal.

Prototype.

This prototype displays the basic functionality which we were able to target as the MVP of the admin portal.

Figma Prototype