Customer Meeting 2 - bounswe/bounswe2026group9 GitHub Wiki
📅 Date - Time: 18.04.2026 📍 Location: Online ⏳ Duration: ~40 🗣️ Communicator: Can Emir Bora 📝 Note Takers: İbrahim Fırat Yoğurtçu, Muhittin Köybaşı
👥 Participants
| Member | Participated |
|---|---|
| Battal HAZAR | |
| Can Emir BORA | X |
| Mustafa KOYUNCU | |
| Muhittin KÖYBAŞI | X |
| Faik İhsan SÜDÜPAK | X |
| İbrahim Fırat YOĞURTÇU | X |
📋 Agenda
- Get feedback on MVP presentation
- Discuss feature priorities and new directions for the final
- Clarify expectations for the final demo
🗣️ Discussion Notes
MVP Presentation Feedback
The presentation was well-received. The step-by-step event creation timeline was highlighted as a good design choice. The UI was noted as pleasant. However, there is no mock data on the web platform. In the event detail page, the start location is visible but the end location is not shown. Overall feedback was positive.
Community Building (Main Direction)
The customer emphasized that the core focus should be on building a community. The application should connect people who attend similar events — similar to a social/matchmaking approach (e.g., Tinder-like suggestions). An example use case: when a user moves to a new city, the system should recommend events based on their past attendance history to help them integrate into a similar community. Social impact should increase as data accumulates.
Auto Recommendation / Suggested Events
A suggestion mechanism based on common event attendance should be implemented. Users who attended similar events should be able to discover and connect with each other. The system should be able to recommend profiles of similar users.
QR Ticket System
A QR-based invitation/ticket system was discussed where the host scans the QR code at the event entrance. This was considered a valid feature idea.
AI Voice Agent for Event Creation
An AI voice agent for event creation was proposed by the team. The customer's view: the current system already guides users sufficiently through tags and step-by-step flow, so AI voice input is not necessary. Energy should be directed toward community features instead.
Final Demo Expectations
The final demo should present a new scenario — not a repetition of the MVP demo. The scenario should highlight community-related features and any extras added since MVP. There is no need to re-demonstrate MVP features already seen.
Post-Event Review / Rating Expansion
The current rating system (stars only) should be expanded. Possible directions: allow text comments on host profiles, introduce a host leaderboard for trending hosts, allow users to leave feedback on the event itself (not just the host), and enable photo sharing after the event to create a memory/nostalgia feature.
Admin Panel
Not a high priority. The customer suggested that database queries or terminal access can handle most admin needs. If considered, it should be done at the very end without spending significant energy on it.
Report System
Having a basic report review mechanism is acceptable, but a fully built admin panel is not necessary. A simple notification (e.g., email) when a report is submitted could be sufficient.
Host–User Messaging
Direct peer-to-peer messaging between host and attendee was discussed. The customer's view: the comment section under an event is sufficient for most communication needs. If desired, the team can adjust the UI to give a messaging feel without building a full chat system.
NFR / Performance Testing
Measurable constraints (e.g., response within 10 seconds, load within 4 seconds) will be revisited in the coming weeks during the testing and quality assurance phase.
UI / Test Automation
Web and mobile test automation was not implemented for MVP. The customer confirmed this is not a problem. UI testing is inherently difficult and was not required for MVP; even for the final, the approach is uncertain.
Edge Cases
The team should not spend excessive effort on edge cases. Focus should be on adding new features or improving existing ones rather than perfecting edge case handling. If the core flow works, that is sufficient.