• Final SRS: Requirements
• Final Design: Use Case Diagram, Class Diagram, Sequence Diagram
• API Documentation: Swagger API
• Deployed Web App: waste-less.alibartukonca.org
• Mobile Release: Release

By the Milestone 3, the WasteLess platform has matured into a fully functional, deployed final delivery of web and mobile applications. All functional and non-functional requirements defined in the Software Requirements Specification, except some minor ones such as implementing horizontal scalability, have been implemented, tested, and validated. Although there is still room for refinements and improvements, our application is complete and polished and can be considered Finished.

All planned deliverables have been completed and finalized. Design artifacts, implementation, documentation, and testing outputs are aligned with the final system behavior. The backend, web frontend, and mobile application have been deployed successfully. The v1.0.0 release represents a stable and deployable version of the platform.

The users are able to perform all the intended functions through our app such as creating personal waste goals, joining into community challenges, utilizing social side of the application through seeing posts, searching them with a semantic search, commenting to them, Seeing other users' profiles, following them, getting notifications, getting badges about their achievements in the application, and so on. Our final product, WasteLess, provides a platform for users to track their waste and reduce their environmental footprint while educating themself through a forum section to make an impact on protecting the environment. The final demo we took also confirmed that the system meets customer expectations in terms of functionality, usability, and accessibility.

• Completed all remaining functional requirements, including:

  • Standardized challenge units and point-based scoring.
  • Contextualized notifications with meaningful event references.
  • Achievement badges, rewards, and feedback mechanisms.
  • Moderator tools and reporting workflows.

• Accessibility support enhancements and final compliance checks.

• Verified WCAG 2.1 AA alignment for implemented accessibility features.

• Finalized multilingual support and accessibility-aware i18n integration.

• Released stable, production-ready backend, web, and mobile applications.

• Published v1.0.0 as the official release with finalized documentation.

After dicussing and materializing what we have changed throughout our project lifetime we could agree on the following bullet points for our process improvements:

• Feedback-Driven Refinement: Following Milestone 2 demos and customer evaluations, we adopted a tighter and more structured feedback loop. Instead of treating feedback as high-level suggestions, we directly translated concrete usability and feature critiques—such as the need for notification previews, more flexible waste logging and impact visualizations into prioritized development tasks. This shift ensured that Milestone 3 focused on addressing real user pain points identified during demos rather than expanding functionality without clear user value.

• Performance-Centric Refactoring: We shifted our process to prioritize Non-Functional Requirements alongside standard features. Recognized that system "smoothness" is vital for the UX, since only a "working" app is not sufficient. Hence we proactively refactored backend endpoints, database and frontend logic—such as reducing repetitive API calls and embedding data in notifications and switching to Vector-DB to minimize latency and enhance the application's responsiveness.

• Automated Accessibility & Testing: We moved from manual verification to automated tooling, implementing custom static analyzers and expanding Jest unit test coverage. This allowed us to enforce WCAG 2.1 AA standards and logic correctness programmatically, reducing regression risks during the final sprint.

• API-First Collaboration: We standardized our communication via updated Swagger documentation and shared Postman collections. This "contract-first" approach allowed the frontend and mobile teams to implement features in parallel with backend development, significantly reducing integration wait times.

• Containerized Deployment: We matured our DevOps process by utilizing Dockerfiles for both backend deployment and mobile APK generation. This standardization eliminated environment-specific bugs and streamlined the migration to our new production server.

During our final milestone demo, we presented the fully realised WasteLess platform across both web and mobile. The demonstration highlighted not only the core functionality delivered throughout previous milestones such as waste goals, challenge system, and community features but also newer enhancements like post and comment reporting mechanism with moderator page, semantic search with predefined tags, badge system, and assistive technology support, i.e VoiceOver. Customers responded positively to the new features and overall polish of the product. The coherence of our application's features with the zero-waste domain is also praised considerably. The customers were overall satisfied with our final product.

Although the project was successfully finalized and delivered as a stable and feature-complete system, several early-stage decisions could have been handled differently to improve architectural stability, reduce rework, and clarify product semantics. The following points outline concrete areas where earlier alignment and planning would have strengthened the overall development process.

From the start of the project, scalability was treated as a future consideration rather than an architectural constraint. While this approach allowed faster initial development, it also meant that horizontal scalability requirements (e.g., stateless service design, scaling assumptions for storage and traffic) were not explicitly accounted for during early system design.

If scalability boundaries and assumptions had been defined earlier—even without full implementation—the backend architecture could have been structured in a way that would better support future horizontal scaling. This would have reduced architectural uncertainty and limited the need for later reassessment of deployment and infrastructure decisions.

