MinorProject
TAO YUZE 0366967
https://www.figma.com/board/FrIyz1CqPrgOt09O1Duz6O/MinorProject?t=LX8Hl7C04WfMOVas-1
https://drive.google.com/drive/folders/1-_8PLrRyPCFTL3VlxhkR1k7tGCHr3Sfs?usp=drive_link
Key Findings and User Flow Feedback for the Halal Food Scanner App
This blog summarizes the current interview findings and reflects on how the feedback influenced the user flow of my halal food and medicine identification app. The project focuses on helping Muslim users quickly identify whether a product is halal, non-halal, or contains uncertain risk ingredients.
1. Research Context
The interviews were conducted to understand how Muslim users identify halal and non-halal food in daily life, especially when they are travelling, studying in a different city, or buying packaged products with unclear ingredient labels. The app concept uses camera scanning and database comparison to analyze food or medicine packaging, then presents a result based on halal standards.
The interview participants showed two different but related user needs. One participant expected the app to become a broader halal lifestyle platform, while the other preferred a very minimal tool focused on fast halal verification. These two perspectives helped define the balance between core function and future expansion.
2. Key Findings from the Interviews
The strongest finding is that halal identification is not only a convenience issue. For the target users, halal practice is connected with religious belief, daily trust, and personal decision-making. Therefore, the interface should avoid vague results and must provide clear, respectful, and reliable information.
Ingredient checking is the main current method
Both participants usually rely on ingredient lists to judge whether packaged food is halal. However, many additives and chemical names are difficult for ordinary users to understand. This creates uncertainty because users are not food specialists.
The scan result must be fast and clear
One participant clearly stated that they only need to know whether the item is halal. This means the first result screen should not be overloaded with long explanations. The main status should appear immediately, while details should be expandable.
Regional standards increase credibility
Participants wanted the app to show certification bodies and standards from different regions or countries. This is important because halal interpretation can vary across communities, especially for derivative ingredients or uncertain production sources.
Offline access is valuable for travel
Offline scanning and an offline ingredient database were considered useful, especially in areas with weak network infrastructure. This finding supports a lightweight local database or cached standard references for basic scanning.
Advanced functions should remain secondary
Features such as nutrition tracking, meal pairing, restaurant data, delivery links, history, bookmarks, and community ratings were seen as useful. However, they should not weaken the main scanning experience.
The UI should be simple, clean, and low-conflict
Participants preferred a clean and easy-to-use interface with minimal advertisements and unnecessary information. For controversial ingredients, a structured rating system may be safer than an open argument-based comment system.
3. User Flow Feedback
Based on the interview findings, the user flow should be designed around one central action: scanning. The main path should help users move from camera scanning to result confirmation with the fewest possible steps. Additional information should appear only when users need it.
Revised Main User Flow
| User Flow Area | Feedback | Design Response |
|---|---|---|
| Home Page | The app should not feel like a complicated community platform at first glance. | Place the scan button as the visual center. Keep secondary tabs in the bottom navigation. |
| Scanning Page | Users need a direct way to scan ingredient lists and packaging. | Use a camera-based scanning interface with a simple frame, flash option, and clear instruction text. |
| Result Page | The first result should be fast, clear, and easy to understand. | Use three main result states: Halal, Non-Halal, and Uncertain Risk. Avoid long text before the result. |
| Standard Details | Different regional standards may produce different levels of confidence. | Allow users to open each standard card and view which ingredient caused risk or uncertainty. |
| History Page | History and bookmarks are useful but not the main need. | Keep history as a separate bottom navigation page. Let users revisit previous scans without interrupting scanning. |
| Standards Page | Certification bodies and regional references help build trust. | Create a dedicated standards page where users can browse different halal references by country or region. |
| Profile Page | Personal preferences should support the user without complicating the first-time experience. | Use profile settings for preferred region, offline database downloads, saved items, and language options. |
4. Design Implications
The interviews show that the product should not be designed as a general food app first. Its most important value is trust-based halal identification. Therefore, the minimum viable product should focus on scanning, ingredient recognition, certification reference, and clear result presentation.
Main design principle: The app should answer the user’s most urgent question first: “Can I eat or use this product?” Everything else should support that answer rather than compete with it.
At the same time, the interviews also suggest future expansion opportunities. Nutrition information, meal pairing, halal restaurant search, delivery connection, and community-based reference systems could make the app more useful for daily life. However, these functions should be introduced as optional layers or future versions.
5. Reflection
Through the interviews, I realized that a halal scanning app must balance simplicity and credibility. A very simple app can serve users who only need quick verification, while a more complete ecosystem can support users who want nutrition, travel, restaurant, and community information.
The revised user flow therefore follows a progressive structure: scan first, show the result second, and provide detailed explanations only when needed. This approach reduces cognitive load while still giving users enough information to make their own decision.
My next design step is to refine the result page and make sure each halal standard card clearly explains the reason behind the result. This will help the prototype become more transparent, trustworthy, and suitable for different Muslim users in different regions.
6. Conclusion
In conclusion, the key findings confirm that the app should be built around a strong scanning experience, clear halal status, ingredient-risk explanation, regional certification references, and offline support. The user flow feedback also shows that advanced features should be carefully separated from the core path. A successful design should feel simple at first use, but still provide deeper information when users need it.
评论
发表评论