Ayo
Selected work

Rootine Culture · 2026

Bringing the taste of home to young Africans in Canada

An iPhone app for finding, cooking and ordering the food of home.

Role
Founder and product designer: research, interaction and visual design, testing
Scope
Research, iOS app, brand, usability testing
Status
In TestFlight
Team
Solo, built with Claude under my direction

Where it started

Arrive in Canada as an international student and one question follows you everywhere: what do I eat? For African students, it is rarely simple. Uber Eats and DoorDash serve everyone, which means the food they grew up on is sometimes hard to find.

The group was also growing fast. Between 2021 and 2023, study permit applications from Africa roughly tripled, from 90,000 to 273,000.1 By fall 2023, close to 72,500 African students were enrolled at Canadian institutions.1 Yet the apps they relied on for food were not built with them in mind.

I did not want to design on assumptions, so I started with a survey of 116 students who identify as African, across Canada, then ran 10 interviews to understand what the numbers could not explain.

01

They cook, and they shop often.

Almost everyone cooks at home, and most shop at least every two weeks. Wanting the food was never the problem.

94%cook at home regularlyof 116 students surveyed across Canada

Insight · Lack of discoveryFinding it was. Most participants struggled to find African restaurants or bulk ordering on existing apps, and the gap showed up in every interview.

02

They shop with a budget.

71% spend $100 to $300 a month on groceries, so every trip has to count.

Rootine Culture
Grocery survey


Monthly grocery spend

116 students across Canada


Under $100
3%
$100 to $200
37%
$200 to $300
34%
$300 and up
26%

Most common$100 to $200

116 responses

Insight · Budget awarenessPrice and bulk buying came up again and again, in the survey and in the interviews. Prices had to be visible, and buying in bulk had to be easy.

03

They trust people, not platforms.

Asked how they choose where to eat, people pointed to friends and family before any app.

Honestly, I would rather order food from a restaurant if I know someone that has tried it and they give me an honest opinion about the place.
Seyi, recent graduate

Insight · Trust through communityFood decisions run on word of mouth. Trust and community had to be built into the product from the start, not added later.

So the app had to do three things: help people find the food, respect their budget, and let the people they trust vouch for it.

My answer was a concept app that connects students to familiar food businesses, makes bulk ordering easy, brings recipes from home into one place and builds community around shared food. I took it as far as a high fidelity prototype and a brand system.

A prototype only tells you what people say they would do. Coming back to it, I wanted to see what they would actually use, so I set out to turn the concept into a working app real people could install.

Why young adults, not students

The first concept was for international students. I widened it to young adults of African origin, for two reasons. International student numbers fell about 29% between 2023/2024 and 2025/2026,2 and the need is the same for anyone building a life far from home. Africa makes up 15.6% of recent immigrants to Canada.3 My testers bear it out: most have lived here 12 to 20 years and still miss the food.

Today the app has four parts.

  • RecipesDishes from across the continent, step by step, with Cook Mode.
  • GroceriesAfrican grocers and supermarkets nearby, nearest first.
  • CateringCaterers for parties and events, with packages you can order in the app.
  • Rootine PlanA meal plan built around the cuisines you love, from tested recipes first.

The first build

The first build went to five people across the Greater Toronto Area, in Mississauga, Markham and North York, through TestFlight. I kept the core and cut the commerce, to learn whether people wanted the app before building checkout.

What went in

  • Recipes, step by step
  • An AI recipe generator
  • Grocers and restaurants nearby
  • Add all to list

What I left out

  • Accounts and sign in
  • A backend
  • Cart and checkout
  • Catering ordersMissed most

Testing then showed that the thing I cut, ordering in the app, was what people missed most. The original research had hinted at it. That tension drives the rest of this story.

Testing

I put the first build in front of five people in one hour sessions, each following the same script: background questions, five live tasks while thinking aloud, then questions about features and price. After each task they rated how easy it was, from 1 to 5.

The five were different in the ways that matter. Names are changed.

  • Funmi, from Lagos, 14 years in Canada. Cooks a fixed weekly plan but visits an African store only once or twice a year.
  • Kola, a passionate home cook. Bulk shops every two weeks at Asian supermarkets because they are cheaper.
  • Lina, from Jordan. Knows African food socially, shops at Loblaws and an Arabic store, and is trying meal prep delivery.
  • Daniel, Nigerian Canadian. Rarely cooks and spends over $200 a month on Uber Eats, but wants to cook to eat better.
  • Zara, a keen foodie. Bulk buys at an African store every two months and learns new dishes on YouTube.

The common thread: the food matters, but finding, planning and getting it is scattered across stores, social media, WhatsApp and phone calls.

How easy each task feltAverage of five testers, from 1 (very hard) to 5 (very easy)
  1. First impressions and onboarding4.6
  2. Find groceries3.8
  3. Cook with AI3.6
  4. Order food for a party3.4
  5. Cook a recipe3.4