Although accessibility was always a project requirement, many accessibility-related improvements such as comprehensive screen reader support, dynamic accessibility labels, and automated contrast checking were implemented in later milestones.

If accessibility constraints had been fully integrated into UI and component design from the beginning, fewer UI elements would have required refactoring. Early enforcement of accessibility principles during design and component creation would have reduced implementation overhead and ensured more consistent coverage across the application.

During the early phases of the project, API endpoints evolved organically as features were added and refined. While this flexibility supported rapid development, it also led to repeated adjustments on the frontend and mobile sides as endpoint structures changed.

Defining a clear API versioning and evolution strategy at the start—including expectations for backward compatibility and contract stability—could have reduced integration friction and rework. Early use of strict API contracts and mock endpoints would have further improved parallel development across teams.

The gamification approach of the project changed multiple times throughout development, largely due to ambiguity in how mechanics such as challenges, points and progress feedback were intended to function and be perceived by users. In several cases, customers found the mechanics unclear or unintuitive, leading to redesigns and adjustments in later milestones.

This could have been mitigated by establishing a clear and agreed-upon gamification model at the very beginning of the project. Defining the intended style of gamification (e.g., progression-based, competitive, or achievement-driven), its core mechanics, and how it integrates with waste tracking and user motivation would have reduced ambiguity and minimized later revisions. Early validation of this model with customers would have ensured shared understanding and more stable implementation throughout development.

• Completed:

  • 1.1.1 Account Requirements: 1.1.1.1, 1.1.1.2, 1.1.1.3, 1.1.1.4, 1.1.1.5, 1.1.1.6, 1.1.1.7, 1.1.1.8, 1.1.1.9, 1.1.1.10, 1.1.1.11, 1.1.1.12
  • 1.1.2 Waste Tracking Requirements: 1.1.2.1, 1.1.2.2, 1.1.2.3, 1.1.2.4, 1.1.2.5
  • 1.1.3 Gamification and Challenge Requirements: 1.1.3.1, 1.1.3.2
  • 1.1.4 Post Requirements: 1.1.4.1, 1.1.4.2, 1.1.4.3, 1.1.4.4, 1.1.4.5, 1.1.4.6, 1.1.4.7, 1.1.4.8
  • 1.1.5 Incentive, Reward and Feedback Requirements: 1.1.5.1, 1.1.5.2, 1.1.5.3
  • 1.2.1 Performance and Storage: 1.2.1.1, 1.2.1.2
  • 1.2.2 Waste Tracking Requirements (System): 1.2.2.1, 1.2.2.2, 1.2.2.3
  • 1.2.3 Gamification and Incentive Requirements (System): 1.2.3.1, 1.2.3.2, 1.2.3.3, 1.2.3.4
  • 1.2.4 Notification System Requirements: 1.2.4.1, 1.2.4.2, 1.2.4.3, 1.2.4.4
  • 1.2.5 Post Requirements (System): 1.2.5.1, 1.2.5.2, 1.2.5.3, 1.2.5.4
  • 1.2.6 Standardization Requirements: 1.2.6.1, 1.2.6.2
  • 1.2.7 Localization Requirements: 1.2.7.1, 1.2.7.2
  • 2.1.1 Performance Requirements: 2.1.1.1
  • 2.1.2 Usability and Accessibility Requirements: 2.1.2.1, 2.1.2.2, 2.1.2.3, 2.1.2.4, 2.1.2.5, 2.1.2.6, 2.1.2.7, 2.1.2.8, 2.1.2.9
  • 2.1.3 Waste Tracking Requirements (UX): 2.1.3.1, 2.1.3.2
  • 2.3 Security Requirements: 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.3.5, 2.3.6
  • 2.4 Portability & Compatibility Requirements: 2.4.1, 2.4.2, 2.4.3, 2.4.4

• In Progress: * [None]

• Not Started:

  • 2.5 Eco-Requirements: 2.5.1
  • 2.2 Scalability Requirements: 2.2.1
  • 2.4 Portability & Compatibility Requirements: 2.4.4

Swagger API

• Endpoint: POST /api/reports
• Scenario Description: A user reports a post, suspecting that it is a spam
• The Request:

curl -X POST "https://waste-less.alibartukonca.org/api/reports" \
     -H "Authorization: Bearer USER_JWT_TOKEN" \
     -H "Content-Type: application/json" 
     -d '{
        "reporterName": "cengizbilalsari2",
        "description": "Such a bad post",
        "type" : "Spam",
        "contentType":  "Post",
        "objectId": 1
     }' 

• The Response:

{
    "success": true
}

• Endpoint: POST /api/feedback
• Scenario Description: A user gives a positive feedback to the application which can be seen by the moderators
• The Request:

curl -X POST "https://waste-less.alibartukonca.org/api/feedback" \
     -H "Authorization: Bearer USER_JWT_TOKEN" \
     -H "Content-Type: application/json" \
     -d '{
       "content": "Such a good designer",
       "contentType": "Compliment",
       "feedbackerUsername": "Aarslan"
     }'

• The Response:

{
    "feedbackId": 29,
    "feedbackerUsername": "Aarslan",
    "contentType": "Compliment",
    "content": "Such a good designer",
    "createdAt": "2025-12-20T07:43:17.751+00:00"
}

• Endpoint: GET /api/forum/search/semantic?username={username}&query={query}
• Scenario Description: A user makes a search based on waste type.
• The Request:

curl -X GET "https://waste-less.alibartukonca.org/api/forum/search/semantic?username=CuriousBartu&query=Plastic" \
     -H "Authorization: Bearer USER_JWT_TOKEN" \
     -H "Content-Type: application/json" 

• The Response:

[
    {
        "postId": 4,
        "content": "No more paper or plastic cups. From now on, refill and reuse.",
        "createdAt": "2025-10-20T16:51:07.000+00:00",
        "likes": 17,
        "creatorUsername": "alcala.kelsy",
        "photoUrl": "https://waste-less-photo-storage-2.sfo3.digitaloceanspaces.com/post/no_more_plastic.png",
        "comments": 2,
        "liked": true,
        "saved": false,
        "profile_picture": "https://waste-less-photo-storage-2.sfo3.digitaloceanspaces.com/profile/d3ddf72e-3afd-4ae3-99e3-addd077b9063.jpeg"
    },
     ... 
    {
        "postId": 73,
        "content": "Riding green and recycling clean! ?‍♂️ Glass bottles ready to find a new life.",
        "createdAt": "2025-11-25T10:29:41.000+00:00",
        "likes": 25,
        "creatorUsername": "daimar_morreno_",
        "photoUrl": "https://waste-less-photo-storage-2.sfo3.digitaloceanspaces.com/post/01bb0ebc-f5e3-462b-a1bb-20fa09333f42.webp",
        "comments": 1,
        "liked": false,
        "saved": false,
        "profile_picture": "https://waste-less-photo-storage-2.sfo3.digitaloceanspaces.com/profile/7df0b0ed-fb98-4836-9793-94e0ba708d87.webp"
    }
]

• Mobile UI Implementation: repo
• Web UI Implementation: repo

1. Report Form	2. Custom Waste Logging	3. Users Profile	4. Notifications

• For Milestone 3, we started by implementing features that were previously only in a mock state. We implemented the APIs that send the report text to the backend for reporting a post or a comment, and we tested them end to end. We also shipped the custom waste log feature.
• We made visual improvements to the User Profile section.
• In the Notifications section, we implemented a preview of the related post, including the post image and a content snippet. We aldo added new notifications for feedback and reports. Later on under performance improvements, we worked with the backend team to make these API calls more efficient.

5. Challenge Page	6. Adding Logs	7. Profile Page	8. New Settings Button

• Based on the feedback we received in Milestone 2, we updated the Challenge section to support more flexible logging options instead of limiting users to discrete and numeric inputs only.
• We simplified the Profile page design and introduced a priority list for badges, displaying the most important ones directly on the profile.
• Elements such as Edit Profile, Log Out, and Language Toggle were grouped under a single Settings section.

9. Change Password	10. Badges Catalog	11. Badges Description	12. Show My Impact Page

• The Change Password feature has been enabled and is now available to users.
• Badge catalogs and detailed descriptions have been created. Badges are ordered based on their rarity scores to encourage progression.
• In the Show My Impact section, we aimed to introduce a clear benchmark that allows users to understand their environmental impact more effectively. On this page, users can view their individual waste logs over the past five months as historical data. While tracking their personal progress over time, they can also compare their behavior with global, category-wise consumption data. The chart grows along the y-axis because every unit of waste, even if recycled, still represents an environmental burden. Therefore, a reduction in waste over time indicates positive improvement.

1. Report	2. Notifications & Previews

• Reporting functionality was fully integrated into the web UI, enabling users to report posts and comments.
• The Notifications section was extended with new notification types for reports and feedbacks.
• Notifications now shows previews of object like comment, post text or feedback report texts.
• Feedback button is added and it opens up feedback creation dialog with feedback types and text sections.
• A Moderator page was added to support moderation workflows, enabling review and handling of reports.

1. Feedback	2. Moderator Page

• Feedback button is added and it opens up feedback creation dialog with feedback types and text sections.
• A Moderator page was added to support moderation workflows, enabling review and handling of reports.

5. Profile Page with Badges	6. Reset Password	7. Badge Catalog

