MVP Demo Plan - bounswe/bounswe2026group4 GitHub Wiki

1. Overview

Project Name:
Local History Story Map

Team Name / Group Number:
Group 4

Demo Date:
08-04-2026

Planned Demo Duration:
8 minutes

Demo Objective:
The objective of this demo is to present a complete and emotionally meaningful end-to-end user journey that reflects the core vision of our project. Rather than presenting isolated features, we aim to demonstrate how the platform preserves local memory by connecting people to places through stories, and how those stories can later be rediscovered by others through map-based exploration.

This demo focuses on one specific location: Eski Çınar Parkı, Kuzguncuk, Üsküdar, İstanbul. Through this scenario, we show how the platform can transform a lost physical place into a living digital memory space. The demo highlights both content contribution on mobile and place-based discovery on the web.

2. Demo Readiness and Setup

2.1 Deployment Status

  • Web Application URL (HTTPS):
    [deployed secure public URL]

  • Mobile Application Demo Method:
    Physical device / emulator

  • Backend/API Status:
    Fully deployed and connected to the live frontend environment

2.2 Presentation Setup

Before the presentation begins, the following conditions will already be prepared:

  • both demo users will already be authenticated,
  • the mobile application will already be open and ready for story submission,
  • the web application will already be open on the map interface,
  • the relevant neighborhood and location data will already exist in the deployed system,
  • historical photographs for the story will already be available on the mobile device,
  • backup tabs and fallback screens will be ready in case of technical issues.

2.3 Demo Principles

To keep the presentation focused and efficient:

  • we will not show login or registration flows,
  • we will not include a separate project introduction segment before the scenario,
  • we will start directly inside the user journey,
  • we will prioritize a realistic and emotionally coherent narrative,
  • we will demonstrate only the most meaningful implemented flows.

3. Demo Narrative Summary

This demo follows two different residents connected through the same location, but from two very different points in time.

The first user is Ayşe Demir, a woman who grew up in Kuzguncuk Neighborhood in Üsküdar, İstanbul. She spent her childhood in a tightly knit community where neighbors knew one another, families gathered frequently, and public places played an essential role in daily life. One of the most meaningful places in her memory is Eski Çınar Parkı. It was not simply a park, but a social and emotional center of the neighborhood. Families met there in the evenings, children played there until sunset, wedding convoys passed through, and community events such as Ramadan gatherings took place there. In Ayşe’s memory, the park represents belonging, continuity, and shared joy. When the park was demolished and replaced by a multi-story residential building, she felt that the neighborhood had lost not only a physical space but also part of its collective memory. She fears that if no one documents these memories, future residents will never know what once existed there. Because of this, she decides to preserve her experience by creating a story on the mobile app and attaching it to the exact location of the former park.

The second user is a woman who has recently moved into the apartment building that now stands where Eski Çınar Parkı once existed. Unlike Ayşe, she has no direct memory of the park and no emotional relationship with the neighborhood’s past. She is new to the area and wants to understand the history of the place she now calls home. Instead of using the platform as a generic content feed, she uses the web map interface to explore her surroundings geographically. As she navigates to her building’s location, she discovers a story pinned to that exact spot. By opening the story, reading Ayşe’s narrative, and viewing the historical photographs, she learns that the land beneath her current home once held an important social space filled with life, celebration, and childhood memory. She is moved by this discovery. What was invisible to her only moments earlier suddenly becomes emotionally real. In response, she likes the story and leaves a comment expressing sadness for what was lost and gratitude for being able to learn the hidden history of the place where she now lives.

This narrative demonstrates the unique value of our project: not only preserving memory, but enabling future rediscovery through location-based storytelling.

4. Demo Structure

Segment Time Presenter Platform Purpose
Story Submission Begins Immediately 0:00–2:40 [Name] Mobile Show Ayşe creating and publishing the story directly
Transition to Discovery 2:40–3:00 [Name] - Shift from the contributor to the discovering resident
Discovery Through Map Interface 3:00–5:40 [Name] Web Show the second user finding the story via the map
Story Interaction 5:40–7:10 [Name] Web Show opening the story, viewing images, liking, and commenting
Closing Wrap-Up 7:10–8:00 [Name] - Summarize what the completed flow demonstrates

5. User Scenarios

5.1 Scenario 1 — Ayşe Preserves the Memory of Eski Çınar Parkı

User: Ayşe Demir
Platform: Mobile
Goal: To document and preserve the memory of a meaningful place that no longer physically exists.

Background

Ayşe Demir is a 35-year-old woman who grew up in Kuzguncuk Neighborhood in Üsküdar, İstanbul. Her childhood was shaped by a strong neighborhood culture in which public space was deeply intertwined with social belonging. For Ayşe, Eski Çınar Parkı was one of the most emotionally important places in the neighborhood. It was where she played as a child, where families gathered in the evenings, and where collective experiences unfolded in visible, shared ways. The demolition of the park and its replacement by a residential building represents, for her, the erasure of a lived and communal past. She is motivated not only by nostalgia, but by a desire to preserve cultural continuity for younger generations and to create a digital space where lost places can still be remembered.

