Meet

Reducing waste, building community.

Submitted as Capstone project of Abdullah Youssef for CODE university

Introduction

As part of my bachelor's thesis, I developed this matrix to summarise the challenges and opportunities for community food-sharing initiatives. In this project, I will be exploring different approaches to tackle P2P food-sharing across neighborhoods with a deeper focus on digital solutions.

Introduction

As part of my bachelor's thesis, I developed this matrix to summarise the challenges and opportunities for community food-sharing initiatives. In this project, I will be exploring different approaches to tackle P2P food-sharing across neighborhoods with a deeper focus on digital solutions.

Introduction

As part of my bachelor's thesis, I developed this matrix to summarise the challenges and opportunities for community food-sharing initiatives. In this project, I will be exploring different approaches to tackle P2P food-sharing across neighborhoods with a deeper focus on digital solutions.

Introduction

As part of my bachelor's thesis, I developed this matrix to summarise the challenges and opportunities for community food-sharing initiatives. In this project, I will be exploring different approaches to tackle P2P food-sharing across neighborhoods with a deeper focus on digital solutions.

Research insights

When applying thematic analysis to the primary research data, a few key insights emerged relating to the motivations and barriers for P2P food-sharing. Those insights shape the core principles that any digital or non-digital solution should address in order to address logistical and social challenges facing community food-sharing in Berlin. Therefore, the designed solution should be:

01

Low-friction

Addresses logistical barriers

The solution should take away the friction of arranging a date & time for pickup, questions about packaging and kitchen boxes, and most importantly, make sure items are within walking distance to avoid over-commitment and no-show.

Example:

Common cooking kitchen

Community fridge/space

Someone delivering the food to you?

02

Informing and Transparent

Addresses logistical barriers

The solution should enable users to offer as many details about their listing seamlessly and naturally. Food is a very intimate item for people, so they want to make sure the item they're offering is presented satisfyingly, and the items they're receiving match their dietary preferences and allergy concerns.

Example:

A sticky note with all dietary details

Food with labels and instructions

Someone telling you the ingriedents

03

Inclusive & Community oriented

Addresses social barriers

The solution aims to bridge the social gap and break the ice between neighbors. Therefore, it should reflect the community sense and offer a space that feels safe and humane for people to feel invited to exchange food items and even further bond over it, instead of being a mere transactional process.

Example:

Community dish-parties

utilizing screens in elevators

Stickers/posters in hallways

04

Progressive & Scalable

Addresses social barriers

The solution should adapt to the progressive nature of food-sharing as a trust-based activity that relies on the buildup of interactions and reciprocity. How can the individual build increments of trust from sharing maybe a pack of chips to sharing a loaf of bread to requesting some salt on a Sunday?

Example:

Trust badges and ratings

Airbnb/Couchsurfing trust models

05

Habit building

Addresses social barriers

The solution should focus on building new habits and a culture around the concept of food saving and sharing. Habit building is about repetition and linking of daily activities to new ones. Can we link evening social media scroll with new food-saving habits?

Example:

Streaks concept

Daily reminders

Donating a penny every time food is wasted

Now the goal is to assess which solution, digital or non-digital, can bring most benefits from above while introducing least struggles. To assess that, I conducted an assessment of different solutions based on the criteria above.

Research insights

When applying thematic analysis to the primary research data, a few key insights emerged relating to the motivations and barriers for P2P food-sharing. Those insights shape the core principles that any digital or non-digital solution should address in order to address logistical and social challenges facing community food-sharing in Berlin. Therefore, the designed solution should be:

01

Low-friction

Addresses logistical barriers

The solution should take away the friction of arranging a date & time for pickup, questions about packaging and kitchen boxes, and most importantly, make sure items are within walking distance to avoid over-commitment and no-show.

Example:

Common cooking kitchen

Community fridge/space

Someone delivering the food to you?

02

Informing and Transparent

Addresses logistical barriers

The solution should enable users to offer as many details about their listing seamlessly and naturally. Food is a very intimate item for people, so they want to make sure the item they're offering is presented satisfyingly, and the items they're receiving match their dietary preferences and allergy concerns.

Example:

A sticky note with all dietary details

Food with labels and instructions

Someone telling you the ingriedents

03

Inclusive & Community oriented

Addresses social barriers

The solution aims to bridge the social gap and break the ice between neighbors. Therefore, it should reflect the community sense and offer a space that feels safe and humane for people to feel invited to exchange food items and even further bond over it, instead of being a mere transactional process.

