Customer Milestone 2 Report ‐ CMPE 451 Fall 2025 - bounswe/bounswe2025group7 GitHub Wiki

📘 Customer Milestone 2 Report - CMPE 451 Fall 2025

1. Summary of Customer Feedback & Reflections

During Customer Milestone 1, the feedback we received highlighted several critical areas for improvement. Specifically, the feedback focused on the following key requirements:

  • System Stability: We were tasked with significantly improving the stability of both the web and mobile applications.
  • Semantic Standards: There was a strong emphasis on ensuring the semantic correctness and accessibility of the User Interface (UI).
  • Protocol Compliance: The feedback required full compliance with ActivityStreams and JSON-LD standards.
  • Multilingual Support: We needed to implement robust support for Turkish, English, and Japanese languages.
  • Data Accuracy: A key priority was improving the accuracy of nutrition data and calorie tracking.
  • Quality Assurance: The team was asked to enhance the testability and reproducibility of the entire system.
  • Deployment Consistency: We were required to ensure consistent deployment by mandating the use of Docker.

Reflections on Milestone 2

Based on this feedback, our team redesigned the sprint plan to focus on three foundational pillars:

  • Reliability and Standards Compliance
    • We have incorporated full JSON-LD contexts for recipe data and user interaction features.
    • We ensured that semantic properties rigorously match the W3C ActivityStreams vocabulary.
    • Comprehensive internationalization (i18n) has been implemented across web and mobile platforms.
  • Feature Maturity
    • Calorie tracking is now fully implemented across the backend, web, and mobile systems.
    • Micronutrients have been added to recipe detail pages to provide deeper nutritional insight.
    • We have optimized search and filtering to handle complex queries efficiently.
    • Translations are now live for English, Turkish, and Japanese (EN–TR–JP).
    • Currency conversion has been implemented based on the user's language settings.
    • Recipe retrieval endpoints have been improved for speed and reliability.
    • The Mobile UI was overhauled to improve clarity and meet accessibility standards.
  • Testing Coverage Improvement
    • Unit tests were implemented for Like, Comment, SavedRecipe, and InterestForm services.
    • Backend tests were added specifically for the new calorie tracking logic.
    • The mobile test suite was expanded to cover new UI components.
    • Integration tests have been stabilized to ensure reliable service communication.

This milestone represents the project's evolution from a prototype to a functioning MVP, offering better stability, semantic correctness, and multi-platform readiness.

2. List & Status of Project Deliverables

