Customer Meeting 3 - bounswe/bounswe2026group4 GitHub Wiki
Customer Meeting 3
Date: April 16, 2026 Note Taker: Kemal Mahmutoğulları
Attendees
Aysu Keskin, Sezin Doğan, Mert Eren Kaplan, Ömer Faruk Çelik, Kemal Mahmutoğulları (note-taker), Kutay Eroğlu (customer/instructor)
Discussion
Multiple Stories per Location
- A single location can have multiple stories.
- Aggregation may be approximate/location-based rather than exact coordinates.
Timeline
- Timeline can be a separate page, parallel to the feed and map views.
- May be user-based (places and times the user lived in or was interested in), rather than purely time- or location-based.
- Identified as the most important feature to focus on.
Geolocation
- Using device geolocation was confirmed as a good idea.
Standards
- Standards may be incorporated; the customer will provide recommendations.
Feature Priorities (domain-specific)
Notification > Gamification > Moderation
Feedback
| Area | Feedback |
|---|---|
| Appraise to MVP demo Timekeeper | Congratulations Aysu! |
| Empty state | When no stories exist at a location (e.g. Beykoz), users should understand this immediately with a clear UI signal. |
| Year filter default | Default value of 0 is wrong. Find a statistical sweet spot from the actual data profile; seed data may help. |
| Mock/seed data | Mock data must be realistic and logically consistent. |
| Mobile UI | Story metadata should be more compact on mobile. |
| Story language | Story language should reflect the demographic of the user base. |
| Zoom behaviour | Like Google Maps — more detailed/granular stories appear as the user zooms in. |
Summary
Key priorities going forward: Timeline, Geolocation, and Standards alignment.
Additional Instructor Feedback (Post-Meeting)
After the main customer meeting, we also briefly discussed some additional points with the instructor/customer.
- Stories may not always belong to a single exact location. In real-life scenarios, a story can cover multiple locations or a broader geographic area rather than one precise coordinate.
- Similarly, stories may not always refer to a very specific date or time. Users may describe memories through broader life periods, such as “during my childhood” or “when I lived in this neighborhood.”
- The timeline feature was emphasized again as an important part of the project. It was mentioned that the timeline could be presented in a more visual and engaging way, rather than only as a simple chronological list.
- Time information should be flexible. In some cases, such as earthquake-related stories or historically important events, users may want to provide very precise time information, including hour and minute. In other cases, users may prefer to provide broader time ranges, such as years, decades, or life periods.