Example:

Community dish-parties

utilizing screens in elevators

Stickers/posters in hallways

04

Progressive & Scalable

Addresses social barriers

The solution should adapt to the progressive nature of food-sharing as a trust-based activity that relies on the buildup of interactions and reciprocity. How can the individual build increments of trust from sharing maybe a pack of chips to sharing a loaf of bread to requesting some salt on a Sunday?

Example:

Trust badges and ratings

Airbnb/Couchsurfing trust models

05

Habit building

Addresses social barriers

The solution should focus on building new habits and a culture around the concept of food saving and sharing. Habit building is about repetition and linking of daily activities to new ones. Can we link evening social media scroll with new food-saving habits?

Example:

Streaks concept

Daily reminders

Donating a penny every time food is wasted

Now the goal is to assess which solution, digital or non-digital, can bring most benefits from above while introducing least struggles. To assess that, I conducted an assessment of different solutions based on the criteria above.

Research insights

When applying thematic analysis to the primary research data, a few key insights emerged relating to the motivations and barriers for P2P food-sharing. Those insights shape the core principles that any digital or non-digital solution should address in order to address logistical and social challenges facing community food-sharing in Berlin. Therefore, the designed solution should be:

01

Low-friction

Addresses logistical barriers

The solution should take away the friction of arranging a date & time for pickup, questions about packaging and kitchen boxes, and most importantly, make sure items are within walking distance to avoid over-commitment and no-show.

Example:

Common cooking kitchen

Community fridge/space

Someone delivering the food to you?

02

Informing and Transparent

Addresses logistical barriers

The solution should enable users to offer as many details about their listing seamlessly and naturally. Food is a very intimate item for people, so they want to make sure the item they're offering is presented satisfyingly, and the items they're receiving match their dietary preferences and allergy concerns.

Example:

A sticky note with all dietary details

Food with labels and instructions

Someone telling you the ingriedents

03

Inclusive & Community oriented

Addresses social barriers

The solution aims to bridge the social gap and break the ice between neighbors. Therefore, it should reflect the community sense and offer a space that feels safe and humane for people to feel invited to exchange food items and even further bond over it, instead of being a mere transactional process.

Example:

Community dish-parties

utilizing screens in elevators

Stickers/posters in hallways

04

Progressive & Scalable

Addresses social barriers

The solution should adapt to the progressive nature of food-sharing as a trust-based activity that relies on the buildup of interactions and reciprocity. How can the individual build increments of trust from sharing maybe a pack of chips to sharing a loaf of bread to requesting some salt on a Sunday?

Example:

Trust badges and ratings

Airbnb/Couchsurfing trust models

05

Habit building

Addresses social barriers

The solution should focus on building new habits and a culture around the concept of food saving and sharing. Habit building is about repetition and linking of daily activities to new ones. Can we link evening social media scroll with new food-saving habits?

Example:

Streaks concept

Daily reminders

Donating a penny every time food is wasted

Now the goal is to assess which solution, digital or non-digital, can bring most benefits from above while introducing least struggles. To assess that, I conducted an assessment of different solutions based on the criteria above.

Research insights

When applying thematic analysis to the primary research data, a few key insights emerged relating to the motivations and barriers for P2P food-sharing. Those insights shape the core principles that any digital or non-digital solution should address in order to address logistical and social challenges facing community food-sharing in Berlin. Therefore, the designed solution should be:

01

Low-friction

Addresses logistical barriers

The solution should take away the friction of arranging a date & time for pickup, questions about packaging and kitchen boxes, and most importantly, make sure items are within walking distance to avoid over-commitment and no-show.

Example:

Common cooking kitchen

Community fridge/space

Someone delivering the food to you?

02

Informing and Transparent

Addresses logistical barriers

The solution should enable users to offer as many details about their listing seamlessly and naturally. Food is a very intimate item for people, so they want to make sure the item they're offering is presented satisfyingly, and the items they're receiving match their dietary preferences and allergy concerns.

Example:

A sticky note with all dietary details

Food with labels and instructions

Someone telling you the ingriedents

03

Inclusive & Community oriented

Addresses social barriers

The solution aims to bridge the social gap and break the ice between neighbors. Therefore, it should reflect the community sense and offer a space that feels safe and humane for people to feel invited to exchange food items and even further bond over it, instead of being a mere transactional process.

Example:

Community dish-parties

utilizing screens in elevators

Stickers/posters in hallways

04

Progressive & Scalable

