Customer Insights Report of Milestone 2 Demo - bounswe/bounswe2025group5 GitHub Wiki
Customer Insights Report of Milestone 2 Demo
Customer Feedback:
-
General Interface & UX Positive Reception: The overall "happy" and "familiar" vibe of the interface was well-received. The customer approved of the current direction.
-
Interaction & Engagement
- Comments vs. Challenges: Simply commenting text (e.g., "I'm upset") is not sufficient. Users should have the ability to initiate or open a "challenge" directly through the interaction flows.
- Note: This point is considered resolved as the team had already included specific scripts covering this feature in the planned scenario.
- Data & Categorization (Final Version Requirements)
- Units & Measurement: Ensure all values regarding amount and kilogram are standardized and corrected in the final build.
- Granularity: Item differentiation is crucial. The system must distinguish between sizes (e.g., large plastic vs. small plastic). There needs to be a clear difference between items like a "large washbasin" and a "small cup."
- Impact Visualization
- Equivalency Logic: The environmental impact must be immediately understandable. For example, when recycling a battery, the system should clearly visualize/explain "what this is equivalent to" (e.g., saved X amount of water).
- Activity Stream & Social Features
- Contextual Links: Notifications like "X liked your post" must include the title of the post so it is clickable and context-aware.
- Follower Feed: Users should clearly see shared content/activities from the people they follow.
- Notifications
- Visuals: If the related content has a photo, include a thumbnail in the notification.
- Content Preview: Include a text snippet (e.g., the first three words) in the notification body.
- Engagement: Do not rely solely on the "Date" to drive engagement, as it does not spark curiosity.
Internal Team Feedback:
- The feedback regarding notifications is very clear and guiding. Development on these improvements has already started.
- Distinguishing between items like large and small basins was already a topic under team discussion. Receiving external feedback on this validated our internal concerns.
- There is a specific request/need to allow entering custom amounts in the waste log.
- We aim to refine the usage statistics section to make it more understandable and free of clutter.