• The Profile page was redesigned for better placement and to include badges section.
• Password reset functionality was enabled and made accessible through the web UI.
• A dedicated Badge Catalog page was introduced, presenting badges in a clear and organized structure.

8. Challenge Page Grouping	9. Waste Type Search Buttons, search UI update

• The Challenge page was restructured to group challenges with separate sections. Cardss has different designs according to their status. If they are inactive and reached to goal they are faded green, and if they didnt reach they are faded red. If the user is attended to a challenge there is a green ring around that challenge but if the challenge is ended and it didnt reach to goal then the ring is red.
• There are waste type buttons in feed page to initiate search for specific waste types.
• Search active mode is now noticably different to with blue puls animations all around with changed color of glass background, search is auto initiated after certain time, cleaning the search box turns off search mode.

10. Waste Impact

• Waste charts now shows meaningful impact data both for platform and for the specific user.

We had already implemented several accessibility/inclusivity implementations before Milestone 2 such as providing text alternatives for non-text content or maintaining a minimum contrast ratio. For Milestone 3, we focused on delivering a comprehensive and seamless screen reader compatibility, namely VoiceOver for the web and TalkBack for the mobile.

Example use case with TalkBack

In the Explore Screen, the notification list provides a complex set of information (sender, action, time, and read status). To ensure a TalkBack user receives all necessary context in a single announcement, we implemented a dynamic accessibilityLabel in the mobile application. Instead of TalkBack reading isolated text fragments, we programmed the container to announce a synthesized string:

// From explore.tsx: Dynamic label construction for TalkBack
accessibilityLabel={t("notificationItemLabel", {
    status: notif.isRead ? t("read") : t("unread"), // Spoken as "Read" or "Unread".
    message: messageText, // Spoken as the specific notification message (e.g., "Someone liked your post").
    time: timestamp, // Spoken as the relative timestamp (e.g., "2 minutes ago").
    defaultValue: `${notif.isRead ? "Read" : "Unread"}. ${messageText}. ${timestamp}`,
})}
accessibilityHint={t("doubleTapToOpenNotification", {
    defaultValue: "Double tap to open notification", // Added to inform the user that a double-tap will open the post preview.
})}

This approach allows a visually impaired user to navigate the feed efficiently, as the screen reader provides a coherent summary of the notification's state and purpose without requiring the user to explore multiple sub-elements.

In milestone 3, We have mitigated the ethical risks by adding post and comment report functionality and moderators to address reports. This new feature allows users to flag content that violates our community guidelines, such as harassment, misinformation, or other harmful content, and alerts administrators for review and action. By enabling the community to help moderate the platform, we address risks like bullying and abuse.

Other than post and comment report functionality, we haven't included a new feature related to ethical considerations. The application was already brought into a level in terms of conforming ethical principles previously. The application still collects only the minimal data necessary to provide its core functionality, and all data transmission is encrypted both in transit and at rest. We are asking approval of Personal Data Protection Law (KVKK) terms while signing up, and we continue to honor the consent and deletion controls implemented earlier. Further detail about our application's ethical considerations is available in Customer Milestone 2 Report.

Since the design phase of our application, we have aimed to met several guidelines from the WCAG 2.1 guidelines document. Although full coverage was not our aim, we have covered most of the important ones. Here is the summary of all the guidelines in WCAG 2.1 AA included in the v1.0.0 release in a list format with corresponding requirements in the SRS. Except requirements 2.1.2.7 and 2.1.2.8 which are not applicable to the mobile application, all listed requirements are both complied in web and mobile applications.

We have aimed to follow the core recommendations of the W3C ActivityStreams 2.0 standard for activity logging and notifications. Each logged activity consistently includes an @context, a top-level type, structured actor and object entities, and a published timestamp. By using unique identifiers for the objects of logs we can find the exact object with no problem. We also build the logs and notifications so that they all have the same structure.

Throughout the development phases, we have aimed to meet the W3C Internationalization Guidelines and BCP 47 standards. Our v1.0.0 release focuses on providing a robust infrastructure for English and Turkish, both in web and mobile applications. Below is the compliance summary of the functional requirements that we have identified from W3C Internationalization Guidelines and BCP 47 standards, relating to our single internationalization SRS requirement (2.1.2.1). The implementation descriptions cover implementations in both the web and the mobile application. While we achieved full content decoupling and language switching, features such as Right-to-Left (RTL) support and locale-aware numeric formatting were discarded to prioritize core implementation.

For the standards 1.1.1 Non-text Content to 3.2.3 Consistent Navigation, the implementations had been already done before milestone 2. Their detailed analysis including implementation details and links to the relevant development artifacts are provided in related part in the Customer Milestone 2 Report. How our implementation fulfills the requirements was described in detail in this document. The deep dive for the rest of the standards are in the following.