Addresses social barriers

The solution should adapt to the progressive nature of food-sharing as a trust-based activity that relies on the buildup of interactions and reciprocity. How can the individual build increments of trust from sharing maybe a pack of chips to sharing a loaf of bread to requesting some salt on a Sunday?

Example:

Trust badges and ratings

Airbnb/Couchsurfing trust models

05

Habit building

Addresses social barriers

The solution should focus on building new habits and a culture around the concept of food saving and sharing. Habit building is about repetition and linking of daily activities to new ones. Can we link evening social media scroll with new food-saving habits?

Example:

Streaks concept

Daily reminders

Donating a penny every time food is wasted

Now the goal is to assess which solution, digital or non-digital, can bring most benefits from above while introducing least struggles. To assess that, I conducted an assessment of different solutions based on the criteria above.

Solutions Overview

Community fridge/sharing space

Simple to integrate in daily-life, one-time setup

High cost, requires physical setup

Low-friction

Informing & Transparent

Inclusive & Community oriented

Progressive & Scalable

Habit building

House Group chats

Low-investment, no learning curve

Hard to establish habits, lacks structure

Low-friction

Informing & Transparent

Inclusive & Community oriented

Progressive & Scalable

Habit building

Food-sharing apps*

Easy to adapt and scale, clear focus

Requires digital presence, needs active integration in daily life

Low-friction

Informing & Transparent

Inclusive & Community oriented

Progressive & Scalable

Habit building

*Depending on the specific app, the values of the metrics above can change, so the values are just an indication of the potential of such solution compared to others.

Review of Existing Digital Solutions

Since my project is focused on digital solutions, I started reviewing apps that try to solve the same issue and analysed what works and what doesn't in their user experience.

The focus was on the "Olio" app, as it seems to be addressing a very similar segment and tackling the same problem with the same solution approach.

To develop insights, I conducted a UX audit by downloading the Olio app, taking screenshots, and highlighting what is working well and what seems to be confusing for the user. Additionally, I conducted online research through platform such as Reddit and online blogs where users express their happy moments and pain points with the Olio app.

In addition to Olio, I analysed apps that successfully build habits and social buzz around their experience. I specifically looked at "BeReal" and "Duolingo" as two of the most common apps that have their success hanging on the idea of consistent repeated visits for the app to understand how to engage users on regular basis. I also looked at the "Strava" fitness app, with a focus on the idea of "badges" and "challenges" and their role in keeping users engaged and motivated to achieve their workout goals.

High no-show rate: Consistent complaint among users. Potenially for the wide-range of distance covered.

Too many features: The app offers food and non-food exchange with both free and paid possiblities

Not directly clear what allergies the food could include or whether it's halal, vegan, etc..

OLIO

Strava trophy case for activities and challenges.

BeReal, sending daily notifications for all users to take a photo within a time window.

The famous streaks and streak extension example of Duolingo.

Solutions Overview

Community fridge/sharing space

Simple to integrate in daily-life, one-time setup

High cost, requires physical setup

Low-friction

Informing & Transparent

Inclusive & Community oriented

Progressive & Scalable

Habit building

House Group chats

Low-investment, no learning curve

Hard to establish habits, lacks structure

Low-friction

Informing & Transparent

Inclusive & Community oriented

Progressive & Scalable

Habit building

Food-sharing apps*

Easy to adapt and scale, clear focus

Requires digital presence, needs active integration in daily life

Low-friction

Informing & Transparent

Inclusive & Community oriented

Progressive & Scalable

Habit building

*Depending on the specific app, the values of the metrics above can change, so the values are just an indication of the potential of such solution compared to others.

Review of Existing Digital Solutions

Since my project is focused on digital solutions, I started reviewing apps that try to solve the same issue and analysed what works and what doesn't in their user experience.

The focus was on the "Olio" app, as it seems to be addressing a very similar segment and tackling the same problem with the same solution approach.

To develop insights, I conducted a UX audit by downloading the Olio app, taking screenshots, and highlighting what is working well and what seems to be confusing for the user. Additionally, I conducted online research through platform such as Reddit and online blogs where users express their happy moments and pain points with the Olio app.

In addition to Olio, I analysed apps that successfully build habits and social buzz around their experience. I specifically looked at "BeReal" and "Duolingo" as two of the most common apps that have their success hanging on the idea of consistent repeated visits for the app to understand how to engage users on regular basis. I also looked at the "Strava" fitness app, with a focus on the idea of "badges" and "challenges" and their role in keeping users engaged and motivated to achieve their workout goals.

