Customer Milestone 1 Report of CMPE 451 Fall 2025 - bounswe/bounswe2025group2 GitHub Wiki

Deliverables

This section compiles all software artifacts produced so far.
Each deliverable must be linked within your repository or wiki (external links are not accepted).

Deliverable Description Link
Revised Software Requirements Specification (SRS) Updated and refined requirements document based on feedback Link to SRS
Revised Software Design (UML Diagrams) Updated design artifacts including class, sequence, and component diagrams Use Case Diagram: Goal Management, Sequence Diagram: Goal Management, Use Case Diagram: Interactive Directory, Use Case Diagram: Claiming Reward through Leaderboard, Sequence Diagram: Claiming Rewards from the Leaderboard, Use Case Diagram : Login & Registration, Sequence Diagram: Login and Registration, Class Diagram
Team Development Policies Communication plan, Git branching/committing policies, and workflow conventions Link to Comm Plan Link to Policies
Project Plan Updated timeline, responsibilities, and upcoming milestones Link to Project Plan
Weekly Reports and Meeting Notes Weekly progress summaries and meeting documentation See the sidebar -->
Milestone Review Reflection on progress, deliverables, and process See Below
Individual Contributions Team member contributions and references See Below
Pre-release Software (v0.x.0-beta) Containerized and deployed version of the software with demo-ready features Link to the release

Milestone Review

Summary of Project Status

The fitness application is currently in a well-developed stage, offering a wide range of features that cover user management, goal tracking, social interaction, and community engagement.

Users can register and log in, view and edit their profiles (including profile photos and bios), and set personalized fitness goals. The app also enables real-time communication through both user-to-user chat and an AI assistant chat, where the AI can access user data such as profiles and goals to provide personalized responses.

The challenge system is functional — coaches can create public challenges, and users can join them, track progress, and view their rankings on the leaderboard.

Additionally, the forum module supports structured discussions, with multiple preset forums containing user-created threads. Each thread supports likes/dislikes, comments, and nested subcomments, all of which can also receive reactions. A notification system is in place to inform users about relevant activities such as comments, goals, and interactions.

Overall, the project’s core functionalities are implemented and stable, with remaining work focused on polishing the experience and extending some systems.

Planned Changes

The next development milestone focuses on expanding the app’s personalization, mentorship, and content management capabilities.

  • Mentor-Mentee System:
    Users will be able to send and receive mentor-mentee requests. Upon acceptance, a mentor-mentee relationship will be established, allowing mentors to assign goals to their mentees and monitor their progress.

  • Daily AI Advice:
    A new home page section will display personalized daily advice generated by the AI based on the user’s profile, goals, and bio information.

  • Forum Report System:
    Users will be able to report inappropriate or problematic content within the forum (threads, comments, or subcomments) for moderation.

  • Search Functionality:
    A global search feature will be implemented, enabling users to find challenges, threads, and other users quickly and efficiently.

  • AI-Generated Goal Descriptions:
    The AI system will generate informative descriptions for each goal or challenge. For example, when a user sets a goal like “100 squats,” the AI will automatically provide context and guidance about the exercise.

Note: We are implementing this feature to include some kind of description for the different exercises. Whether we are going to implement this or not will be decided in the next meeting.

Customer Feedback and Reflections

  • Customer Feedback:

    • The app was considered too community-oriented, resembling a general social platform like Facebook rather than a fitness-focused one. It needs more domain-specific features that directly support user fitness journeys.
    • Reviewers emphasized the lack of standardized exercise descriptions. For example, the use of custom terms like “upsies” (for juggling a ball with one’s feet) caused confusion. A clear, AI-supported exercise description system was recommended.
    • The challenge system was found to be somewhat overwhelming since all challenges are public. A difficulty level and filtering system was suggested to help users find challenges suited to their fitness level.
    • The notification system currently only informs users about updates but does not allow direct navigation to the related content. The teacher requested a system where clicking a notification opens the relevant goal, thread, or challenge directly.
    • The teacher also suggested adding a mechanism to share a challenge or post directly from chat, improving interactivity between features.
    • During the demo, the introduction section was criticized for being static. The team was advised to start future presentations with interactive user scenarios instead of showing a motionless screen.
    • The mobile team was told to justify why they were presenting on mobile and to clarify the reasoning behind the user’s device choice during each scenario.
    • Inconsistent terminology during the demo (e.g., the “upsies” example) was pointed out as confusing; the team was advised to prepare a clear list of fitness terms beforehand.

  • Team Reflections:

    • The team acknowledged that the app currently leans too much toward social interaction. As a result, they decided to add domain-specific mechanisms such as the mentor-mentee system, AI-generated goal descriptions, and daily AI advice to make the app feel more fitness-centered.
    • The team agreed to redesign the challenge list with filtering and difficulty options to make navigation easier and more meaningful for users.
    • For notifications, the next implementation step will include deep-link functionality so that users can open specific content (e.g., a goal, thread, or challenge) directly from a notification.
    • The team plans to integrate content sharing into the chat system, allowing users to send goals, posts, or challenges directly in conversations.
    • Based on demo feedback, the team decided to restructure the presentation flow — skipping static introduction screens, focusing on story-driven usage scenarios, and ensuring both web and mobile teams justify the context of their demos, decide the terminology beforehand.