Evidence:

• #743: The issue for the VoiceOver implementation for milestone 3 for both frontend and mobile.
• #765: The PR for the VoiceOver implementation for milestone 3 in mobile.
• #851: The PR for the VoiceOver implementation for milestone 3 in frontend.

Reasoning: We have already did some work on this standard in previous milestone. The details for those implementations are provided in the related part in the Customer Milestone 2 Report. Similar to our work in milestone 2, we have conducted a comprehensive check on all UI components and provided missing ARIA attributes and roles such as aria-label, aria-describedBy, aria-required etc. By providing these attributes, we aimed to achieve a seamless VoiceOver support (or any other assistive technology, we aimed for just one for this project). Thereby, names and roles of components can be programmatically determined as stated in the guideline. We showed the availability of this property by using the VoiceOver with our web application, and presented it in our customer milestone 3 demo presentation. By fulfilling this guideline, we reached a more accessible application for people who use these assistive technologies such as visually impaired people.

Evidence:

• Implementing preview for activity logging
• Profile Picture field for activity logging
• Fixing the comment preview

Reasoning: We introduced a preview field to capture a description of events. This fulfills the standard’s requirement for the summary property, which is intended to provide a human-readable description of an activity. This allows our system to present "human interpretation" data alongside machine-readable JSON-LD.

We added Profile Picture field for performance considerations. By embedding the profile pictures in the notifications, we eliminated many unnecessary requests coming from frontend to load the profile pictures.

• Backend API: HTML Report | XMLs
• Web App: Link to Unit test XML Link to Unit test HTML | Link to e2e XML Link to e2e HTML
• Mobile App: HTML Report | XML Report

• Integration Tests: Postman
• End-to-end (E2E) Tests: Postman
• UI/UX Tests: [Link to source code] FeedbackModal, BadgeUtils, ColorContrast

Coverage: The test suite now provides 100% coverage for the Feedback and Report modules in backend. Specifically, it covers the logic for reporting various content types and ensures the Moderator Dashboard correctly filters solved vs. unsolved reports. Additionally, we have added coverage for the enhanced Notification System, verifying that preview snippets are correctly generated and truncated to 255 characters before being served to the client.

Coverage in mobile team perspective: The current test suite provides comprehensive coverage across the core user journey, spanning from initial authentication and guest access to complex social interactions and environmental goal tracking. By validating the ProfileScreen across 21 distinct scenarios, we have ensured that data-heavy components remain resilient during loading states, API failures, and empty data returns. The inclusion of specialized utility tests for badgeUtils further guarantees that the gamification logic remains consistent regardless of backend naming conventions. Additionally, the coverage of the WasteGoalScreen and ReportModal ensures that both the primary functional features and the community safety tools are verified for logic accuracy and localization support. This multi-layered approach ensures that critical path regressions are caught early, maintaining a stable and accessible experience for both guest and authenticated users.

For Frontend: Unit/Integration (Vitest) Scope: React components, hooks, and utilities (form validation, i18n, layout guards, feed/challenge UI pieces). E2E (Playwright) Scope: Core authenticated journeys and key pages load without errors: login, main page, feed, goals, profile, challenges. Includes challenge attend/leave and goal creation flows; assertions are tolerant of empty data states.

• Bug Detection:
  • 1. During Postman testing of the notification endpoint, we discovered that the "Comment Notification" was pulling the username of the commenter instead of the actual Comment Text for the preview snippet. This would have resulted in confusing notifications for users. We corrected the mapping logic to ensure the preview field accurately reflects the start of the comment.
  • 2. In the mobile team implementation phase our badgeUtils tests caught a critical logic error where badges earned in the system were failing to render their icons. The backend was sending badge identifiers in SNAKE_CASE (e.g., WASTE_WARRIOR), but the frontend asset library was expecting camelCase (e.g., wasteWarrior). This resulted in undefined image sources and broken UI elements. We implemented and tested normalizeBadgeTranslationKey and normalizeBadgeSlug within badgeUtils. These utilities now sanitize any incoming string format from the API into a predictable format. The tests ensure that no matter how the backend formats the string, the frontend reliably maps it to the correct local icon and translation key.
• Readiness: This suite confirms that the system is stable for the 1.0.0 Official Release by validating the workflow. By checking the opereations in the reporting and feedback logic and inconsistencies in notifications in milestone 3 and all other endpoints before via Postman, we have ensured that the social interaction features are both secure and user-friendly. The system now handles edge cases, with graceful error handling and consistent data state.

Abdurrahman Arslan, Group 5, Frontend Team