High no-show rate: Consistent complaint among users. Potenially for the wide-range of distance covered.

Too many features: The app offers food and non-food exchange with both free and paid possiblities

Not directly clear what allergies the food could include or whether it's halal, vegan, etc..

OLIO

Strava trophy case for activities and challenges.

BeReal, sending daily notifications for all users to take a photo within a time window.

The famous streaks and streak extension example of Duolingo.

Solutions Overview

Community fridge/sharing space

Simple to integrate in daily-life, one-time setup

High cost, requires physical setup

Low-friction

Informing & Transparent

Inclusive & Community oriented

Progressive & Scalable

Habit building

House Group chats

Low-investment, no learning curve

Hard to establish habits, lacks structure

Low-friction

Informing & Transparent

Inclusive & Community oriented

Progressive & Scalable

Habit building

Food-sharing apps*

Easy to adapt and scale, clear focus

Requires digital presence, needs active integration in daily life

Low-friction

Informing & Transparent

Inclusive & Community oriented

Progressive & Scalable

Habit building

*Depending on the specific app, the values of the metrics above can change, so the values are just an indication of the potential of such solution compared to others.

Review of Existing Digital Solutions

Since my project is focused on digital solutions, I started reviewing apps that try to solve the same issue and analysed what works and what doesn't in their user experience.

The focus was on the "Olio" app, as it seems to be addressing a very similar segment and tackling the same problem with the same solution approach.

To develop insights, I conducted a UX audit by downloading the Olio app, taking screenshots, and highlighting what is working well and what seems to be confusing for the user. Additionally, I conducted online research through platform such as Reddit and online blogs where users express their happy moments and pain points with the Olio app.

In addition to Olio, I analysed apps that successfully build habits and social buzz around their experience. I specifically looked at "BeReal" and "Duolingo" as two of the most common apps that have their success hanging on the idea of consistent repeated visits for the app to understand how to engage users on regular basis. I also looked at the "Strava" fitness app, with a focus on the idea of "badges" and "challenges" and their role in keeping users engaged and motivated to achieve their workout goals.

High no-show rate: Consistent complaint among users. Potenially for the wide-range of distance covered.

Too many features: The app offers food and non-food exchange with both free and paid possiblities

Not directly clear what allergies the food could include or whether it's halal, vegan, etc..

OLIO

Strava trophy case for activities and challenges.

BeReal, sending daily notifications for all users to take a photo within a time window.

The famous streaks and streak extension example of Duolingo.

Solutions Overview

Community fridge/sharing space

Simple to integrate in daily-life, one-time setup

High cost, requires physical setup

Low-friction

Informing & Transparent

Inclusive & Community oriented

Progressive & Scalable

Habit building

House Group chats

Low-investment, no learning curve

Hard to establish habits, lacks structure

Low-friction

Informing & Transparent

Inclusive & Community oriented

Progressive & Scalable

Habit building

Food-sharing apps*

Easy to adapt and scale, clear focus

Requires digital presence, needs active integration in daily life

Low-friction

Informing & Transparent

Inclusive & Community oriented

Progressive & Scalable

Habit building

*Depending on the specific app, the values of the metrics above can change, so the values are just an indication of the potential of such solution compared to others.

Review of Existing Digital Solutions

Since my project is focused on digital solutions, I started reviewing apps that try to solve the same issue and analysed what works and what doesn't in their user experience.

The focus was on the "Olio" app, as it seems to be addressing a very similar segment and tackling the same problem with the same solution approach.

To develop insights, I conducted a UX audit by downloading the Olio app, taking screenshots, and highlighting what is working well and what seems to be confusing for the user. Additionally, I conducted online research through platform such as Reddit and online blogs where users express their happy moments and pain points with the Olio app.

In addition to Olio, I analysed apps that successfully build habits and social buzz around their experience. I specifically looked at "BeReal" and "Duolingo" as two of the most common apps that have their success hanging on the idea of consistent repeated visits for the app to understand how to engage users on regular basis. I also looked at the "Strava" fitness app, with a focus on the idea of "badges" and "challenges" and their role in keeping users engaged and motivated to achieve their workout goals.

High no-show rate: Consistent complaint among users. Potenially for the wide-range of distance covered.

Too many features: The app offers food and non-food exchange with both free and paid possiblities

Not directly clear what allergies the food could include or whether it's halal, vegan, etc..

OLIO