List and Status of Project Deliverables

Deliverable Status Notes
Revised SRS ✅ Completed Updated with new requirements
Revised UML Design ✅ Completed Sequence diagrams pending
Communication Plan ✅ Completed Updated with new term plans
Git Development Policies ✅ Completed Written & apllied in practice
Project Plan ✅ Completed New issues related to feedback added
Weekly Reports & Meeting Notes ✅ Completed They're uploaded every week
Milestone Review ✅ Completed Available in this report
Individual Contributions ✅ Completed Available in this report
Pre Release version ✅ Completed GenFit Web & APK

Evaluation of Deliverables and Impact on Project Plan

The deliverables of this milestone have significantly advanced the project’s overall maturity, improving both functionality and documentation quality. The completion of the Revised SRS and Project Plan provided a solid and traceable foundation for ongoing implementation, while the UML updates and development policies improved cross-team consistency.

At the beginning of the semester, a major refactoring of both the frontend and mobile applications was conducted. Although this took additional time, it was a crucial investment that resulted in a cleaner architecture, improved maintainability, and a smoother development environment. This refactoring allowed for more efficient debugging, faster feature integration, and better synchronization between teams in later stages.

Deliverables were generally submitted on schedule, though some—particularly UML sequence diagrams—required additional revisions due to evolving architecture and new features like the mentor-mentee system and AI integrations. This delayed some design documentation updates, but did not critically affect implementation thanks to effective communication between backend and frontend teams.

The Customer Meeting was a major driver in reorganizing priorities:

  • It highlighted missing features (e.g., mentor-mentee flow, field specific content, and AI-generated content), which are now explicitly scheduled for the next milestone.
  • The customer feedback integration stage led to restructuring the challenge and leaderboard mechanisms to focus more on fitness relevance rather than social engagement.
  • As a result, the project plan was updated in GitHub Projects, introducing new issues and deadlines targeting personalization, interactivity, and improved domain focus.

The Pre-release software deployment provided critical feedback for UI/UX refinement and technical stability. Having a demo-ready web and mobile version early in the cycle helped identify dependencies between teams (e.g., shared APIs and notification behaviors), which will guide optimization in the next sprint.

Overall, the deliverables allowed the team to:

  • Validate the technical feasibility of major modules (login, forum, chat, notifications).
  • Identify remaining gaps (mentor system, pop-up notifications on mobile, email verification, badge system, AI-supported recommendation systems).
  • Adjust workload distribution—especially between web and mobile—to ensure balanced progress.

In terms of project impact, the milestone confirmed that the system architecture scales well for additional AI-based and mentorship features. The clear definition of pending items also allows the team to shift focus from structural development to refinement, user experience, and performance improvements in the next phase.

