Role
User Research & UI Design
Product Owner
Platform & Technologies
iOS, Android, Node.js, React
The current food ordering landscape, in general and particularly in Erbil as Nosh's initial market entrance, suffers from a critical lack of customization options. Existing delivery applications fail to provide a user interface that allows customers to personalize their orders, leading them to resort to direct calls to restaurants. Unfortunately, even this approach is riddled with limitations, as most establishments either lack customization options altogether or rely on their own delivery personnel. When minor modifications are available, communication gaps often result in incorrect orders being delivered.
Introducing a network of food brands that prioritize comprehensive menu customization, all operating from a shared open kitchen. Through our dedicated app, we enable effortless personalization across various culinary genres. To ensure convenient delivery, we integrate the APIs of major delivery apps into our platform, granting customers the freedom to receive their orders through their preferred service. As an initial initiative, we are launching the following brands:
When conducting our competitor analysis, we discovered that local restaurants lacked their own delivery services and fell short on menu customization options for pizza, burgers, subs, and salads. Additionally, gourmet toppings were scarce, primarily limited to dine-in experiences rather than delivery. Instead, we shifted our focus to the two prominent delivery apps in Erbil and the larger region: Talabat and Lezzo. Our analysis centered around evaluating their features and the effectiveness of their UI/UX implementation. Below is a summary of our findings.
Note: The UI/UX ratings are on a scale of 1 (lowest) to 5 (highest) and indicate the quality of the respective app's user interface and user experience for the mentioned features.
Through multiple mind-mapping and brainstorming sessions of the founding team and several stakeholders who were aware of the concept, we explored a number of ideas, not just for the user experience but also for the business case as well. This helped us qualitatively to grasp a better idea of our goals and challenges, as well as serves as a foundation to curate better directed questions during our surveys and user interviews. Due to the visual nature of the app, a mobile-first design approach had to be taken.
Working professionals
Ages 18 - 45
Residing in Erbil who frequently order in their meals either at work or at home
Customers who due to the frequency of their orders and the uncertainty of trying new restaurants, customers crave a trusted establishment(s) that allows them to explore new dishes and combinations with each order.
Efficient delivery to compete with larger competitors and API integration with other apps
Initial user resistance to download an app for only a few restaurants
Visual representation of the customized meal in the smaller app screen relative to website
Limited project budget and timeline
Goal is to create a seamless experience on websites and phones (Apple & Android)
Separate web development for the website and native app development (or using Flutter)
Using FlutterFlow to develop the native outputs and web app with one code base
Utilize a combination of the above options to make sure it is cross platform
We conducted a survey of 30+ potential users of the app, and tried to diversify our participants' demographics - age, occupation, education, residence, lifestyle, marital status, etc. All participants had prior experience ordering food online at least once. Our survey questions revolved both around the digital user experience as well as the business concept of the idea. Here are some key metrics from the survey (multiple choice questions are represented in a bar graph while single-choice questions are represented in a doughnut chart).
How old are you?
do you use the tracking feature for your deliveries?
During what times do you usually order food?
How frequently do you order food on a weekly basis?
Select more than one if it depends on the week
Which delivery app have you used in the past month?
How have you paid for your food delivery in the past?
What device have you used to order your food from?
If you've ever ordered directly some any restaurant, what were the reasons?
To better understand our user needs and reinforce/revisit our assumptions, we came up with a list of questions, and conducted user interviews with 10 sponsored users. Similar to the survey, we attempted to choose our user pool to be from diverse background and demographics. The user questions and key insights gained from the interviews are shared below.
Given the time constraint of the project and the urgent need to show an interactive hi-fi prototype to an investor, we had to get creative with the time in our hands. Therefore, even if it meant extra work later down the line, I created sketches and lo-fi wireframes for only the basic functionality and general template.
Quickly after, we had to put that into creating an interactive prototype. In doing so, I ignored a crucial part of the application such as the UI/UX of the user entry, task flow entry and exit, cart addition efficiency, account, etc. My focus was mostly on designing the customization process of the app.
On a more positive note, having a more polished version of the app, even if not fully complete, helps more when it comes to user testing. Hence, we planned to refine the UI design of overall architecture and user flow in a later iteration after receiving feedback from our sponsored users during testing.
As mentioned, the wireframes were quickly implemented into an interactive UI using Figma and tested by myself very quickly. We knew it wasn't complete, but we had to embraced the situation and reminded ourself that design means iteration.
Of course, I could have simply combined the UI process into one iteration, making a happy perfect scenario. But I believe the story of how something comes about is as important, as is how you adapt to things that come your way. Most of the time, especially in smaller constrained operations, a designer needs to be flexible, break his routine. I believe a great designer makes the process work for him, instead of working for the process.
Similar to the other phases of the project, the branding is an iterative process and I am certain I will make changes to what we got currently, both major ones as well as small tweaks to details.
Since the executive decision was made, and later confirmed during our interviews and brainstorming sessions, to segregate each food category across different restaurant brands, we needed a name for the app/website. The name I came up with for now is Nosh.
In addition to easy spelling and pronunciation (a major factor for the local culture where language barriers exist), Nosh was especially unique since it has its meaning in both English as well as the local Kurdish language. In English, Nosh is a noun meaning food, more commonly in Britain. As a verb, it means to eat food enthusiastically or greedily. In Kurdish, Nosh is a short way of saying "Noshi gyani bet" which translates to Bon Appétit.
I will not go very in-depth into the branding process, as the branding is part of a larger project and I don't want it to be super lengthy. Instead, I will touch on some milestones to arrive to the final logo as well as presenting the final concept for each restaurant.
From the different fonts I experimented with, I decided to go with Newake 400 as it was bold and strong, but its mild rounded corners gave it a friendly approachable vibe. Moreover, its strong structure made it scalable and easy to read even in smaller font sizes, as would be the case of this logo most of the time.
Next, I started experimenting with my second concept, which was a geotag/location mark. Both positions below felt non-geometric and off. I knew I could fix the geometry by adding some slogan as one of the variations and creating other variations, so I let that go for now. Focusing on the logomark, I wasn't happy as well. Just a geotag mark felt too generic, boring and not indicative of the full brand message. It signified the delivery aspect, but nothing about food.
Next, I had this idea to combine both concepts into one, by adding a bite mark inside the geotag and then adding some alt-text under the logo to solve the geometry issue -- and it seemed like something clicked.
As for the color scheme, I went with a black and red against a white background (for digital applications) and kraft beige (for packaging applications). Playing off the word "club", I used some abstract dot pattern (representing disco lights) and round concentric circles (representing a record player).
For the packaging, I went with a negative print idea where the logo and a surround thin circle would effectively "not be printed" inside of the black circle badge -- where instead the contract of the salad would bring out the logo contrast.