Strava trophy case for activities and challenges.

BeReal, sending daily notifications for all users to take a photo within a time window.

The famous streaks and streak extension example of Duolingo.

Target audience

Although the app could be used by anyone, there is two main user personas that emerged from primary research.

Paolo

Expat student/young professional

Single (Lives alone)

"I hate wasting any kind of food but it's hard to cook/buy exactly the portions needed for only one person."

Wants & Needs

  • Wants to feel part of a community and make new connections

  • Wants to save food from being wasted

Frustrations

  • Feels anxious to reach out to neighbours

  • Always ends up cooking too much and having leftovers

  • Forgets about items in the fridge

Behaviors & Habits

  • Works partially or fully from home

  • Likes to try new things

  • Uses apps like Too Good To Go

  • Travels abroad 2-3 times a year

Julia

Young mother

Family living setup

"My kids don't like eating leftover food, and I wish there was a convenient way to save the food from waste."

Wants & Needs

  • Wants to better know the neighbors so she can feel safer with her kids going around.

  • Wants to cook different meals everyday without wasting food

Frustrations

  • Always has unused cooking materials

  • Wastes a lot of food in family gatherings

Behaviors & Habits

  • Buys groceries in whole

  • Always has edible leftovers

  • Has a fixed routine for cooking/shopping

Target audience

Although the app could be used by anyone, there is two main user personas that emerged from primary research.

Paolo

Expat student/young professional

Single (Lives alone)

"I hate wasting any kind of food but it's hard to cook/buy exactly the portions needed for only one person."

Wants & Needs

  • Wants to feel part of a community and make new connections

  • Wants to save food from being wasted

Frustrations

  • Feels anxious to reach out to neighbours

  • Always ends up cooking too much and having leftovers

  • Forgets about items in the fridge

Behaviors & Habits

  • Works partially or fully from home

  • Likes to try new things

  • Uses apps like Too Good To Go

  • Travels abroad 2-3 times a year

Julia

Young mother

Family living setup

"My kids don't like eating leftover food, and I wish there was a convenient way to save the food from waste."

Wants & Needs

  • Wants to better know the neighbors so she can feel safer with her kids going around.

  • Wants to cook different meals everyday without wasting food

Frustrations

  • Always has unused cooking materials

  • Wastes a lot of food in family gatherings

Behaviors & Habits

  • Buys groceries in whole

  • Always has edible leftovers

  • Has a fixed routine for cooking/shopping

Target audience

Although the app could be used by anyone, there is two main user personas that emerged from primary research.

Paolo

Expat student/young professional

Single (Lives alone)

"I hate wasting any kind of food but it's hard to cook/buy exactly the portions needed for only one person."

Wants & Needs

  • Wants to feel part of a community and make new connections

  • Wants to save food from being wasted

Frustrations

  • Feels anxious to reach out to neighbours

  • Always ends up cooking too much and having leftovers

  • Forgets about items in the fridge

Behaviors & Habits

  • Works partially or fully from home

  • Likes to try new things

  • Uses apps like Too Good To Go

  • Travels abroad 2-3 times a year

Julia

Young mother

Family living setup

"My kids don't like eating leftover food, and I wish there was a convenient way to save the food from waste."

Wants & Needs

  • Wants to better know the neighbors so she can feel safer with her kids going around.

  • Wants to cook different meals everyday without wasting food

Frustrations

  • Always has unused cooking materials

  • Wastes a lot of food in family gatherings

Behaviors & Habits

  • Buys groceries in whole

  • Always has edible leftovers

  • Has a fixed routine for cooking/shopping

Target audience

Although the app could be used by anyone, there is two main user personas that emerged from primary research.

Paolo

Expat student/young professional

Single (Lives alone)

"I hate wasting any kind of food but it's hard to cook/buy exactly the portions needed for only one person."

Wants & Needs

  • Wants to feel part of a community and make new connections

  • Wants to save food from being wasted

Frustrations

  • Feels anxious to reach out to neighbours

  • Always ends up cooking too much and having leftovers

  • Forgets about items in the fridge

Behaviors & Habits

  • Works partially or fully from home

  • Likes to try new things

  • Uses apps like Too Good To Go

  • Travels abroad 2-3 times a year

Julia

Young mother

Family living setup

"My kids don't like eating leftover food, and I wish there was a convenient way to save the food from waste."

Wants & Needs

  • Wants to better know the neighbors so she can feel safer with her kids going around.

  • Wants to cook different meals everyday without wasting food