Evaluation of Tools and Processes

  • Project management & Communication:
    • What we used:
      • GitHub Projects for planning roadmap and tracking milestone goals.
      • Weekly Google Meet meetings for status updates and planning, plus separate web and mobile team meetings.
      • WhatsApp for fast, day-to-day coordination.
      • Meeting notes in the wiki for Google Meet meeetings.
    • Effectiveness:
      • GitHub Projects gave clear visibility on the fresh web and mobile implementation tasks. Ownership and due dates were explicit enough to hit the Initial milestone.
      • Short Meet calls kept blockers visible and decisions quick. WhatsApp filled gaps between meetings and worked well for urgency.
      • Meeting notes helped us keep the decisions taken during meetings in a persistent place.
    • Pain points:
      • 2 hours spent during lab time can actually be spent as 15-30 minutes online meeting + 1.5 hours of individual/sub-team work.
  • Development:
    • What we used:
      • Feature branches from main with mandatory PRs; merge commits; branches deleted after merge.
      • Free-form branch names; PRs linked to issues; no issue numbers in branch names.
      • Assigned reviewers; no direct pushes to main.
    • Effectiveness:
      • Main stayed stable while web and mobile restarted.
      • Issue and PR templates improved clarity and acceptance criteria tracking.
      • Post-merge branch cleanup kept the repo tidy.
    • Pain points:
      • Free-form branch names reduced discoverability
      • Manual verification in reviews increased reviewer load without automated checks
  • Deployment: (Docker, CI/CD)
    • What we used:
      • Docker for containerizing the application to ensure consistent environments across development and production.
      • GitHub Actions for automating CI/CD workflows — building, testing, and deploying on merges to the main branch.
      • Docker Hub & DigitalOcean for storing container images and hosting the live deployment environment.
    • Effectiveness:
      • Automated deployment greatly reduced manual steps and human error.
      • Continuous integration checks improved code quality before merging.
      • Containerization made the system reproducible and easy to scale or migrate.
    • Pain points:
      • Initial setup of GitHub Actions and environment variables was time-consuming.
      • Docker image build times can occasionally slow down the CI/CD pipeline.
    • Adjustments:
      • Implemented caching in Docker builds to speed up pipelines.
      • Fine-tuned workflow triggers to avoid unnecessary rebuilds.

Requirements Addressed in This Milestone

  • Our main focus was implementing the functional requirements first. So non-functional ones were not a factor in this milestone.
  • Main 1.1.1. Account and Profile requirements are implemented. We still lack mentor functionality and badge functionality.
  • Main 1.1.2. Login and Registration requirements are implemented. We still lack email confirmation functionality.
  • Our mobile lacks forum part of the app.
  • Main 1.1.4. Goals & Rewards requirements are implemented. We lack mentor functionality and goal restarting.
  • Notifications are visible and functional but managing preferences feature is still lacking.
  • 1.1.6. Support and Contact requirements are not implemented.
  • 1.2.1. Account and Profile section lacks true verification. Currently system accepts any file as verification.
  • Main 1.2.2. Goals & Rewards requirements are implemented. We lack badge functionality.
  • 1.2.3. Search and Interactive Directory requirements are not implemented.
  • Main 1.2.4. Challenges and Leaderboards requirements are implemented. We lack badge functionality. Lacking small features will be added in the MVP.
  • Push notifications are lacking in mobile.
1.2.3. Account and Profile Requirements Status
Requirement code Status
1.1.1.1. ✅ Completed
1.1.1.2. ✅ Completed
1.1.1.3. ⚠️ Mentor functionality not implemented
1.1.1.4.1. ⚠️ Mentor functionality not implemented
1.1.1.4.2. ⚠️ Mentor functionality not implemented
1.1.1.4.3. ⚠️ Mentor functionality not implemented
1.1.1.5.1. ⚠️ Badge functionality not implemented
1.1.1.5.2. ✅ Completed
1.1.1.6. ✅ Half-Completed, profile pictures doesn't have an alternative text.
1.1.1.7. ✅ Completed
1.1.1.8. ⚠️ Missing Feature
1.1.1.9. ⚠️ Badge functionality not implemented
1.1.1.10. ⚠️ Missing Feature
1.1.2. Login and Registration Requirements Status
Requirement code Status
1.1.2.1. ✅ Completed
1.1.2.2. ✅ Completed
1.1.2.3. ✅ Completed
1.1.2.4. ⚠️ Email confirmation functionality not implemented
1.1.2.5. ✅ Completed
1.1.2.6. ⚠️ Email confirmation functionality not implemented
1.1.3. Forum Requirements Status

This section is missing in mobile, below table is for web.