Onboarding landed. Two people said the flags and regions made the app feel like theirs straight away. Cooking a recipe and ordering for a party were the hardest, and they were hard for the same reason.

What I found

People had to leave the app to finish what they started. Four of five testers hit it. To order from a caterer they had to phone them. To buy groceries they went to a shop’s website. To see a menu they left for a browser. Every exit was a place to drop off. Asked what would make them miss the app if it disappeared, testers named ordering in it.

Daniel said he would “fully switch” from Uber Eats if the caterers he orders from were in the app.

The other patterns:

  • Add to list confused people (4 of 5). It pulled them off the recipe, added every ingredient instead of only what was missing, and never said which recipe an item was for.
  • Recipes are the weekly habit. Testers ranked recipes first of the four parts (average 1.8 of 4), though every part was someone’s favourite.
  • Stores weren’t sorted by distance (3 of 5), so people guessed which was closest.
  • AI trust is fragile. Kola called its jollof “super close” to the real thing, but a bug that reset the chat and changed the recipe earned a 1 out of 5.
  • Smaller asks (2 of 5 each): search by dish or ingredient, a servings control, swiping between steps with wet hands, and supermarkets as well as African grocers.

I fixed six bugs from these sessions within days, including a chat reset bug.

Leaving the app4 of 5

  • Had to phone the caterer to place an order
  • Went to the shop’s website to buy the groceries
  • Left for a browser just to see a menu
  • “Fully switch” from Uber Eats if my caterers were in here
  • Ordering is what I’d miss if the app disappeared

Add to list4 of 5

  • It took me away from the recipe
  • Added everything, even what I already have
  • Which recipe is this item for?
  • Thought it would order delivery

Finding places3 of 5

  • Which store is closest? I had to guess
  • Show supermarkets too, not just African grocers
  • Let me search by dish or ingredient

Cooking

  • Recipes are the part I’d use every week
  • Let me change the servings
  • Swipe between steps, my hands are wet

Trusting the AI

  • Its jollof is “super close” to the real thing
  • The chat reset and the recipe changed. 1 out of 5

Feels like mine2 of 5

  • The flags and regions made it feel like mine straight away

Paraphrased from session notes, except where quoted

The redesign

Every change traces back to something testers said. The guiding rule: finish everything inside the app.

1. Order without leaving

Every caterer now has Place order: pick packages, choose delivery or pickup and a date, and follow the order live from sent to delivered. A Rootine Runner can shop and deliver groceries too, with a chat and a choice of what happens if something is out of stock. I chose this over linking out to delivery apps, which would have kept sending people away.

2. A shopping list that knows why you need things

Adding to the list now stays on the recipe. Tapping an ingredient marks it Got it, so only what is missing goes on the list. Each item shows which recipe it is for, and the list is grouped by aisle.

Switch between the first build and the redesign to see the difference.

Tap what’s already in your kitchen. Only the rest goes on your list.

Party JollofServes 6 · 8 ingredients
Shopping list

Your list is empty.

In the app, Get ingredients asks how you want them: shop it yourself from a list sorted by aisle, or let a Rootine Runner shop it, with every nearby store priced first.

3. Nearest first, and search everywhere

A postal code or your location sorts every store and caterer nearest first, with the distance on each card. One search on every tab finds dishes, ingredients (including other names, like dodo for plantain), stores and caterers. Supermarkets now sit next to African grocers, with prices.

The map grew with it. What started in Mississauga now covers the wider GTA: nine caterers from Oakville to Pickering, six Naomi African Food Market branches, and four supermarket chains.

4. Cooking that fits real kitchens

Servings chips rescale a recipe for one person or a crowd. In Cook Mode you swipe between steps, and the timer keeps running and notifies you even when you leave the app. And a recipe can come in from anywhere: paste a link from Instagram, TikTok, YouTube or a blog, or snap a cookbook page, and it arrives in the same format, ready for the list and Cook Mode.

5. AI that earns trust

The Rootine Plan asks five quick questions (cuisines, diet, allergies, daily targets, how long you want to cook) and builds a meal plan from tested recipes first. AI only fills the gaps. It came straight from watching one bug cost a tester’s trust.

6. Food is social

One tester asked for community, and it echoed the original research: people trust what their own people recommend. I added a light social layer to test the idea: post the dishes you cook, follow cooks, share lists with friends, and a spice rack that builds your taste profile from what you save. Games and trivia are parked.

Look and feel

The brand is warm and vibrant: deep forest green with a hand drawn food pattern, sunset orange for the main actions, goldenrod and cream, set in Space Grotesk and DM Sans. Flags and greetings from across the continent (Akwaaba, Karibu, Ẹ káàbọ̀, Bienvenue) make it feel like home from the first screen.

Every piece of small text meets WCAG AA contrast, 4.5:1 or better. I made darker shades of the orange and green for text on light backgrounds so the brand colours could stay.

