UX & Prototyping for iOS and Android


Chef prepared meals delivered. Always dairy and gluten free.


I performed as Lead Product Owner, Lead UX Designer & Prototyper for Powersupply mobile (native).  

Discovery Process

The who, what, why and how.


Before jumping into the design, I used Google Forms to kick off a design experiment. We started by answering:

Who are the primary and secondary users?

What is the human problem to solve?

How do we know we have a problem?

What is the impact of solving this problem?

How do we measure the success (or failure) of having solved this problem?

How do users currently achieve success given their needs?

How do these solutions work for the users benefit? What makes them unique?

How do these solutions fail? (What is our competitive advantage?)





Meet Maria Kang

Maria’s a wife, mom of three and caregiver to her elderly mother

Partime personal trainer who travels between two to three gyms a week

Social media influencer

Conscientiously feeds the family

Our ideal candidate to measure the app’s usefulness and benefit to the other primary users (we would also interview).

Validation driven design.

Putting a scientific method to design in practice. We would interview Maria to learn about her needs for our discovery.

Check it out.


As as person on the go, there isn’t an easy way to:

  • view Powersupply delivery orders for the (upcoming) week(s)

  • modify those orders and their shipping address and/or information pertaining to an order (just in case)

  • see when orders will be or have been delivered

  • update payment information or support multiple payment  methods



I proposed solution that allows:

  • meals to be ordered, monitored and amended without the need of logging into a web browser on the go

  • notifications that alert the user of important events such as delivery or delivery cut off

  • billing / invoicing, support for multi-payments, and an ability to change payment methods


Signals (or Goals)

We know we’re right if Maria can:

  • maintain consistent order accuracy without having to re-order items from the menu

  • receive the correct order in time for their respective delivery

  • have deliveries make it freshly into a storage place before spoilage or potentially theft

  • estimate the cost and maintain an expense record for past, present, and future orders

  • can introduce filtering by dietary preference, calories or other micro factors without friction

Jobs Stories in Place of Personas


Jobs to be done helped shaped the context which would inform the design decisions for Maria and other users on the go.

The typical outline follows the following format:

The role: the primary user

Situation: defined by “when something happens”, it helped us hone in on situations that may impact the user’s motivation

Motivation: defined by “I want or need a way to…”, motivations help us understand the needs of our user based on the situation they may or may not be in

Expected outcome: defined by “So I can…”, this is how or feature should in part function on behalf of the user’s desire

I would then create a spreadsheet matrix for the Jobs to Be Done. Which accompanied the loose scope and feature set.

How I measured design impact

Task-success and adoption are the overlapping metrics I used to measure the design’s impact.

As this product matures, proposed features may be paired with retention, happiness, or engagement metrics.

Design Process

To deliver a high-level prototype, I would primarily use Skectch to design low and high fidelity comps.

Invision was used for rapid prototyping, capturing feedback and iterations.

Navigation & IA

I typically start with the navigation of any application. The navigation plays a critical role in the user’s ability to coherently achieve their goals between the different views or pages.

Specifically to mobile, navigation must be discoverable, accessible, and take little screen real estate.




Rapid Prototyping

Sketch and Invision deliver context and the appropriate feeling for the experience we want to design.

Home or Menu View

Meal Detail View

Orders View

Profile View


A definitive method for learning while doing.

To learn how the product shapes up in the mobile context, I install a click-through build onto my mobile device, while updating comps as I discover opportunities to improve the design.


The native application would be shelved after considering budget and engineering constraints

Feasibility and overall business impact would also play a roll in the implementation of the designs

After listening to investors, branding moved into the priority queue


Closing Remarks

There’s never a perfect scenario

Constraints instigate problem-solving (but not all of them)

A designer’s initiatives are best focused on solutions for the user and business

Never let anything get in the way of your own learning


This is a unique website which will require a more modern browser to work!

Please upgrade today!