Requirement code Status
1.1.3.1. ✅ Completed
1.1.3.2. ✅ Completed
1.1.3.3. ⚠️ Missing Feature
1.1.3.4. ✅ Completed
1.1.3.5. ✅ Completed
1.1.3.6. ⚠️ Missing Feature
1.1.3.7. ✅ Completed
1.1.3.8. ⚠️ Missing Feature
1.1.3.9. ⚠️ Missing Feature
1.1.3.10. ⚠️ Missing Feature
1.1.3.11. ⚠️ Missing Feature
1.1.3.12. ✅ Completed
1.1.3.13. ⚠️ Missing Feature
1.1.3.14. ⚠️ Partially implemented, will be continued
1.1.4. Goals & Rewards Requirements Status
Requirement code Status
1.1.4.1. ✅ Completed
1.1.4.2. ✅ Completed, for all sub-requirements
1.1.4.3. ✅ Completed
1.1.4.4. ✅ Half-Completed, restarting isn't available
1.1.4.5. ✅ Completed
1.1.4.6. ⚠️ Mentor functionality not implemented
1.1.5. Notifications Requirements Status
Requirement code Status
1.1.4.1. ⚠️ Missing feature
1.1.4.2. ✅ Completed, for all sub-requirements
1.2.2. Goals & Rewards Requirements Status
Requirement code Status
1.2.2.1. ⚠️ Badge functionality not implemented
1.2.2.2. ✅ Completed
1.2.2.3. ✅ Completed
1.2.4. Challenges and Leaderboards Requirements Status
Requirement code Status
1.2.4.1. ✅ Completed
1.2.4.2. ✅ Completed
1.2.4.3. ✅ Completed
1.2.4.4. ✅ Completed
1.2.4.5. ⚠️ Missing feature
1.2.4.6. ✅ Completed
1.2.4.7. ⚠️ Missing feature
1.2.4.8. ✅ Completed
1.2.4.9. ✅ Completed
1.2.5. Notifications Requirements Status
Requirement code Status
1.2.5.1. ✅ Completed
1.2.5.2. ⚠️ Missing feature
1.2.5.3. ✅ Completed
1.2.5.4. ✅ Partially implemented
1.2.5.5. ⚠️ Missing feature, badges not implemented
1.2.5.6. ⚠️ Missing feature, mentor feature not implemented
1.2.5.7. ⚠️ Missing feature
1.2.5.8. ⚠️ Missing feature, sending e-mails is not an option without 3rd party providers

Individual Contributions

Each member must complete their own subsection.
Subsections should be ordered alphabetically by surname.

Yusuf Akdoğan

  • Responsibilities:
    Contributed to front-end development, focusing on the forum page implementation, note-taking in team and customer meetings, project documentation, and requirements refinement. Supported the team in planning, reviewing, and communicating project progress with TAs and customers.

  • Main contributions:
    Actively participated in forum page front-end implementation, collaborating with Alperen and completing the assigned tasks. Took notes in multiple team and customer meetings and uploaded them to the wiki. Contributed to updating and refining project requirements, prepared communication plans for the team, and supported discussions on project scope and roadmap.

  • Code-related significant issues / PRs:

    • Created PR #403: "Restructure front forum" (~15–20 hours of work)
    • Reviewed and merged PR #422: Berkay's bug fixes
    • Reviewed issues and PRs related to CI/CD, requirements update, and roadmap updates: #345, #366, #367, #385

  • Non-code-related significant issues:

    • Created and worked on issues #315: Communication Plan, #336: Requirements update, #343: Forum page implementation - front end
    • Took notes and uploaded to wiki for meetings: #373, #395, #411
    • Moderated issue #360: Requirements updates for lab
    • Reviewed description updates for project roadmap: #355

  • Pull requests that you have created, merged, and reviewed:

  • Additional information:

    • Participated in all team meetings and participated customer meetings as note taker.
    • Was tasked with being communicator.
    • Updated project requirements after meetings and collaborated in front-end discussions.
    • Prepared wiki pages, communication plan, and project documentation.
    • Supported team in reviewing other members' work and ensuring project progress was tracked efficiently.

