Lab 9: Milestone 3 Demo Preparation

Lab 9: Milestone 3 Demo Preparation

Demo-Data Strategy (Content & Use-Case Alignment)

Overview of Data Requirements

Applications data will be populated before with appropriate posts, challenges, tips, etc. before our presentation. On top of that we will add the data that will be used during the presentations.

User Roles

• We have a user named Meryem who is a person concerned about protecting our environment and an admin.

Pre-Populated State

• Meryem will already have an account before the demo to not waste time with creating it during presentation.
• There will be posts for Meryem to like or dislike and comment on that will demonstrate the community aspects of the app. Also there will be some inadequate tip to show reporting functionality.
• There will be tips for Meryem to interact with.
• There will be challenges for Meryem to participate and progress.
• Leaderboard will be populated.

Realistic Content

None of the data that are mentioned will be unrelated to the topic of the application to demonstrate realistic scenarios. So there won't be any data with names similar to "demo", "test" or random names like "ahdadsj".

Edge Case Data

Demo data will show that we handle edge cases such as "finished challenges" or "a user not being able to join many challenges.

---

Demo Plan (Presentation Flow & Key Scenarios)

User Scenario: End-to-End User Journey & Admin Moderation

This document outlines a comprehensive user scenario demonstrating the usability of the Zero Waste Challenge application for an elderly demographic, as well as the administrative moderation capabilities.

1. User Persona

• Name: Meryem Yılmaz (referred to as "Meryem Teyze")
• Age: 72
• Location: Ankara, Çankaya
• Tech Literacy: Low (Struggles with small text, prone to typing errors)
• Motivation: She hates wastefulness ("Israf") and wants to leave a clean world for her grandchildren.

---

2. Scenario: A Sustainable Day with Meryem Teyze

Phase 1: Inspiration & Interaction (Tips Tab)

Time: 10:00 AM

Meryem Teyze cleans up after a family breakfast where she fried peppers. She opens the app to relax.

1. Navigation: She taps the Tips Tab.
2. View: Instead of confusing categories, she sees a simple "Recent Tips" feed sorted chronologically.
3. The Trigger: She scrolls and stops at a specific tip:

   "Did you know? One liter of waste oil can contaminate 1 million liters of clean water. Collect it in a jar!"

4. Internal Motivation: This reminds her of the used cooking oil she was about to pour away. She decides to save it.
5. Interaction: She wants to save this information, so she taps the Thumbs Up icon (👍) below the tip.

Phase 2: Adding Waste & Error Handling

Time: 10:15 AM

Motivated by the tip, she pours the oil into a jar and wants to log it immediately. She returns to the Home Page.

1. Selection: She goes to the "Add Waste" section and selects Waste Type: "Oil & Fats".
2. The Error (Manual Input):
   • She initially leaves the method as "Enter Grams".
   • She tries to estimate the weight. She intends to type "500" but her hand shakes, and she accidentally types "50000".
   • She taps the Add Waste button.
3. System Response (Handler): The app blocks the input. A warning pop-up appears:

   "⚠️ Warning: You cannot enter more than 5000g. Please check the amount."

4. The Solution (Smart Selection):
   • Meryem Teyze realizes she doesn't know the exact weight anyway.
   • She changes the Measurement Method to "Select by Item".
   • She selects "Jar of Oil (Standard)" from the item list.
5. Success: The app automatically calculates the average weight for the jar. She taps "Add Waste".
6. Feedback: A green checkmark animation appears on the screen (Visual feedback only, no sound plays).

Phase 3: Challenges & Planning

Time: 02:00 PM

Meryem Teyze checks her progress in the competition.

1. Navigation: She goes to the Challenges Tab.
2. Observation: She views her active challenge: "Kitchen Master: Recycle Organic Waste".
3. Planning: She looks at the deadline information. She sees the text "Due Date: 17 Dec 2025".
4. Action: Seeing she has time left, she plans to log her vegetable peels tomorrow.

Phase 4: Community & Reporting (Moderation Flow)

Time: 04:00 PM

She browses the Community tab to feel connected to others.

1. Navigation: She opens the Community Tab.
2. The Conflict: While reading posts, she sees a post by a user named "User123" containing inappropriate language and spam content.
3. User Action: She finds this disturbing. She taps the Options (...) button on the post and selects "Report".
4. System Feedback: The app notifies her: "Report sent to admin for review."

---

3. Admin Scenario: Moderation Loop

Actor: Ali (System Administrator) Time: 04:05 PM

Ali logs into the web-based Admin Panel to maintain community standards.

1. Notification: Ali sees an alert on his dashboard: "1 New Reported Post".
2. Review: He navigates to the Reported Content page.
3. Decision: He views the post reported by Meryem Yılmaz. He confirms it violates community guidelines.
4. Action: Ali clicks the "Delete Post" button.
5. Result: The content is permanently removed from the app database. When Meryem Teyze or any other user refreshes the feed, the post is gone.

---

4. Feature Coverage Matrix

Feature	Usage in Scenario	UI/UX Note
Chronological Tips	Meryem views "Recent Tips" feed.	No complex categories for ease of use.
Social Interaction	Meryem uses Thumbs Up.	Replaces "Heart/Like" for clarity.
Error Handling	Input of 50,000g is blocked.	Prevents unrealistic data entry (>5000g limit).
Select by Item	"Jar of Oil" selected.	Auto-calculates weight, removing the need for a scale.
Add Waste Feedback	Animation plays upon success.	No Sound (Silent feedback).
Challenge Details	User checks Due Date.	Clear visibility for planning.
Reporting System	User reports spam.	Community self-policing tool.
Admin Delete	Admin removes the content.	Backend moderation capability.

• …