Frustrations

  • Always has unused cooking materials

  • Wastes a lot of food in family gatherings

Behaviors & Habits

  • Buys groceries in whole

  • Always has edible leftovers

  • Has a fixed routine for cooking/shopping

User stories

User stories were developed to define the core features of the app.

As a user, I want to easily see listings from other members of the community and make sure it fits my preferences without wasting too much time.

As a user, I want to share food items that I have with pickup details for my community members.

As a user, I want to stay engaged with the app so I can remeber to use it when I need to.

User stories

User stories were developed to define the core features of the app.

As a user, I want to easily see listings from other members of the community and make sure it fits my preferences without wasting too much time.

As a user, I want to share food items that I have with pickup details for my community members.

As a user, I want to stay engaged with the app so I can remeber to use it when I need to.

User stories

User stories were developed to define the core features of the app.

As a user, I want to easily see listings from other members of the community and make sure it fits my preferences without wasting too much time.

As a user, I want to share food items that I have with pickup details for my community members.

As a user, I want to stay engaged with the app so I can remeber to use it when I need to.

User stories

User stories were developed to define the core features of the app.

As a user, I want to easily see listings from other members of the community and make sure it fits my preferences without wasting too much time.

As a user, I want to share food items that I have with pickup details for my community members.

As a user, I want to stay engaged with the app so I can remeber to use it when I need to.

Wireframes

Basic wireframes were designed to plan the main user flow and the rough structre of the main app function.

Wireframes

Basic wireframes were designed to plan the main user flow and the rough structre of the main app function.

Wireframes

Basic wireframes were designed to plan the main user flow and the rough structre of the main app function.

Wireframes

Basic wireframes were designed to plan the main user flow and the rough structre of the main app function.

Component library (Design system lite)

Given the small scale of the project as a prototype and a proof of concept, I only created the necessary components to facilitate testing and rapid screen design.

Component library (Design system lite)

Given the small scale of the project as a prototype and a proof of concept, I only created the necessary components to facilitate testing and rapid screen design.

Component library (Design system lite)

Given the small scale of the project as a prototype and a proof of concept, I only created the necessary components to facilitate testing and rapid screen design.

Component library (Design system lite)

Given the small scale of the project as a prototype and a proof of concept, I only created the necessary components to facilitate testing and rapid screen design.

Building the user interface

Building the user interface

Building the user interface

Building the user interface

User flow #1
(Setup + Picking up an item)

Core concepts tackled:

Low-friction -> Takes 1.28 minutes to arrange pickup

Informing & Transparent -> Clear dietary information and pickup details

Community oriented -> Chat like UI helps users feel as part of a group.

User flow #2
(Offering an item)

Core concepts tackled:

Low-friction

|


1- User defines a window for pickup to avoid extended effort to arrange pickups.

2- It takes 1.13 minutes to post an item.

3- User can easily add allergy and dietary details through tags to avoid additional questions before pickup.

User flow #3
(Streaks and reminders)

Core concepts tackled:

Habit building
One of the core issues tackling this solution is how to keep user engagement and stay in the mind of users so they consider the solution when they face the problem.

|


1- User keeps a streak of zero food waste and gets a daily notification to confirm.

2- This serves as its own feature of reminding people to check their fridge/leftovers, but also opens the window for sharing items through the app.

3- To engage users better, a user can save their streak by sharing an item on the app.

4- This feature opens the space to collecting points and trophies that help with engagement, but also offers an opportunity to exchange points for services through collaborations with private and public initiatives.

Try it yourself!
Clickable Prototype

An Interactive prototype was created for user testing, allowing for quick, unmoderated testing. Feel free

Try it yourself!
Clickable Prototype

An Interactive prototype was created for user testing, allowing for quick, unmoderated testing. Feel free

Try it yourself!
Clickable Prototype

An Interactive prototype was created for user testing, allowing for quick, unmoderated testing. Feel free

Try it yourself!
Clickable Prototype

An Interactive prototype was created for user testing, allowing for quick, unmoderated testing. Feel free

Testing

setup

To test the prototype above, I used an online tool called UXtweak. Using this tool, I created an unmoderated test to verify the two main user flows in the app - namely, sharing food and receiving food.

The session included 2 tasks with follow-up questions to evaluate the ease of completing the task and collect qualitative feedback for the overall user experience.

Task #1

Task description

"Your name is Steve and you live in Klosterstr. 15.
After completing the app onboarding, view community listings and make a reservation for the vegan Lasagna. Arrange pickup today at 7:00pm."