Alperen Akyol

  • Responsibilities: Contributed to front-end development, focusing heavily on the forum page, project organization, demo preparation, and ensuring compliance with accessibility, GDPR, and other standards. Supported team in planning, reviewing, and communicating project progress with TAs and customers.

  • Main contributions: Actively participated in Customer Milestone 1 by dedicating significant effort (~20 hours) to the forum front-end, including restructuring and implementing key functionalities. Also organized wiki and lab notes, implemented notifications page, prepared and supported the demo, and proposed enhancements for project originality and usability.

  • Code-related significant issues:

    • Worked on and merged PR #314: "Copying the project into archive for lab1"
    • Reviewed PR #322: "feat: refactor web frontend"
    • Worked on and merged PR #348: "Notifications page implementation for web"
    • Created PR #403: "Restructure front forum" (~20 hours of work)
    • Reviewed and merged PR #427: "[Restructure front forum](feat: add chat functionality back)"
    • Reviewed and merged PR #441: "fix: address profile pic for chats and inclusive forums"

  • Non-code-related significant issues:

    • Created and worked on issue #317: "Organize Wiki"
    • Created and worked on issue #333: "Add Lab2 Meet Notes"
    • Created and worked on issue #334: "Remove unused branches from cmpe 352"
    • Created and worked on issue #343: "Forum Page Implementation - Front end" (~20 hours of work)
    • Created and worked on issue #360: "Lab 3 Requirements Review"
    • Created issues #371, #372, #380, #383 to ensure HTTPS, RTBF, GDPR, and accessibility standards
    • Created and worked on issues #450, #451, #453 for communication plan, Git policies, and adding new issues per feedback
    • Created future issues #454, #455, #456, #457 for recommender bot, mentor functionality, thread editing/deletion, and goal page improvements

  • Pull requests that you have created, merged, and reviewed:

  • Additional information:

    • Supported lab and customer meetings for demos.
    • Tested front-end functionality and prepared mock data for demos.
    • Proposed mechanisms to make the project more original and standout.
    • Communicated with TA regarding requirement revisions.

Talha Başıbüyük

  • Responsibilities: I was responsible for the mobile front-end, focusing on implementing the Challenge page. I also contributed to planning and project setup, requirements review, issue and PR reviews, lab note-taking, and I attended all scheduled meetings. I helped some of my teammates with technical difficulties they had, even after midnight.

  • Main contributions:

    • Planned milestones with Güney and initialized the GitHub Projects board for tracking the fresh client work.
    • Implemented the Mobile Challenge page: started during 2025-09-29 week, completed before the milestone after initial registration logic issues.
    • Reinstalled and verified the local development environment and participated in mobile team meetings.
    • Reviewed requirements, issues, and PRs, and captured notes during lab.

  • Code-related significant issues:

    • Created and worked on issue: #347: "Mobile Challenge Page" (challenge mobile, ~24 hours)

  • Non-code-related significant issues:

    • Worked on issue #360: "Lab 3 Requirements Review"
    • Created and worked on issue #366: "Performance, Reliability, and Compatibility Requirements Review"
    • Created and worked on issue #411: "Meeting 4 Notes"

  • Reviewed issues:

    • #399: "Readme Update"
    • #395: "Customer Meeting Notes"
    • #382: "Mobile Notifications Page"
    • #414: "Online Backend Integration"
    • #330: "Mobile Goal Page"

  • Pull requests that you have created, merged, and reviewed:

  • Additional information:

    • Actively participated during lab sessions.

Ahmet Burak Çiçek

Berkay Buğra Gök

  • Responsibilities:
    I mainly worked on the front-end and deployment procedures of our app. My tasks included maintaining development consistency, providing the necessary infrastructure, and supporting teammates during implementation.

  • Main contributions:
    I was responsible for the deployment of our web app and for initializing a clean front-end project with shared components and layouts.
    I also:

    • Created Dockerized environments for efficient development.
    • Set up CI/CD workflows using GitHub Actions.
    • Implemented login/registration, main, goals, and chat pages of the application.

Code-related significant issues

Issues implemented or resolved

  • #339: Implemented home and goal pages.
  • #362: Implemented chat page.
  • #321: Implemented login/registration pages and shared components.
  • #345: Added server configuration and deployment automation.
  • #353: Added build checks to deny failing builds.

Pull requests implemented or resolved

  • #322: feat: refactor web frontend (large-scale frontend cleanup).
  • #422: fix: various small issues.
  • #441: fix: address profile pic for chats and inclusive forums.
  • #420: bug fixes.
  • #421: bug fixes.