• I continued to be primarily responsible for frontend implementation, UI/UX consistency, and standardization across the application. During this milestone, my focus shifted more towards refining existing features, improving usability, performance optimization, and ensuring alignment with acceptance criteria. I worked closely with backend changes (new endpoints), reviewed and tested multiple PRs, and contributed to acceptance planning and documentation while maintaining overall design coherence across pages.

• Main contributions:
  For this milestone, I focused on improving the notification system with content previews, refining UI consistency (especially in feed, challenge, moderator, and report-related views), and performing a major UI makeover for better clarity and interaction feedback. I optimized frontend performance by reducing repetitive API calls, implemented fallbacks for invalid media, and improved challenge state visibility. Additionally, I actively reviewed, tested, and coordinated PRs, resolved conflicts, and contributed to acceptance planning and criteria documentation.

Developed core additions to mobile features with test coverage, conducted code reviews. Managed APK generation and co-authored project documentation for Milestone 3.

• Finalization of Voiceover in mobile application
• Integrating report API endpoints, with test coverage and report-type notifications
• Implementing reset password functionality
• Review of important code from other mobile developers
• APK generation, data population for Milestone 3 demo

1. #743 - Voiceover: Finalized VoiceOver and TalkBack support by implementing dynamic accessibility labels and hints, specifically for notification, post interaction, and language choice contexts.
2. #798 - Reset Password: Implemented reset password modal in the profile page, rejection of weak passwords (also in register), with test coverage using Jest.
3. #809 - Report (API endpoints): Integrated the report API endpoints for posts and comments (report modal was present) with error handling and loading states, with test coverage using Jest

1. #761 - User Experience Assessment (Lab 8): Co-authored user assessment part in Requirements Review and Acceptance Planning document, which was a deliverable in Lab 8.
2. #789 - Demo-Data Strategy (Lab 9): Co-authored demo-data strategy part in M3 Demo Strategy document, which was a deliverable in Lab 9.
3. #822 - Population of New Images for the New Machine: Updated profile photos of users whose profile picture was not properly transferred from the old deployment machine.

Mobile Team Lead, Group Communicator. Responsible for writing mobile code, developing and maintaining tests, placing new features on the timeline and distributing tasks within the team by collecting customer feedback.

• Implemented “Notification post preview” and “Diversified Challenge Waste Logging” based on Milestone 2 customer feedback.
• Prioritized and implemented “My Impact on Planet” on mobile by combining user waste logs with researched impact data.
• Refactored the badges system: visuals, catalog, descriptions, and rarity-based prioritization on profiles.
• Simplified the profile page by consolidating options under a single Settings entry.
• Added a mobile feedback submission feature with the required API integrations.
• Contributed across milestone planning, testing, and documentation.

1. #757 - Notification Section Post-Milestone-2-Feedback : After the Milestone 2 demo, the customer emphasized the importance of having a body preview and image (if available) in notifications to improve user engagement. Based on this feedback, body previews, images, and navigation links were added to the notification items.

2. #794 - Structural Changes in "Impact on Planet" Section: Displaying the solid impact of logged waste was a frequently stated customer request in the first 2 milestones. To address this, I redesigned the graph to grow toward the negative y-axis, researched global average consumption per category from external sources and added them as benchmarks, and applied several improvements to the graph and modal behavior in a section that was previously basic and not fully accurate.

3. #824 - Mobile Feedback System: Implemented a mobile feedback feature that allows users to directly share their thoughts with the app owners. As part of this work, the profile page was also redesigned to include an entry button point for this feature.

1. #764 - Lab 8 Report: Revisit Requirements : Contributed to writing the revisit requirements section for the Requirements Review & Acceptance Planning Report.

2. #786 - Demo Data Strategy: Collaborated on defining a demo data strategy by creating realistic user profiles and data states to ensure scenario authenticity and proper coverage of edge cases.

3. #865 - User Interface/ UX for Milestone 3 Report: Added screenshots and explanations of newly developed mobile features to the Milestone 3 report.

• Supported the team in writing a series finale for our scenario.
• Further info: Week12, Week 11

Mobile Team Member - Responsible for implementing core mobile features, optimizing application performance, managing API integrations, and ensuring high-quality user experience across the mobile platform.

• Implemented a comprehensive badges system with 15 badges across 5 waste types and 3 achievement levels
• Developed search filter functionality with waste type filters for the Explore screen
• Optimized mobile app performance by eliminating N+1 query patterns and implementing local image caching system
• Contributed to demo data strategy and planning for milestone presentations
• Participated in acceptance test planning and milestone reporting

1. #801 - Mobile Badges Implementation: Implemented badges display on user profiles with API connection and unit tests. Delivered 15 badges across 5 waste types with interactive modal displays.

2. #803 - Mobile Search Filter Implementation: Developed search filtering system enabling users to filter posts by waste type (Plastic, Paper, Glass, Metal, Organic) with comprehensive unit tests.