Starting State

Before the demo starts:

  • Ayşe is already authenticated on the mobile application,
  • the mobile story creation flow is ready,
  • her historical photographs are already accessible on the device,
  • the map and story submission features are functional in the live deployed environment.

Flow

  1. Ayşe begins directly in the mobile story creation flow.
  2. She selects the former location of Eski Çınar Parkı on the map.
  3. She enters the story title.
  4. She provides the place name.
  5. She selects the relevant time period.
  6. She writes a narrative describing the role of the park in neighborhood life.
  7. She uploads historical photographs.
  8. She submits the story.
  9. The story becomes publicly visible and is attached to that geographic point.

What This Demonstrates

  • story creation on mobile,
  • map-based location selection,
  • use of title, place name, time, and narrative text,
  • image upload functionality,
  • publishing a story to the live system,
  • associating memory with a precise real-world location.

5.2 Scenario 2 — A New Resident Searches the Neighborhood Through the Web Map Interface

User: Newly moved resident
Platform: Web
Goal: To learn about the history of the neighborhood through place-based discovery.

Background

The second user Öykü recently moved into the apartment building that now stands where Eski Çınar Parkı once existed. Unlike Ayşe, she has no lived memory of the old neighborhood. Her relationship to the place begins in the present: a new apartment, a new area, a new routine. However, she is curious about the neighborhood’s past and wants to understand the place beyond its current physical appearance. The web map interface is especially important in this scenario because it allows her to discover stories geographically rather than abstractly. She is not searching for a random post; she is searching for the memory of the exact place where she lives.

Starting State

Before this part begins:

  • Ayşe’s story is already published,
  • the web application is already open,
  • the map interface is ready,
  • the second user is already in the appropriate browsing state.

Flow

  1. The second user begins directly on the web map interface.
  2. She navigates to her neighborhood using the map.
  3. She zooms into the exact location of her apartment building.
  4. She notices a story pin placed at that location.
  5. She clicks the pin to view the preview.
  6. She opens the full story from the map preview.
  7. She reads the story and views the photographs.
  8. She realizes that the building’s location used to be Eski Çınar Parkı.

What This Demonstrates

  • web map interface,
  • map navigation and location-based exploration,
  • story discovery through a pin,
  • preview-to-story-page transition,
  • place-centered storytelling,
  • historical context revealed through geography.

5.3 Scenario 3 — The User Reacts Through Like and Comment

User: Newly moved resident
Platform: Web
Goal: To respond emotionally after learning the hidden history of her current home.

Background

The second user’s discovery is not purely informational. The story changes how she understands the place she now inhabits. What was previously just an apartment building becomes the site of a lost park, a former center of community life, and a place filled with memory. This emotional shift is important because it shows that the platform does more than store content: it creates meaningful intergenerational and interpersonal connection.

Starting State

The second user is already on Ayşe’s full story page.

Flow

  1. She views the images and narrative.
  2. She clicks the like button.
  3. She writes a comment expressing her feelings.
  4. She submits the comment.
  5. The interaction becomes visible on the story page.

Example Comment

“I recently moved into this building and had no idea that such a meaningful park once stood here. It makes me sad to imagine what was lost, but I’m grateful to learn the hidden history of the place I now call home.”

What This Demonstrates

  • story page engagement,
  • liking functionality,
  • commenting functionality,
  • visible interaction on published stories,
  • emotional connection through local memory.

6. Detailed Demo Script

6.1 Full Timed Script