The Rootine Culture app iconApp icon

Palette · tap to copy

  • 12.0:1 with cream
  • 3.7:1 with white, decorative only
  • 6.3:1 with forest
  • 8.2:1 with forest
  • 12.0:1 with forest

Made for small text

  • Emerald for text5.9:1 on the app’s cream, from Emerald at 3.5:1
  • Orange for text5.5:1 on the app’s cream, from Sunset Orange at 2.0:1
Space Grotesk · headlinesCraving that taste of home?
DM Sans · everything elseRecipes, grocers and caterers from across the continent, nearest first.
  • AkwaabaTwi, Ghana
  • KaribuSwahili, East Africa
  • Ẹ káàbọ̀Yoruba, Nigeria
  • BienvenueFrench, West and Central Africa

Feels like home

Cook

Shop

Order

Share

Motion

Motion explains what is happening. It never just decorates, and all of it respects Reduce Motion.

The logo builds itself on launch: the fork rises, the knife swings in, the name slides up.
The welcome sets a table: your flags spring into seats around the plate while the hello cycles through Akwaaba, Karibu and Ẹ káàbọ̀.
Show me around serves the features as courses on a printed menu, starter to dessert, swiped like pages.
While a recipe imports from a link, the app’s own ingredient photos pass through a scanner, so the wait feels like cooking.
Cook Mode puts the step in big type with one big timer, which keeps counting even when you leave the app.

In real life

One short film shows the app where it gets used: on the kitchen counter.

The timer keeps time while you cook. The phone sits on the counter in Cook Mode, counting down one step, while the peppers for the next get sliced beside it.

Why ordering

People would pay for savings, not features. Four of five testers would pay for free delivery, lower fees or discounts, the way a food delivery membership works. None would pay for a recipe app alone. Most put the ceiling at about $10 to $11 a month. Funmi put it plainly: anything is too much “as soon as it hits two digits”.

That pointed the product at ordering, and one tester suggested caterers, not customers, should pay most of it. So the question became how much ordering to build first. I weighed four options.

CChosenOrder requestsOrder and pay in the app; I confirm with two or three caterers by phone or WhatsApp.Keeps people in the app and tests whether they really order, and what they pay, before building more.

Tap a point to compare

Order requests won because they test real behaviour cheaply. The prototype shows what C and D would feel like end to end, so the idea can be tested with caterers before anything heavier is built.

An honest note: demand is still soft. Asked how disappointed they would be if the app disappeared, testers answered 2.5, 3 and 4 out of 5. The redesign targets exactly what they said would change that.

Where it stands

The redesign is built and in TestFlight. Ordering, Runners and the social features are a high fidelity simulation: they work end to end on the phone, with sample people and orders, so the ideas can be tested before a backend exists.

Early signal. I asked two people to try the redesign informally: a check, not a second round of testing. One called it multifunctional and singled out bringing in recipes from a link. The other summed up the whole redesign.

My normal experience is going through multiple food blogs, messy screenshots, the timer set up somewhere else. I like that it was all in one place.

She also liked finding grocers and caterers in the app, “another task eliminated”, and a place to share food: “when I make something I’m proud of, I send it around to the necessary people.” And she raised trust. Without a friend’s recommendation, Google reviews are how she decides on a caterer. That went straight onto the list.

What’s next

  1. A second round of testing with the same script, so the numbers compare, and with East, North and Southern African testers.
  2. Caterer reviews, ideally synced with Google reviews, for the moments a friend has not already vouched for one.
  3. The ordering pilot with two or three caterers, with real payments.
  4. A small backend for accounts, real orders and keeping the AI key off the phone, then the App Store.
  5. One or two more cities, then South Asian and Middle Eastern communities, who share the same problem.

What I learned

The research was right the first time. Leaving ordering out of the first build was a fair call for a pilot, but five people told me in an hour each what 116 survey answers had already hinted. Next time I would test the riskiest assumption first, not the easiest one to build.

Building with AI changed how I work. I could put a real app in people’s hands in weeks instead of a clickable prototype, and watch where it broke. People were not imagining the app; they were using it. That made testing honest, and it made every design decision mine to defend, because every one of them shipped.

And trust is a design material. One bug cost a tester’s faith in the AI. One friend’s recommendation decides which caterer gets the call. Most of the redesign is about earning that trust, screen by screen.

Want to try it?

Rootine Culture is in TestFlight. Ask for an invite and I’ll add you to the next build.

Request to test the app

Opens your email with a note to ayo@prodvent.ca, ready to send.

  1. Immigration, Refugees and Citizenship Canada: French speaking students from Africa, committee briefing, November 2024 (opens in a new tab)
  2. Statistics Canada, The Daily, May 5, 2026: Estimating the international student population in Canada using administrative data (opens in a new tab)
  3. Statistics Canada, The Daily, October 26, 2022: 2021 Census, immigration and ethnocultural diversity (opens in a new tab)

More work