Follow up questions

  • From 1-5, how easy was it to complete the task?

  • Did you feel you had all the infromation needed to pickup the item? (Yes/no with explanation)

  • Do you have any feedback or thoughts you would like to add? (Text field)

Task #2

Task description

"Now it's your turn to offer back to the community :) Assume you got half a can of fava beans, and you want to post about it and add details for pickup and so on."

Follow up questions

  • From 1-5, how easy was it to add your own listing?

  • How often could you use such an app (A scale from once a year to once a week)

  • Would you prefer to use a Whatsapp group or social media group instead of the app, why/why not?

  • Do you have any feedback or thoughts you would like to add? (Text field)

Results

7

Total participants

1.28 min

Average time to complete task #1

1.13 min

Average time to complete task #2

80%

Found it easy to complete the task

Feedback

I am not sure if Olivia's address should be available to anyone planning to reserve the Lasagne. If I am to participate I do not want everyone to see my address. Also is there a chat function? ITwould be nice if I could chat with Olivia if I am going to arrive late for example, especially that she mentioned the pickup is in front of the door. If there were small tags like "vegan" and so on listed on the description of each item in the main community page it would be helpful. I know there are filter tags, but just adding them next to each listed item is even more appealing.

I think it is usefully because it is specialised and organised. I do not want to participate in a FB group listing food because first of all I do not know where the people are or how close/far they live. Also reserving on FB would be inconvenient because you have to message the person next and messenger does not always allow that. Also posts on FB group are not always sorted by date, I do not want a lasagne that was posted one month ago. For me, WhatsApp is more for private chats. I do not like getting into bigger groups with people I don't know.

Very useful as it's designed to make providing all the necessary information very easy and more organized to see.

I have an address but which intercom should I ring when I get there?

Love it!!! And I really love feed view with the posted items, as if it's a conversation.

Testing

setup

To test the prototype above, I used an online tool called UXtweak. Using this tool, I created an unmoderated test to verify the two main user flows in the app - namely, sharing food and receiving food.

The session included 2 tasks with follow-up questions to evaluate the ease of completing the task and collect qualitative feedback for the overall user experience.

Task #1

Task description

"Your name is Steve and you live in Klosterstr. 15.
After completing the app onboarding, view community listings and make a reservation for the vegan Lasagna. Arrange pickup today at 7:00pm."

Follow up questions

  • From 1-5, how easy was it to complete the task?

  • Did you feel you had all the infromation needed to pickup the item? (Yes/no with explanation)

  • Do you have any feedback or thoughts you would like to add? (Text field)

Task #2

Task description

"Now it's your turn to offer back to the community :) Assume you got half a can of fava beans, and you want to post about it and add details for pickup and so on."

Follow up questions

  • From 1-5, how easy was it to add your own listing?

  • How often could you use such an app (A scale from once a year to once a week)

  • Would you prefer to use a Whatsapp group or social media group instead of the app, why/why not?

  • Do you have any feedback or thoughts you would like to add? (Text field)

Results

7

Total participants

1.28 min

Average time to complete task #1

1.13 min

Average time to complete task #2

80%

Found it easy to complete the task

Feedback

I am not sure if Olivia's address should be available to anyone planning to reserve the Lasagne. If I am to participate I do not want everyone to see my address. Also is there a chat function? ITwould be nice if I could chat with Olivia if I am going to arrive late for example, especially that she mentioned the pickup is in front of the door. If there were small tags like "vegan" and so on listed on the description of each item in the main community page it would be helpful. I know there are filter tags, but just adding them next to each listed item is even more appealing.

I think it is usefully because it is specialised and organised. I do not want to participate in a FB group listing food because first of all I do not know where the people are or how close/far they live. Also reserving on FB would be inconvenient because you have to message the person next and messenger does not always allow that. Also posts on FB group are not always sorted by date, I do not want a lasagne that was posted one month ago. For me, WhatsApp is more for private chats. I do not like getting into bigger groups with people I don't know.

Very useful as it's designed to make providing all the necessary information very easy and more organized to see.

I have an address but which intercom should I ring when I get there?

Love it!!! And I really love feed view with the posted items, as if it's a conversation.

Testing

setup

To test the prototype above, I used an online tool called UXtweak. Using this tool, I created an unmoderated test to verify the two main user flows in the app - namely, sharing food and receiving food.

The session included 2 tasks with follow-up questions to evaluate the ease of completing the task and collect qualitative feedback for the overall user experience.