PRs reviewed

  • #351: Front end challenge page.
  • #349: Profile page implementation for web.
  • #426: Routing from notification to forum.

Non-code-related significant issues

  • #437: Additions for forum inclusivity.
  • #452: Explanation of development environment.
  • #356: Explanation of development pipeline.
  • #354: Clarification of project plan.
  • #367: Revised requirements for accessibility.

Pull requests that you have created, merged, and reviewed

Conflicts:
No major merge conflicts occurred; minor file path and component naming inconsistencies were resolved by rebasing and aligning imports across branches.

Additional information

  • Tested front-end functionality and prepared mock data for demos.
  • Supported lab and customer meetings for demos.
  • Participated in brainstorming sessions to improve project direction.
  • Acted as on-call support, assisting with urgent integration and deployment issues.
  • Helped other teams integrate frontend services with backend APIs.

Ali Ayhan Günder

Responsibilities: Contributed primarily to the mobile front-end development, focusing on the forum page, settings, and notification features. Supported the team in project documentation, weekly planning, reviewing teammates’ work, and ensuring W3C compliance and mobile accessibility standards. Played an active role in milestone preparation, testing, and demo participation.

Main Contributions: Actively participated in Customer Milestone 1, dedicating significant effort (~22–25 hours) to the mobile front-end development. Worked on implementing the Forum Page GUI, Settings, Mentors, and Notification Preferences pages. Contributed to refining the mobile UI/UX, transferring handwritten milestone notes to digital documentation, and creating the Milestone Review Section based on demo feedback. Consistently attended team meetings and labs, provided constructive feedback on peers’ work, and improved project documentation and organization.

Code-Related Significant Issues:

  • Created and worked on #430: “Mobile Forum Page Implementation (W3C standards)” (~10 hours of work)
  • Created and worked on #445: “Transfer handwritten milestone notes to digital format”
  • Created and worked on #462: “Implement Milestone Review Section based on demo feedback”
  • Worked on #384: “Mobile Settings Page (layout and interactions)”
  • Worked on #393: “Mobile Home Page updates (thread feed and UI polish)”
  • Worked on #377: “Mentors UI mobile implementation”
  • Worked on #359: “Identify applicable W3C standards for mobile homepage”
  • Closed #337 and #335: “Frontend README updates and standardization”
  • Worked on #328: “Homepage refactoring for maintainability”

Non-Code-Related Significant Issues:

  • Created #402: “Research strategies for accessibility and inclusivity”
  • Closed #412: “Review roadmap improvements (Güney’s issue)”
  • Created #424: “Notification Preferences Page implementation”
  • Reviewed #461, #434, #450: “Milestone Report, Mobile Bugfix, and Communication Plan”
  • Created #319, #323: “Group Information and Meeting Template Revisions”
  • Participated in #335, #364: “README and Documentation Updates for CMPR 451”
  • Attended and documented Mobile Team Meetings #1–4 and Labs 1–5
  • Transferred and structured milestone meeting notes for the project wiki

Pull Requests Created, Merged, and Reviewed:

  • Created: #446 (Forum Feature with navigation & UI), #433 (Mobile Forum Page & Sidebar), #419 (Settings & Threads fixes), #346 (Home Screen with thread feed), #392 (Settings UI), #338 (README Enhancements)
  • Merged: #392, #338
  • Reviewed: #440 (Mobile Chat bugfix), #434 (Default Profile Picture fix), #450 (Communication Plan), #461 (Milestone Report Review)

No major merge conflicts were encountered during development or review processes.

Additional Information:

  • Supported demo preparation and milestone presentation through documentation updates and UI testing.
  • Tested mobile responsiveness and resolved cross-platform interface inconsistencies.
  • Provided continuous feedback to improve code readability and UI consistency.
  • Helped refine the project roadmap and participated in weekly team and lab discussions.
  • Proposed several improvements to forum structure, navigation flow, and mobile accessibility to ensure a smooth end-user experience.

Abdullah Umut Hamzaoğulları

Doran Pamukçu

Responsibilities

I contributed primarily to the front-end development of the web application. My main responsibilities included implementing new interface components, reviewing code contributions from teammates, and ensuring overall code quality and maintainability. Additionally, I supported documentation efforts and played an active role in team communication and planning, taking notes during meetings and contributing to roadmap discussions.