3. #805 - Mobile Performance Optimization: Enhanced app performance by optimizing backend queries, removing N+1 patterns, implementing 3-week image caching, and cleaning up irrelevant code blocks.

1. #764 - Lab 8 Report: Acceptance Test Planning: Contributed to writing the acceptance test planning section for the Lab 8 requirements review and acceptance planning report.

2. #786 - Demo Data Strategy: Collaborated on defining demo data strategy including user creation, pre-populated states, and edge case handling to align with use case scenarios.

3. #321 - Populating application data: Populated the application data for the presentation as we planned in demo data strategy.

1. #802 - Mobile Badges Implementation: Added comprehensive badges system with 1,121 additions across 6 files. Implemented 15 badges with clickable chips, modal descriptions, and profile integration. Merged successfully with 17 review comments addressed.

2. #806 - Mobile Search Filter: Implemented semantic search with waste type filters (376 additions). Also resolved Profile Screen test failures and added comprehensive test coverage for search execution and filter buttons.

3. #828 - Mobile Performance: Major performance optimization PR with 1,226 additions across 14 files. Eliminated N+1 queries, implemented local image caching with automatic cleanup, significantly improving feed loading speed and app responsiveness.

1. #758 - Milestone 2 Feedbacks: Notification System: Reviewed and approved enhancements to the notification system addressing feedback from Milestone 2 presentation (579 additions, 7 files changed).

2. #796 - Show Impact Reconstruction & Custom Waste Logging: Reviewed major structural changes to the "Show my Impact" section and custom waste logging implementation (1,031 additions across 7 files).

3. #821 - Mobile Badges and Final Improvements: Reviewed comprehensive PR including profile redesign, feedback system implementation, and general badges design improvements (1,035 additions, 28 files changed).

• Actively participated in mobile team coordination and code review processes
• Contributed to milestone demo preparation through demo data strategy planning
• Maintained high test coverage for all implemented features with comprehensive unit tests

I was generally responsible for the backend related tasks, namely adding functionality and reviewing/testing code. I also helped with the presentation tasks and release.

• Adding functionality to the backend
• Reviewing code related to backend development
• Demo presentation
• Milestone 3 Documentation

I have also presented the app with Yusuf Onur Öksüz. And helped with the release of the final version.

Mobile Team Member - Responsible for implementing core mobile features, managing API integrations, leading the demo strategy and planning.

• Implemented the preview functionality for notifications by integrating optimized APIs to enhance listing performance and user engagement.
• Redesigned the Challenges section by integrating the new gamification process. Connectied new endpoints, added new predefined type selection feature, implemented the point scoring system, and added a challenge log history view.
• Planned the demo strategy, created the demo scenario, presented the demo.
• Participated in meetings and planning of the project. Contributed to the documentations and the task distributions in labs.

1. predefined specific types: The new challenge logic accross the app.

2. mobile/ challenge page redesign: Integrating the new gamification process. Connectied new endpoints. Added new predefined type selection feature, implemented the point scoring system, and added a challenge log history view.

3. mobile/ notifications preview: Integrated the preview functionality for notifications by using new optimized APIs to enhance listing performance and user engagement.

1. #789: Created the demo plan and strategy, latest version.

2. #760: Requirements review & acceptance planning. Distributed lab tasks and written my section of "write user experience assessment"

3. #863: Written Milestone 3 report section 3.4, 3.6 and 4.6 (it is in a different issue)

1. #835 - Mobile Challenge Page Redesign: Integrating the new gamification process. Connectied new endpoints. Added new predefined type selection feature, implemented the point scoring system, and added a challenge log history view. related to issue 1 and 2 above.

2. #843 - Mobile Notification Previews: Integrated the preview functionality for notifications by using new optimized APIs to enhance listing performance and user engagement. related to issue 3 above.

1. #808 - Mobile/ report endpoints: Reviewed, tested, approved and merged the new report feature.

2. #833 - mobile/ unit test for badges and feedback: Reviewed, tested and merged the new jest tests for the newly added features.

3. #840 - Mobile/ report notifications: Reviewed, tested, approved and merged the notification connecction for the new feature "report".

• Actively participated in mobile team coordination and code review processes
• Contributed to data population via pointing out what data is needed and how it need to be populated

Backend Team Member - Responsible for implementing core backend features, management of database , management of deployment, release of the web application and mobile application.