Time Speaker Live Action Talking Points
0:00–0:20 Ayşe Mobile app already open on story creation flow “We begin directly with a resident who wants to preserve the memory of a place that no longer exists physically.”
0:20–0:50 Ayşe Show story creation form “This user is Ayşe Demir, who grew up in Kuzguncuk Neighborhood in Üsküdar, İstanbul. One of the most meaningful places from her childhood was Eski Çınar Parkı.”
0:50–1:20 Ayşe Select the former park location on the map “That park has now been replaced by a residential building, and she fears that the memories tied to it may disappear over time.”
1:20–1:50 Ayşe Fill in title, place name, and time range “So she creates a story and links it to the exact location where the park once stood.”
1:50–2:20 Ayşe Add written narrative “In her narrative, she explains how the park functioned as a shared social space where people gathered, celebrated, and created memories together.”
2:20–2:40 Ayşe Upload photographs and submit story “She uploads historical photographs and publishes the story so that this memory becomes visible to others.”
2:40–3:00 Ayşe Transition from mobile to web “Now we move to another resident whose connection to the same place begins from the present.”
3:00–3:30 Öykü Web app already open on map interface “This user has recently moved into the building that now stands where the park once existed.”
3:30–4:00 Öykü Navigate the map toward the neighborhood “She wants to understand the history of the neighborhood, so she explores it through the map interface.”
4:00–4:40 Öykü Zoom and pan to the apartment location “She moves to the exact place where she lives and looks for any stories tied to that location.”
4:40–5:10 Öykü Click the pin on the map “There, she notices a story pinned to the same spot as her building.”
5:10–5:40 Öykü Open preview and full story page “She opens the story and discovers that the place where she now lives used to be Eski Çınar Parkı.”
5:40–6:10 Öykü Show photographs and text “Through the photographs and written memory, she sees that this was once a joyful and meaningful neighborhood space.”
6:10–6:40 Öykü Pause on story content “Without the platform, this history would have remained invisible to her.”
6:40–6:55 Öykü Click like button “She responds by liking the story.”
6:55–7:10 Öykü Type and submit comment “She also leaves a comment expressing sadness for what was lost and appreciation for learning this hidden history.”
7:10–7:35 Öykü Show updated interaction state “At this point, we have completed the full flow from preservation to rediscovery to engagement.”
7:35–8:00 Öykü End on story page or map “This is the core value of our MVP: preserving disappearing places and helping people rediscover the layered history of where they live today.”

7. Demo Data Strategy

7.1 User Roles Prepared

  • Ayşe Demir — the contributor who creates and publishes the story
  • New Resident — the user who discovers and interacts with the story

7.2 Pre-populated State

To support a smooth and realistic demo, we will prepare the following in the live deployed environment:

  • Ayşe Demir’s account and the second user’s account will already exist,
  • both users will already be authenticated before their parts begin,
  • the relevant geographic location for Eski Çınar Parkı / the current apartment building will already be mapped,
  • the mobile device will already contain historical photographs for upload,
  • the map interface on the web will already be functional and populated,
  • the story, once submitted, will be visible through the same location on the map.

7.3 Why This Data Was Chosen

This data supports a coherent, realistic, and meaningful user journey. It allows the demo to show not just that features technically exist, but that they solve a specific and human-centered problem: the loss of neighborhood memory when meaningful places disappear physically. The chosen data also creates a strong transition between mobile contribution and web discovery.

7.4 Edge Case / Backup Data

  • a pre-published version of Ayşe’s story will exist in case live story creation fails,
  • a backup web tab may already be centered on the correct location,
  • screenshots or a short backup recording of the mobile flow will be available,
  • a fallback comment may already exist in case live commenting fails.

8. Role Assignments

Responsibility Team Member Description
Mobile Demo Driver Mert Eren Kaplan Performs Ayşe’s story creation flow
Mobile Scenario Narrator Kemal Mahmutoğulları Explains the emotional and contextual meaning throughout the demo
Web Demo Driver Ömer Faruk Çelik Performs the map-based discovery flow on the web
Web Scenario Narrator Sezin Doğan Explains the emotional and contextual meaning throughout the demo
Timekeeper Aysu Keskin Ensures the demo stays within 8 minutes
Note Taker Osman Yusuf Tosun Takes notes of evaluator reactions and feedback
Observer Ahmet Çağdaş Girit Records evaluator reactions and feedback
Observer Oğuz Semih Records evaluator reactions and feedback
Backup Technical Support Aysu Keskin Handles tab switching, reloads, and fallback screens

9. Rehearsal Plan

Before the final demo, the team will rehearse the full 8-minute flow at least once.

Rehearsal Goals

  • ensure that both mobile and web platforms function reliably in the deployed environment,
  • check that the transition between users feels smooth and natural,
  • verify that the map interaction is fast and easy to follow,
  • reduce unnecessary pauses during form filling,
  • make sure the like and comment actions are clearly visible,
  • confirm that the full flow fits within the planned time.

Specific Points to Check

  • whether the mobile story submission can be completed smoothly,
  • whether the location selection is clear to the audience,
  • whether the pin appears or is accessible as expected on the map,
  • whether the second user can discover the story efficiently through the map interface,
  • whether switching speakers or devices causes delay.

10. Backup Plan

If mobile story creation fails

We will continue with a pre-published version of the same story and explicitly state that the story is already available in the deployed environment.

If the web application becomes unstable

We will switch to a backup browser tab or use prepared screenshots / a short recorded walkthrough.

If the map is slow

We will use a pre-positioned backup tab focused on the correct neighborhood and location.

If live commenting fails

We will show a fallback existing comment and continue explaining the intended behavior.

If timing becomes too tight

We will shorten narration during input steps and move directly to the most important screens.

11. Key Message for Evaluators

Our MVP demonstrates that local memory can be preserved even when the physical places tied to that memory disappear. By allowing one user to document a lost place and another user to later rediscover that place through the map interface, the platform turns geography into a bridge between past and present. This is the central value of our project.