At the very beginning of our group creation, I took initiative to build our wiki home page and sidebar. I created personel page template and meeting notes template. Such foundation allowed my team to keep consistent structure while filling our individual profile pages, and taking meeting notes that are highly elaborate and descriptive. This experience was one of my first encounters with the wiki syntax. Fortunately, the learning curve was not steep, and I enjoyed working on them.

• Issues #3, #4, #25.

For our first customer milestone, I took the lead on writing the milestone report, along with Ramazan. This was the most challenging task I have undertook so far in the scope of this project. I investigated previous years' repositories to figure out what kind of content we are expected to provide. I took notes from the document provided from the teaching staff, and I outlined the table of content of the report. Then, I initiated the wikipage and determined the subtasks. We divided the sections of the report equally with Ramazan. I wrote the project description & project status, and the organization and communication sections. I also provided a table for the status of the deliverables, as well as the table for the individual contributions. Additionally, I filled the deliverables section of the project by providing brief introductions for each deliverable and adding the related URIs. Moreover, as we discussed wth the team, I took initiative on preparing the roadmap view of Github for our project planning. I observed my teammates adding their issues to the project, and I sorted them accordingly, to obtain a nice time-flow in our project planning view.

• Issues #85, #91, #94.

I was the reviewer of the use-case diagram. After my teammates designed the first draft, I provided an exhaustive review and held a meeting with Suleyman to further improve the diagram. Then, I took the initiative in my group to ask for feedback from the teaching staff for the class and use-case diagrams. I comminucated with the assignees of the use-case diagram several times during this process, to ensure we follow the feedback and general guidelines to obtain a good quality use-case diagram. This process of

• Issue #104.

For the Milestone 2, I implemented the personal profile page for mobile. Then, I worked on some design details to make personal and feed pages look similar to each other, and to the web design. I worked together with Ramazan to resolve the node version issue we encountered and took notes of the solution in our repo. I worked with Ramazan on a connection with the back end. I also worked on resolving minor bugs, we encountered in mobile at the last minute, with Ramazan. For the demo of our project, I organized the flow of our demo and presented it with Suleyman and Abdullah Umut.

• Issues #126, #136, #152, #158.

For the Milestone 3, I implemented a Post component, a comment screen and extended the Feed page to display all the available posts on the platform, as well as the tagging and uploading image functionalities to create post screen. I then worked on the implementation of the requests to backend endpoints. With valuable support from Ramazan and the entire backend team, I implemented several connections between the mobile UI and our backend, ensuring a smooth functionality and user experience for our platform.

• PR #203: Mobile UI screens
• PR #215 & #229: Mobile requests to backend for personal profile, comment and share post screens.
• PR #224: Preserve the user info as a parameter between Mobile screens.
• Issue #190: Improve create post screen.
• Issue #200: Implement post component and extend feed page.
• Issue #238: Implement various requests to backend.