Task #1

Task description

"Your name is Steve and you live in Klosterstr. 15.
After completing the app onboarding, view community listings and make a reservation for the vegan Lasagna. Arrange pickup today at 7:00pm."

Follow up questions

  • From 1-5, how easy was it to complete the task?

  • Did you feel you had all the infromation needed to pickup the item? (Yes/no with explanation)

  • Do you have any feedback or thoughts you would like to add? (Text field)

Task #2

Task description

"Now it's your turn to offer back to the community :) Assume you got half a can of fava beans, and you want to post about it and add details for pickup and so on."

Follow up questions

  • From 1-5, how easy was it to add your own listing?

  • How often could you use such an app (A scale from once a year to once a week)

  • Would you prefer to use a Whatsapp group or social media group instead of the app, why/why not?

  • Do you have any feedback or thoughts you would like to add? (Text field)

Results

7

Total participants

1.28 min

Average time to complete task #1

1.13 min

Average time to complete task #2

80%

Found it easy to complete the task

Feedback

I am not sure if Olivia's address should be available to anyone planning to reserve the Lasagne. If I am to participate I do not want everyone to see my address. Also is there a chat function? ITwould be nice if I could chat with Olivia if I am going to arrive late for example, especially that she mentioned the pickup is in front of the door. If there were small tags like "vegan" and so on listed on the description of each item in the main community page it would be helpful. I know there are filter tags, but just adding them next to each listed item is even more appealing.

I think it is usefully because it is specialised and organised. I do not want to participate in a FB group listing food because first of all I do not know where the people are or how close/far they live. Also reserving on FB would be inconvenient because you have to message the person next and messenger does not always allow that. Also posts on FB group are not always sorted by date, I do not want a lasagne that was posted one month ago. For me, WhatsApp is more for private chats. I do not like getting into bigger groups with people I don't know.

Very useful as it's designed to make providing all the necessary information very easy and more organized to see.

I have an address but which intercom should I ring when I get there?

Love it!!! And I really love feed view with the posted items, as if it's a conversation.

Testing

setup

To test the prototype above, I used an online tool called UXtweak. Using this tool, I created an unmoderated test to verify the two main user flows in the app - namely, sharing food and receiving food.

The session included 2 tasks with follow-up questions to evaluate the ease of completing the task and collect qualitative feedback for the overall user experience.

Task #1

Task description

"Your name is Steve and you live in Klosterstr. 15.
After completing the app onboarding, view community listings and make a reservation for the vegan Lasagna. Arrange pickup today at 7:00pm."

Follow up questions

  • From 1-5, how easy was it to complete the task?

  • Did you feel you had all the infromation needed to pickup the item? (Yes/no with explanation)

  • Do you have any feedback or thoughts you would like to add? (Text field)

Task #2

Task description

"Now it's your turn to offer back to the community :) Assume you got half a can of fava beans, and you want to post about it and add details for pickup and so on."

Follow up questions

  • From 1-5, how easy was it to add your own listing?

  • How often could you use such an app (A scale from once a year to once a week)

  • Would you prefer to use a Whatsapp group or social media group instead of the app, why/why not?

  • Do you have any feedback or thoughts you would like to add? (Text field)

Results

7

Total participants

1.28 min

Average time to complete task #1

1.13 min

Average time to complete task #2

80%

Found it easy to complete the task

Feedback

I am not sure if Olivia's address should be available to anyone planning to reserve the Lasagne. If I am to participate I do not want everyone to see my address. Also is there a chat function? ITwould be nice if I could chat with Olivia if I am going to arrive late for example, especially that she mentioned the pickup is in front of the door. If there were small tags like "vegan" and so on listed on the description of each item in the main community page it would be helpful. I know there are filter tags, but just adding them next to each listed item is even more appealing.

I think it is usefully because it is specialised and organised. I do not want to participate in a FB group listing food because first of all I do not know where the people are or how close/far they live. Also reserving on FB would be inconvenient because you have to message the person next and messenger does not always allow that. Also posts on FB group are not always sorted by date, I do not want a lasagne that was posted one month ago. For me, WhatsApp is more for private chats. I do not like getting into bigger groups with people I don't know.

Very useful as it's designed to make providing all the necessary information very easy and more organized to see.

I have an address but which intercom should I ring when I get there?

Love it!!! And I really love feed view with the posted items, as if it's a conversation.

Based on the feedback,
I made some modifications.

Thanks for your time!