Cooking ideas, cooking shopping, in one app.
Sajiloka is an online groceries mobile app platform that provides cook packages and recipes — designed end-to-end using the Lean UX approach, from user research to high-fidelity UI and usability testing.
Sajiloka is an online groceries mobile app platform that provides cook packages and recipes, designed to serve Home Cooks who want to cook at home but face barriers around knowing what to cook, how to buy ingredients, and how to follow a recipe.
During the pandemic, many food stalls were closed due to operational time restrictions. This condition caused people to need to cook at home themselves. However, there were several obstacles experienced by Home Cooks that made starting to cook at home difficult.
"Home Cooks who want to cook independently face multiple simultaneous barriers — they don't know what to cook, can't find all ingredients in one place, and lack a reliable step-by-step cooking guide."
Before forming assumptions, the team conducted problem validation interviews with various Home Cooks including students, housewives, and employees. The rule: a problem is valid if at least ten users feel the same problem.
Using the Lean UX (2016) approach, I started by declaring assumptions about the users, their problems, and the solutions that might address those problems. Even though we start with assumptions, users are still involved at the problem observation stage.
Lives alone in a boarding house, cooks to learn and save money, often cooks with boarding house friends.
Framed using the Lean UX format: "We have encountered that USER has PROBLEM, HOW MIGHT WE ___ with this FEATURE so that user can achieve this OUTCOME."
| ID | Problem | How Might We | Feature | Outcome |
|---|---|---|---|---|
| H1 | Confused about what to cook | Help Home Cooks find a cooking idea | Knowing customer favourite's dish | Get the dish ideas |
| H2 | Didn't have time for a grocery shop | Simplify grocery shopping process | Straight forward order flow and flexible order | Flexible order at anytime anywhere |
| H3 | It's hard to buy ingredients separately | Simplify the cooking process | Provide ready-to-cook packages | Reducing cooking processing time |
| H4 | Didn't know how to cook | Help Home Cooks to serve the dish | Provide cooking guide with text and media (image/video) | Serve the dish |
I used the Lean UX (2016) approach for solving this problem — creating a product as fast as possible and validating to market as soon as possible by making the MVP. The team focused only on minimum feature sets that could be made, making the development process more efficient.
Based on the proposed solution, I designed a simple user flow divided into three domains — Authentication, Exploration, and Order — each serving a distinct phase of the user journey from onboarding to completing a purchase.
Before moving to high-fidelity screens, wireframes were built to quickly test layout assumptions across the Exploration Flow — covering the home page, search, product detail, and cooking guide screens.
There are two iteration design cycles in the MVP making process. These changes were caused by improvement on the design system. The design system helps maintain product and brand design consistency across all screens.
Open Sans was chosen because it gives a minimalist look and is easy to read.
The MVP was brought to life with high-fidelity screens across three key flows — Authentication, Exploration, and Order — each reflecting the finalized design system.
"The Exploration screens feature information banners for promotions, a time-based filter to choose cooking packages, and infinite scrolling of product cards displaying servings, difficulty level, and processing time."
Various test task scenarios were prepared according to the needs of the testing tool, Maze. User research involved users who matched the user persona. The study obtained three quantitative findings: Effectiveness, Efficiency, and Satisfaction.
| Task | Description | Expected Result |
|---|---|---|
| T1 — Search Product | Search for a product named "Balinese Chicken" then look at the product. | Users find and open the product detail page for "Balinese spiced chicken" dish. |
| T2 — How to Cook | From the product detail page, open the "how to cook" tab for "Balinese spiced chicken." | Users find the "how to cook" tab. |
| T3 — Buy Product | Buy "Balinese spiced chicken" — explain what you should do to buy this product. | User understands how to buy a product by pressing a CTA button. |
| T4 — Checkout | Checkout with your delivery location, "Gosend" as courier, and "Mandiri Virtual Account" as payment. | User sets the shipping address, courier service, and payment method. |
This project helped me learn more about the process of a Lean UX framework — working fast, validating early, and iterating based on real user feedback rather than assumptions alone. It reinforced the value of collaborative design, where every team member contributes to a shared understanding of the product.
I also deepened my ability to do better visuals with material design guidelines, by creating a small component library that ensured consistency across all screens. Most importantly, I learned how to empathize with users in a better way — not just understanding their problems on paper, but designing for the real friction they face in everyday cooking.
"The project helped me to learn more about the process of a Lean UX framework. Learned to do better visuals with the material design guidelines, by creating a small component library. Also learned how to empathize with the users in a better way."