Main Contributions

At the beginning of the semester, I helped archive the previous project codebase and took part in the refactoring of the front-end and mobile environments, which significantly improved our development workflow.
Later, I implemented the Challenge Page, reviewed multiple issues and pull requests, and participated actively in defining Lab 3 requirements and preparing the milestone demo.
I also helped establish new standards for frontend contributions and acted as the web speaker for the milestone demo, preparing the talking points and scenario.
Toward the milestone period, I took responsibility for tasks related to the customer milestone report and review updates.

Code-related Significant Issues

  • #340: Challenge page implementation for front-end — designed and implemented the new Challenge Page.
  • #375: Lab3 Requirements Review — initiated and participated in reviewing and clarifying project requirements.
  • #417: Initial version of milestone demo preparation document — prepared the foundation for the demo presentation flow.
  • #447: Creating the template for customer milestone 1 report — assigned to me; prepared the initial template structure for milestone reporting.
  • #459: Update Milestone Review Section — assigned to me; updated and refined the milestone review part in the documentation.

Non-code-related Significant Issues

  • #339: Reviewed the initial implementation of new frontend pages.
  • #415: Reviewed meeting notes for Lab 4 contributions.
  • #410: Participated in defining demo scenarios.
  • #408: Contributed to discussions on inclusive design ideas.
  • #407: Reviewed fixes for homepage dropdown issues.
  • #401: Participated in lecture topic discussions.
  • #453: Add new issues according to the customer feedback — reviewed and contributed to feedback-based issue creation.

Pull Requests

  • Created:
    • #314: Copying the project into archive for Lab 1.
    • #351: Front-end Challenge Page implementation — a major contribution that introduced new components and logic.
  • Merged:
    • #351: Successfully merged after iterative improvements and reviews.
  • Reviewed:
    • #425: Fix profile button functionality.

Additional Information

Throughout the semester, I consistently contributed to improving team coordination and communication. I took meeting notes, helped draft documentation, and supported decisions regarding coding standards and development priorities.
My proactive involvement in demo preparation, milestone documentation, and presentation strengthened our team’s delivery and coherence across web development tasks.

Volkan Bora Seki

  • Responsibilities:
    Worked as the Mobile Developer of the team, primarily responsible for the Goals and Notifications features on the mobile application.
    Led the presentation of the mobile side during customer meetings, representing the progress, challenges, and technical details of the mobile development process.
    Contributed to diagram preparation, bug fixing, and API synchronization tasks between the mobile front-end and back-end services.

  • Main contributions:
    Implemented the Goals and Notifications modules on the mobile app, ensuring full integration with the backend endpoints.
    Moved the notification icon to the top bar for improved user accessibility and layout consistency.
    Updated and reviewed sequence and use case diagrams for the Goal mechanism and Login flow.
    Collaborated in planning demo scenarios, resolving notification conflicts, and preparing milestone deliverables.
    Took active part in customer meetings, explaining the mobile app’s features and workflow.

  • Code-related significant issues / PRs:

    • #431: Goals notifications added (merged ✅, ~15 tasks completed)
    • #444: Moved notification icon to top bar (merged ✅, ~9 tasks completed)
    • #398: Added goals.tsx file (cancelled ❌, changes requested)
    • Related issues:
      • #460: Goal Sequence diagram update
      • #459: Goal feature’s Use Case Diagram Update
      • #443: Notification conflict handle
      • #440: Adjust APIs of goals and notifications before publishing branch

  • Non-code-related significant issues:

    • #446: Sequence diagram review
    • #408: Discuss the inclusive ideas
    • #402: Discuss the topics covered in lecture
    • #397: Providing Weekly Efforts
    • #396: Mobile meeting notes
    • #410: Determine the Demo Scenarios

  • Pull requests that you have created, merged, and reviewed:

  • Additional information:

    • Acted as the mobile side presenter in customer meetings, demonstrating mobile progress and collecting feedback.
    • Coordinated urgent bug fixes and retroactive diagram updates for goal and notification features.
    • Ensured seamless connection between mobile UI and backend APIs before milestone submissions.
    • Supported the team through documentation, meeting notes, and preparation of the demo presentation.

Güney Yüksel

⚠️ **GitHub.com Fallback** ⚠️