Deliverable Status Notes
Weekly reports, meeting notes Completed All documentation is archived and readily available in the GitHub Wiki section (e.g., #481, #468).
Updated use cases Completed New use cases covering Calorie Tracking (#506), Micro Nutrients (#505), and Translation (#504) have been documented.
Main feature implementations (MVP) Completed Features are fully integrated across the Backend, Web application, and Mobile application.
Unit and integration tests In Progress / Partial Testing is ongoing; most core services are now thoroughly tested, but UI and E2E tests still require expansion.
Pre-release version 0.2.0-beta Completed The release is fully prepared, including the required Dockerized web and Dockerized mobile environments.
Documentation & wiki updates Completed All use cases, a new demo outline, and all weekly reports have been updated and organized.
Deployment (GCP) Completed All tasks related to the Google Cloud Platform (GCP) redeployment have been successfully executed (#515).

3. Evaluation of Status & Impact on Project Plan

Completed Deliverables Impact

The successful implementation of calorie tracking across all system components significantly strengthens the core value proposition of the MVP. The robust multilingual support (EN–TR–JP) is a major step toward achieving the project's inclusivity goals. The increased unit testing coverage has boosted system stability and has provided the team with higher confidence in merging and deploying new features. Furthermore, establishing semantic correctness via JSON-LD and ActivityStreams positions the application excellently for future interoperability and data sharing.

In-progress Deliverables Impact

We note that some minor mobile UI refinements and non-critical backend refactoring tasks are still pending. More comprehensive End-to-End (E2E) testing is required to ensure complete readiness for the final demonstration. Crucially, the API contract documentation must be expanded and formalized to meet clear customer expectations.

Risk Areas

Three key risk areas have been identified: the reproducibility of the deployment (specifically for the mobile Docker image) must be rigorously validated; the new multilingual UI requires broader and more thorough test coverage; and the integrity of the nutrition endpoints needs stricter input and output validation.

4. Evaluation of Tools & Processes

Tools Used

Our technology stack and process tools remain robust and effective: GitHub Projects, Issues, and Pull Requests (PRs); GitHub Actions for Continuous Integration/Continuous Deployment (CI/CD); Docker and Docker Compose for containerization; a database layer consisting of PostgreSQL and MongoDB integrated with Spring Boot; React and React Native for the frontends; and testing frameworks including Jest, JUnit, and Expo Jest. We also successfully integrated the crucial standards of JSON-LD and W3C ActivityStreams.

Process Evaluation

The team's development processes have seen marked improvements this milestone. Our branching strategy was refined after addressing early merge conflicts. The PR review culture has significantly strengthened, as evidenced by thorough review threads (e.g., #551, #537, etc.). Task assignment and planning have become more efficient following the adoption of new Lab 7 workflows (#511). Notably, the team successfully adapted to the new, challenging requirement of mobile Dockerization.

5. Requirements Addressed in Milestone 2

Requirement Status Notes
R1 – Track calorie intake Completed Functionality implemented across Backend, Web, and Mobile systems (#525, #473, #528)
R2 – Search & view recipes Completed Backend improvements (#531) and mobile search integration (#548) are finalized.
R3 – View micronutrients Completed Micronutrient data is now displayed on the Web application (#486, #500 , #474).
R4 – Multi-language support Completed Full support for EN, TR, and JP is implemented across Web (#529) and Mobile (#530).
R5 – JSON-LD ActivityStreams Completed Backend utilities have been updated, but full integration requires finalization.
R6 – Accessibility improvements Completed Initial features like color-blind mode, dyslexic font, and dark mode are underway.
R7 – Deployment Completed Core Dockerization is complete, but the final GCP redeploy is pending verification. (#515)
R8 – Unit testing Completed Significant test additions have been made to core services (#514, #496).

6. Planning & Team Process

Changes Since M1

We have successfully implemented several key changes since Milestone 1 to enhance productivity and code quality:

  • A test-first PR workflow has been officially adopted to ensure high-quality code.
  • We resolved recurrent dev→main merge conflicts through better communication and process (#527, etc.).
  • Unified and standardized translation workflows were created.
  • We added structured planning for the final demonstration to minimize last-minute issues (#510, #511).

Plan for Completion

To finalize the project for the upcoming customer milestone, we will focus on the following:

  • Expand E2E tests for all critical user paths.
  • Fully integrate ActivityStreams across the entire data model.
  • Finalize and validate the mobile Docker environment for clean deployment.
  • Strengthen and document the deployment process on GCP.
  • Complete all remaining documentation and API contract details.

GitHub Projects Board

7. Utilized Standards

7.1 ActivityStreams 2.0

This standard is utilized for correctly modeling and representing all user interactions, such as likes, comments, and saves, which feed into the social and interactive components of the application.

7.2 JSON-LD 1.1

This standard is fundamental for structuring our recipe and nutritional metadata in a semantically correct and machine-readable format.

7.3 WCAG 2.1 AA

We are actively implementing the guidelines of this standard, which include accessibility improvements such as a dyslexic font, a color-blind safe palette, and a dark mode.

7.4 i18n Internationalization

Full internationalization has been implemented to support English, Turkish, and Japanese across both the web and mobile platforms.

8. UX Design: Accessibility, Inclusivity & Ethics

8.1 Key Use Case

The primary successful flow is where a user can seamlessly browse the recipe feed, interact with recipes (like/comment), accurately log meals using the calorie tracker, and switch the application's language without friction.

8.2 Accessibility

  • We implemented Dyslexic-friendly text to improve readability for users with dyslexia.
  • A Color-blind safe palette was developed to ensure UI clarity for all users.
  • Dark mode is available to reduce eye strain in low-light conditions.
  • The UI is fully translated to provide a native experience for all supported languages.

8.3 Inclusivity

  • Multi-language support promotes a global user base.
  • Currency conversion offers contextual and helpful financial information based on the user's location.
  • We are building a diverse recipe dataset to appeal to varied cultural tastes and dietary needs.

8.4 Ethical Considerations

Risk Mitigation
Privacy risks We ensure minimal data storage and maintain a secure, encrypted backend to protect user information.
Dietary bias We mitigate this by actively curating and sourcing a diverse range of recipes from various cultures and dietary restrictions.
Misinformation Nutrition and micronutrient data are rigorously schema-validated to ensure accuracy and prevent the spread of inaccurate health information.
Dark patterns The UI is designed to be fully transparent, intentionally avoiding deceptive design or gamification elements that could pressure users.

9. Testing

9.1 Unit Tests

Unit tests now cover critical backend services (LikeService, CommentService, etc.) and core mobile functionalities (Calorie tests). Web translation tests have also been added.

9.2 Integration Tests

Integration tests are focused on validating the full calorie tracking flow and the efficiency and correctness of recipe retrieval endpoints.

9.3 End-to-End Tests

Current E2E testing covers the critical user path: from viewing the Feed to viewing a Recipe, performing a Save, and finally logging a Calorie log.

9.4 UI/UX Tests

These involve manual accessibility checks against WCAG guidelines and comprehensive responsive design tests to ensure the application works correctly across various devices.

10. The Software (0.2.0-beta Pre-release)

10.1 Release

Name: 0.2.0-beta Tag: customer-milestone-2_cmpe451-fall2025 Key Features: This release includes the fully integrated Calorie tracking, micronutrient display, comprehensive EN/TR/JP multilingual support, refined ActivityStreams integration, and general semantic improvements.

10.2 Deployment

Web:

  • The web application is ready for deployment using the provided docker-compose.yml.
  • A configuration example is provided in .env.example, which will require the user to fill in environment-specific values.

Mobile:

  • The mobile application is containerized via its dedicated Dockerfile.
  • Configuration will be handled using the provided .env.example file.

10.3 Clean Environment Requirement

It is a crucial requirement that the provided deployment instructions must successfully execute in a clean, isolated environment (e.g., a fresh Virtual Machine or machine instance) to fully validate reproducibility.

11. Individual Contributions

Duran Kaan Altın (@duran0)

Responsibilities

I am responsible for frontend web internationalization (i18n), semantic refinement of UI components, and backend unit testing for comment-related services. My work during Milestone 2 focused on:

  • Extending multilingual support (EN–TR–JP)
  • Fixing untranslated or inconsistent UI elements
  • Expanding the translation system to newly added pages
  • Improving semantic correctness and accessibility
  • Adding backend unit tests for comment operations
  • Supporting web demo preparation and UI refinement

Main Contributions

Throughout Milestone 2, my work strengthened the project’s multilingual capabilities, frontend semantic quality, and backend reliability. Key contributions include:

  • Added Japanese and expanded Turkish translation support for the web application.
  • Integrated translations for newly added calorie-tracking pages and components.
  • Fixed untranslated UI elements, ensuring a fully internationalized and consistent user experience.
  • Implemented backend unit tests for CommentService, increasing reliability of user-generated content features.
  • Contributed to the preparation and refinement of the web demo flow.

Significant Issues

Code-Related (Top 3)

  1. Japanese & Turkish Translation Initial Addition
    Issue: #483
    Added initial Japanese and extended Turkish language support in the web frontend.

  2. Addition of New Pages to Translation System
    Issue: #538
    Added translation keys and implementation for newly introduced UI sections.

  3. Fix Untranslated Button in Calorie Page
    Issue: #544
    Resolved untranslated UI elements to ensure consistent multilingual behavior.

Non-Code-Related
  1. Web Demo Preparation
    Issue: #510
    Assisted with planning demo flow, verifying interface readiness, and ensuring multilingual consistency.

Pull Requests Created & Merged

  1. Japanese & Turkish Support (Web)
    PR: #529
    Added Japanese language support, updated Turkish translations, and improved language-switching behavior.

  2. Translations for Newly Added Pages
    PR: #539
    Integrated translations for additional pages, especially those related to calorie tracking.

  3. Fix Untranslated UI + Semantic Refactor
    PR: #551
    Fixed untranslated UI components and refactored semantic logic related to the calorie and search modules.

  4. Unit Test: CommentService
    PR: #513
    Implemented backend unit tests covering comment creation, deletion, and error paths.

Pull Requests Reviewed

  1. Mobile Translate + Currency Support
    PR Reviewed: #542

  2. Mobile Profile Page Translation Fix
    PR Reviewed: #552

Additional Information

  • Improved translation key structure in the web side, across modules for future maintainability.
  • Helped verify multilingual behavior across EN/TR/JP in preparation for customer demo.
  • Assisted teammates with semantic alignment and UI consistency during integration.

Hasan Arda Güneş (@Hasan-Arda-Gunes)

Responsibilities

I am responsible for the backend of the project, reviewing others' work and mobile and frontend testing. My Milestone 2 work includes:

  • Translation feature on backend
  • Backend bug fix
  • Unit test for interest form backend
  • Adding UI components to web and mobile
  • Tests for web and mobile

Main Contributions

  • Adding Translation Service to backend. The request body consists of text, source language and target language and it gives a response body containing the translated text.
  • Fixing the database related bug in backend
  • Testing the web and mobile for any problems before the merges.
  • Reviewing others' issues and the PR's related to those issues. Informing others if there is any problem with their work.
  • Writing unit test for interest form in backend using junit.
  • Adding UI components for the nutritions for web and the recipe detail page in mobile.
  • Preparing Calorie Tracking Use Case for the demo.

Significant Issues

Code-Related (Top 3)

  1. Adding translation for backend

    Issue: #470

  2. Backend bug fix

    Issue: #520

  3. Unit test

    Issue: #497

Non-Code-Related

  1. Calorie Tracking Use Case

    Issue: #506

Pull Requests Created

  • PR: Add Unit Test for Submit Interest Form #517

Pull Requests Reviewed

  1. PR: Add Like Unit Test #523

  2. PR: Add Calorie Tracking Test Mock #495

  3. PR: Merging Dev to Main #540

  4. PR: Add Update Function to Calorie Tracking #521

  5. PR: Add Get All Recipes For All Users #532

The reviews for PRs exist in their corresponding issues.

Additional information

  • Documented the feedbacks to prepare for the next milestone
  • Reviewed how to add a badge system for our app
  • Generated mock recipes for testing the nutrition data and showing in the demo

Burak Korkmaz (@burakorkmaz)

Responsibilities

I am responsible for backend side, devops of the project and UI testing of the mobile and web application. My work during Milestone 2 focus on:

  • Calorie tracking backend enhancement.
  • Micronutrient backend enhancement.
  • Dockerisation of project.
  • Unit test.
  • UI and UX test for web and mobile.

Main Contributions

  • Adding Calorie Tracking feature with extensive date parameter. Adding CRUD models of the Calorie Tracking side. User may create, update, read and delete their tracking for specific recipe.
  • Relating the recipes to the calorie tracking and calculating their calorie properly. The portion size is considered, so the calorie calculation is close to reality.
  • Adding micronutrients of the recipes by using external API to fetch the micronutrients of the ingredients. Micronutrients says to user that how much recipe has Iron, Potassium, and etc.
  • Adding docker-compose-local.yaml file for the local deployment of the web application and backend application. Adding local database
  • Adding Dockerfile for creating apk file of the mobile application.
  • Writing unit test of the calorie tracking.
  • Testing UI of the mobile and web application.

Significant Issues

Code-Related (Top 3)

  1. Adding Calorie Tracking Issue : #473

  2. Adding Micronutrients Issue : #474

  3. Docker-compose and Dockerfile Issue : #553

Non-Code-Related

  1. Gcp Deployment of the app Issue : #515

  2. Task Distribution during Lab 7 Issue : #511

  3. Use case of Japanese Translation Issue : #504

Pull Requests Created & Merged

  1. Calorie Tracking PR : #488

  2. Micro Nutrient PR : #479

  3. Adding Get All Recipe Endpoint PR : #532

  4. Equalizing Test branch to Main Branch PR : #489

  5. Unit test for Calorie Tracking PR : #495

  6. Equalizing Dev to Main PRs : #526 , #533, #540, #546, #555

There were conflicts between them sometimes. Especially in translation files. I have solved them one by one.

Pull Requests Reviewed

  1. PR : #537
  2. PR : #539
  3. PR : #551
  4. PR : #530
  5. PR : #529
  6. PR : #525

Kerem Bozkurt (@kerembozkurt2002)

Responsibilities

I am responsible for frontend web development, backend unit testing, and Calorie Tracking feature improvements. My work during Milestone 2 focused on:

  • Implementing the Calorie Tracking Page with full functionality
  • Adding and refining the update flow in the Calorie Tracking module
  • Writing backend unit tests (Like Utility, Interest Form utility)
  • Creating documentation for the Calorie Tracking use case
  • Reviewing and merging PRs related to calorie tracking and backend testing

Main Contributions

Throughout Milestone 2, my contributions improved the usability, correctness, and reliability of the Calorie Tracking system. Key highlights include:

  • Developed the Calorie Tracking Page for the web frontend with create/update functionality.
  • Added the update functionality for calorie entries, ensuring correct calorie recalculation.
  • Wrote backend unit tests for multiple utilities, including Like and Submit Interest Form logic.
  • Authored the Calorie Tracking Use Case documentation for the project wiki.
  • Reviewed and merged critical PRs such as calorie tracking mocks, update logic, and recipe-related endpoints.

Significant Issues

Code-Related (Top 3)

  1. Calorie Tracking Page with Functionality (Web)
    Issue: #485

  2. Unit Testing for Like Utility
    Issue: #492

Non-Code-Related
  1. Wiki – Calorie Tracking Use Case
    Issue: #506

Pull Requests Created & Merged

  1. Calorie Tracking Update Flow
    PR: #534

  2. Frontend Enhancements for Calorie Tracking
    PR: #524

  3. Calorie Tracking Integration Fixes
    PR: #523

  4. Frontend Component Refinements
    PR: #522

  5. Unit Tests for Interest Form
    PR: #518

Pull Requests Reviewed

  1. Calorie Tracking Test Mock
    PR Reviewed: #495

  2. Get All Recipes for All Users
    PR Reviewed: #532

  3. Add Update Function to Calorie Tracking
    PR Reviewed: #521

  4. Unit Tests for Submit Interest Form
    PR Reviewed: #517

  5. Additional Review
    PR Reviewed: #514

Additional Information

  • Helped maintain consistency between frontend and backend calorie models.
  • Ensured smooth integration of calorie tracking updates.
  • Assisted teammates by reviewing PRs and validating frontend workflows.

Kerem Haktan Kurt (@Kerem-Kurt)

Responsibilities

I am responsible for Mobile Frontend Development, specifically focusing on the health tracking modules and data visualization. Additionally, I contribute to Backend Quality Assurance by ensuring service stability through unit testing. My work during Milestone 2 focused on:

  • Developing the Calorie Tracking interface for mobile.
  • Implementing data visualization (Charts) for nutritional intake.
  • Ensuring data integrity through strict Date Validation in forms.
  • Implementing Search functionality within the recipe creation flow.
  • Writing backend unit tests for the Like/Unlike endpoints.
  • Managing form state integrity and input validation across the mobile application.

Main Contributions

Throughout Milestone 2, my work significantly enhanced the mobile user experience regarding health tracking and improved backend reliability. Key contributions include:

  • Created the Mobile Calorie Tab, allowing users to view and manage their daily intake.
  • Designed and implemented Calorie and Nutrition Charts, providing visual feedback on user diet data.
  • Implemented Date Validation logic across required forms to prevent data entry errors.
  • Developed Search Functionality for the "Add Recipe" page to streamline ingredient/recipe selection.
  • Wrote Unit Tests for Unlike Endpoint, ensuring the stability of user interaction features on the backend.
  • Integrated responsive design principles into the calorie tracking modules to support various device sizes.

Significant Issues

Code-Related (Top 3)

  1. Create Calorie Tab (Mobile) Issue: #501 Created the dedicated screen and tab navigation for calorie management, ensuring proper layout and data binding.

  2. Implement Search Functionality for Calorie Recipes Issue: #535 Implemented the search logic required during the recipe creation process to filter items effectively.

  3. Implement Unit Test for Unlike Endpoint (Backend) Issue: #490 Implemented backend unit tests covering unlike logic to ensure service reliability and prevent regressions.

Non-Code-Related
  1. Preparation for Mobile Demo Issue: #509 Assisted in preparing the mobile application flow for the milestone demonstration, ensuring all features functioned seamlessly.

Pull Requests Created & Merged

  1. Implement Calorie Tracking Feature with UI Integration PR: #525 Implemented the core calorie tracking UI, including the calorie tab and nutritional charts for visual feedback.

  2. Implement Recipe Search Functionality in CalorieScreen PR: #537 Added search functionality to the recipe adding flow to allow users to easily find and log foods.

  3. Enhance Date Validation in CalorieScreen PR: #549 Enforced strict date validation rules to ensure that calorie logs are accurate and consistent.

Additional Information

  • Focused on optimizing mobile performance when rendering complex chart data.
  • Collaborated with the backend team to ensure the LikeService tests matched the API contract requirements.
  • Ensured input validations on the mobile side were consistent with backend constraints.
  • Refined the mobile folder structure to better accommodate the new chart and tracking components.

Erencem Özbey (@ErencemOzbey)

Responsibilities

I am responsible for Mobile Development, with a primary focus on accessibility features, particularly multi-language support and translation consistency across the application. Additionally, I contribute to the micronutrient tracking functionalities and ensure overall service stability by addressing UI integrity issues and validating data flow.

During Milestone 2, my work focused on:

  • Implementing full translation coverage for all feed elements, posts, recipes, and search results.
  • Ensuring correct currency conversion based on the user’s selected language and locale.
  • Maintaining UI integrity and accessibility, ensuring consistent component behavior across languages.
  • Co-designing user scenarios and assisting in creating the demo flow with Yiğit Kağan Poyrazoğlu.
  • Supporting micronutrient-related features and ensuring their compatibility with multilingual functionality.

Main Contributions

Throughout Milestone 2, my work strengthened our mobile application's accessibility and usability by ensuring language consistency, improving user experience, and supporting critical nutrition features. Key contributions include:

  • Implemented comprehensive multi-language support across all major pages: feed, posts, recipe details, and search views.
  • Ensured accurate currency conversion, allowing prices and nutritional data to adapt to the selected locale dynamically.
  • Improved UI integrity, resolving inconsistent layouts and ensuring all visual elements adapt properly across languages.
  • Helped shape the demo scenarios and presentation flow, ensuring a clear and realistic representation of user journeys.
  • Supported micronutrient tracking functionality, ensuring its correct integration into the mobile interface and multilingual structure.

Significant Issues

Code-Related (Top Issues)

  1. Multi-Language Support to Mobile
    Issue: #465
    Implemented translation logic and ensured all primary components and pages are fully localized.

  2. Fix Problems with Translation
    Issue: #466
    Resolved inconsistencies in translated strings, addressed missing keys, and enforced a standardized internationalization structure.

  3. Testing
    Issue: #480
    Contributed to mobile testing efforts to validate translation, formatting, and UI behavior across languages.

  4. Calorie Tracking
    Issue: #482
    Ensured that calorie tracking views are fully translated and properly aligned with UI/UX requirements.

  5. Micro Nutrition Story
    Issue: #516
    Collaborated on implementing micronutrient functionality and confirmed its compatibility with multilingual support.

Non-Code-Related
  • Demo Flow Planning
    Designed the Milestone 2 demo scenarios with Yiğit Kağan Poyrazoğlu, ensuring the presentation accurately represented user journeys and feature functionality.

Pull Requests Created & Merged

  1. Saved Recipe Functionality Testing
    PR: #499
    Contributed testing coverage to ensure saved recipe interactions function correctly across languages.

  2. Mobile Translation + Currency Conversion
    PR: #542
    Added comprehensive translation support and implemented seamless currency conversion logic.

  3. Add Recipe Ingredient and Search Improvements
    PR: #543
    Refined recipe ingredient input and improved search experience, ensuring compatibility with multi-language support.

  4. Calorie Tracking Page – Translation
    PR: #550
    Added translation support for calorie tracking pages and ensured UI adaptability for multilingual layouts.

Additional Information

  • Ensured full localization coverage across newly developed features during the milestone.
  • Improved user interface consistency by reviewing element spacing, alignment, and scaling across languages.
  • Coordinated with the nutrition and backend teams to ensure translated fields aligned with API structures.
  • Helped optimize the translation and formatting to reduce redundancy and improve maintainability.

Yiğit Kağan Poyrazoğlu (@poyrazogluyigit)

Responsibilities

I am responsible for Web Frontend Development, specifically the components related to recipe management, nutrition details, and the integration of micronutrient data into the web interface. I also contribute to frontend testing to ensure reliability and alignment with backend API expectations. During Milestone 2, I focused on:

  • Integrating micronutrient information into recipe views.
  • Redesigning the Recipe Detail Page to support richer nutritional data.
  • Improving the overall web UI for consistency and clarity.
  • Writing unit tests for recipe creation logic.
  • Co-creating the demo flow and user scenarios with Erencem Özbey.

Main Contributions

My contributions during Milestone 2 focused on lifting the web interface to support the new nutrition features and improving navigability and clarity for end users. Key work includes:

  • Implemented full micronutrient integration on the web, updating recipe components to display extended nutrition data.
  • Redesigned the Recipe Detail Page, fixing layout issues and improving readability across devices. -Ensured UI consistency after the nutrition expansion, adjusting styles and component structure.
  • Wrote unit tests for recipe creation, covering the core logic to reduce regression risk.
  • Helped design a coherent demo scenario, ensuring the milestone presentation accurately showcased the nutrition-related features.

Significant Issues

Code-Related (Top Issues)

  1. Frontend Recipe Detail Page Redesign Issue: #519 Reworked the recipe detail UI to support new micronutrient data and improve visual structure.

  2. Micronutrient Information Integration Issue: #486 Added micronutrient fields to the web interface, ensuring proper API alignment and rendering.

  3. Unit Test for Recipe Creation Issue: #494 Implemented frontend test coverage for recipe creation, focusing on validation and data-flow correctness.

Non-Code-Related
  1. Demo Preparation & User Scenarios Issue: #516 Co-designed milestone demo flow and user journey walkthrough with Erencem Özbey.

Pull Requests Created & Merged

  1. Micronutrients Implemented in Frontend PR: #500 Added full micronutrient support to recipe components and updated UI accordingly.

  2. Unit Test for Recipe Creation PR: #498 Added initial test suite for recipe creation (currently pending merge due to conflict).

  3. Re-added Micronutrients After Merge Conflicts + Translation Fixes PR: #545 Restored micronutrient features and ensured compatibility with the project’s translation updates.

Additional Information

  • Improved internal component structure to support future nutrition-related features.
  • Ensured front-end logic remained compatible with evolving API schemas.
  • Assisted in aligning micronutrient display with mobile and backend expectations for consistency.

Yiğit Memceroktay

Responsibilities

During this milestone, I was mainly responsible for the development of the Mobile Project since I was more experienced in that area. I focused more on the internationalization of the mobile project and small UI Bug Fixes

Main Contributions

  • Implemented I18n for the internationalization of the mobile project interface
  • Implemented the translation feature of the recipes using MyMemoryAPI
  • Improving the overall mobile UI for better user experience and consistency
  • Implemented a backend unit test for the recent feed functionality
  • Helped design a coherent demo scenario, ensuring the milestone presentation accurately showcased the translation features of our mobile project

Significant Issues

Code-Related (Top Issues)

  1. I18n Internationalization Issue : #541

  2. Implemented Translation Feature for the Recipes Issue : #472

  3. Backend Unit Test for the Recent Feed Utility Issue : #493

Non-Code-Related
  1. Demo Outline Preparation
    Issue: #502
    Created an outline for the milestone 2 demo

Pull Requests Created & Merged

  1. Translation for the mobile project PR: #530 Implemented I18n internationalization and translation for the mobile recipes using MyMemoryAPI

  2. Mobile UI Bug Fixing PR: #552 Fixed some significant UI bugs for the profile page of our mobile application

  3. Backend Unit Test PR: #448 Implemented backend unit test for the recent feed utility of our mobile project