• Implementation of feedback and report/moderator feature at backend
• Implementation of badges and its triggers
• Creation and deployment configuration of the new machine(since previous one's free credit ended, space objects for photo and profile, configuration of nginx for https.
• Generate APK for mobile
• Participated in test coverage of backend and milestone reporting

1. #766 - Backend Report-Moderator Implementation: Implemented the report- moderator feature at backend. The users are able to report comments and posts and moderator can see the reports and delete the posts or comments.

2. #780 - Backend Feedback Implementation: Feedback implementation is done at milestone 3, as we aim to gather feedback from our users to improve our app.

3. #791 - Backend Badge Implementation: Implemented badges in backend part, they are obtained with triggers, the implementation is done at the db level since the badges are about the update of the tables and depend on the previous values in db.

1. #387 - Generate APK for final release: I arranged the dockerfile for the last release and build the mobile apk with a dockerfile.

2. #789 - Writing Demo Plan: I participated in the development of the demo plan, I have written the user roles part of it.

3. #822 - Update of profiles and posts for new machine: Since we needed to pass to new machine, the space object of the new machine is required to be created and photos in the mysql db are needed to be updated with the new urls.

• I wrote the swagger api of our backend.
• Contributed to milestone demo preparation through demo data strategy planning
• Maintained high test coverage for all implemented features with comprehensive unit tests in backend
• Wrote the status of requirements, testing of backend part of the milestone 3

• I was responsible for frontend team leading. I reviewed all the implementations and discussed them before implementation. Checked and decided on the technologies used. Maintained the api connection with services. Implemented needed features mostly focusing on testing and moderating for this milestone.

• Main contributions:
  For this milestone, I focused on implementing needed features like reporting, moderation and e2e tests. We faced lots of difficulties while trying to implement some advices from milestone 2 presentations. I reviewed and tried to ensure the stability of our app after improvements. Also again as a feedback from second meeting, I revisited the waste page to show the impact a user can do and fixed bugs in that page.

I am part of the frontend team, and I am responsible for the development of the frontend side of the project. Additionally, I am responsible for attending weekly and non-routine meetings, being part of the project planning, conducting necessary research, and writing reports and documentation.

For milestone 3, my main contribution was the development of the web frontend side of the project. In particular, I updated challenge cards and create challenge modal as discussed in meetings and according to updated backend endpoints. Predefined challenge types and logging predefined waste types are introduced for challenges in addition to new point logic. Furthermore, I implemented the comprehensive badge feature for web application. Created badge icons that is being used on both web application and mobile application. Created a badge catalog page and implemented a badge showcase component to enable users to show their earned badges. Moreover, I introduced tabs for edit profile modal and added reset password tab. Thereby, users are able to change their passwords in web application. Lastly, I have consideraqbly improved our application's VoiceOver support and made web application ready for customer demo. Aside these, I have reviewed and tested several PRs from my team members and merged them, proactively discussed important decisions for our project, attended all meetings and labs, and collaborated with my teammates about the project throughout the process.

• #782: Implementation of reset password feature for the frontend.
• #783: Implementation of predefined challenge types and challenge logs for the frontend.
• #800: Implementation of badge feature for the frontend.

• #763: Written WCAG 2.1 and i18 parts of Current Compliance Status sections of lab 8 report.
• #789: Written Timeline part in Demo Plan section of Lab 9 report.
• #862: Written UX & Accessibility Analysis part of 4.4 User Interface / User Experience section and WCAG 2.1 part of 4.5 Utilized Standards section in Customer Milestone 3 Report.

• #797: Implementation of updated predefined challenge types and log types in the frontend.
• #804: Bug fix in backend related to badge endpoint in the frontend.
• #814: Implementation of reset password section in profile page in the frontend.
• #817: Implementation of badge feature in the frontend.
• #847: Addition of our application logo as a web page icon.
• #851: Enhancement of VoiceOver support of our web application.

• #792: Reviewed and merged the PR on feedback feature implementation in the frontend.
• #818: Reviewed, tested, and merged the PR on fix of displaying unloaded images in the frontend.
• #819: Reviewed, tested, merged, and asked for a change for a comprehensive UI makeover for the frontend.
• #827: Reviewed and merged the PR on increasing test coverage for the frontend.
• #837: Reviewed and merged the PR on updating moderator page design and functionality in the frontend.
• #846: Reviewed and merged the PR on predefined waste type buttons in post searches in the frontend.
• #848: Reviewed and merged the PR on general frontend updates on components such as feedback, notification, moderator etc.
• #850: Reviewed and merged the PR on fixing of failed frontend unit tests.

Joined every single meeting/lab and actively contributed to discussions, organized my team members, actively discussed every aspect of our project through our communication platforms, and helped team members both in frontend team and in other teams on development of the application.

• Release Tag: customer-milestone-3_cmpe451-fall2025
• Live Deployment: waste-less.alibartukonca.org
• README Instructions: README.md
• Docker Setup: docker-compose.yml
• Mobile APK: Mobile Asset