Weekly Meeting 6 (25.03.2026) - bounswe/bounswe2026group11 GitHub Wiki

📝 Weekly Meeting 6

  • 📅 Date: 25-03-2026
  • ⏰ Time: 21:30 - 23:00

👥 Participants

Member Participated
Mehmet Kaan Ünsel ✅
Mehmet Akif Yıldırım ✅
Oğuz Özer ✅
Utku Yiğit Demir ❌
Cansu Er ✅
Buğra Keser ✅
Emine Türk ❌
Sevde Pekköse ✅

🎯 Agenda

  1. Discuss Project Structure and shared resources
  2. Define Application Pages and Endpoints
  3. Finalize Authentication Flow and security measures
  4. Specify "Create Event" page requirements
  5. Determine Profile and Admin Panel features

💬 Discussion Summary

  • Project Structure:

    • A new shared directory may be created to house common logic and types used by both the Frontend and Mobile teams.
    • The Registration flow may serve as the initial test case for this shared structure.

  • Authentication & Security:

    • A "Forgot Password" flow will be added to the login process.
    • Security Best Practice: Upon entering an email for password recovery, the system will display a generic confirmation message regardless of whether the email exists in the database. This prevents user enumeration and enhances security.

  • "Create Event" Page Details:

    • Images: Image uploading will be optional for now. A placeholder will be designated, but full implementation is postponed until next week.
    • Location: The app will use a public API to fetch locations based on user input. For the MVP, location type is restricted to point; route selection will be considered post-MVP.
    • DateTime: The end date/time is optional. All timestamps must be sent to the backend as ZonedDateTime.
    • Constraints: Tags are limited to a maximum of 5. Participation constraints (age, gender, capacity, etc.) are optional.

  • Event Interactions:

    • Join Requests: Users can send a join request accompanied by a message. Event states will reflect "Full" or "Successful" join status.
    • Role-Based UI: The event detail screen will differ for the Host and Participant (e.g., different tabs and management tools).

  • Profiles & Admin Panel:

    • Post-Registration: Users will be immediately redirected to a profile setup screen to provide their Name, Bio, and Photo URL.
    • Profile Layout: Divided into "Hosted Events" and "Attended Events." Event listings should be kept separate from the main profile summary.
    • Metrics: A combined "Average Rating" will be displayed, calculated from event ratings and cancellation rates.
    • Navigation: Direct access to other users' profiles is unnecessary; host ratings will be visible directly on the event detail page.
    • Administration: An Admin role and a dedicated Admin Panel will be implemented for platform management.