Sprint 3 Review - Rohan Bojja

[Rbojja23]

Sprint 3 Objectives

Overview

1. Create and Compete (Reality Room)
2. Night at the Museum (N@TM)

---

Reality Room

An interactive game and chat area to interact with AI or humans.

• Features:
  • Post discussions and comments.
  • Guess if the image is AI-generated or not.
  • Chatbot for guessing whether the responses are from AI or a human API.
• Reality Room Home type=canvas&t=MITKmBs74wd8LFQX-0)

---

Individual Contributions

1. Figma UI Design

I heavily contributed to the design aspect, leveraging my prior experience.

• Iterations: We went through multiple iterations to finalize a layout that the team agreed upon.
• Link to Figma:
  Flocker Room Design

2. Reality Room Frontend

• Reflection: I could have improved this area more.
• Challenges: Spent excessive time on design iterations, which delayed functionality and visuals.
• Final Version Improvements: Color scheme, dimensions, and layout matching our final design.

---

Team Contributions

Collaboration Skills

One of my key takeaways from the project was the importance of collaboration, especially between frontend and backend developers.

• Communication Tools:

  • Slack for quick updates.
  • GitHub Issues for detailed collaboration.

• Takeaway: Functionality depends on seamless integration of frontend and backend.

---

Night at the Museum (N@TM) Summary

We enjoyed presenting our chatroom and game at N@TM. Many attendees were interested in learning more about our project.

---

Presentation Overview

1. Highlighted the main homepage with various posts.
2. Showcased dynamic chat rooms with unique ID numbers for commenting and chatting.
3. Presented the interactive game where users guessed if the chatbot responses were from AI or a human.
4. Demonstrated data and posts saved in a backend SQLite database.

---

Comment Examples (Total: 12)

Feedback from Viewers

1. Srijan Atti (CSA): Loves the concept; suggested improving cohesive theming/styling and better-defined DIV containers.
2. Ethan Zhou (CSP): Enjoyed interactive features and AI chatbot similar to ChatGPT.
3. Shriya Palagudu: Appreciated the design and complex topics like AI bots.
4. Nikhil Lalwani: Suggested enhancing student interaction for a more human aspect.

---

Main Improvements

1. Visual Design: Enhance dimensions of posts, color scheme, and define DIV containers clearly.
2. Human API: Incorporate APIs (e.g., Twitter API) for human-like interactions.
3. Real-Time Leaderboard: Connect leaderboard functionality to the backend.

---

Assignment	Points	Grade	Evidence
Sprint 1-3 Review Ticket	3	2	I believe my designing skills were good, however, I could have improved on the actual frontend desinging and backend connections, suhc as with post and get request.
Sprint 3 Team Issue(s)/Plan	2	2	I believe we were up to date effectivley and were always stayign ahead of the curve, where we made sure to complete the designing quickly and get to work on forntend and backend.
Beginning-2-End Contribution	2	1.5	Although my contribution to the frontend was cosistent, I could have been more of an asset in the backend, as well as implementing the Gemini chat bot API
N@tM Team Presentation	2	2	The whole team equally split topics to talk about in the presentaiton. Specifccly, I spoke about the main home page and how each post was connected to a dynamic chat room, where you can interact with the author.
Live Review Indi Demo	1	1	I felt our live reviews showed our knowledg ein the field and how we can implement differnt items and API's into our projects. We earned a 0.93 on our first progress check for this project.
Total	10	8.5

Skill	Points	Grade	Evidence
Work Habits (Analytics)	1	0.8	Although commits were not consitent, it was mainly due to merge conflcits that could have been a future problem. We circumnavigated this problem by instead sending blocks of code through slack which we indivdually worked on, and neil, would mainly implement these into the md files for the actual frontend.
Evidence of Role in Team	1	0.9	I believe I played a vital role in the devlopemtn of the frontend. I also played a role in creating the design for this proejct, where we did multiple iterations and finnaly ended up on a good idea.
Function / Purpose Design	1	0.9	I have a good understanding of both the frotnend and backend, but I could be more knowledgable about the specfic API implementation process if I particpated more in backend.
Live Review	2	1.85	We did a progress check with Mr. Mortenson and ended up with a 0.93 for our first one, which equations to a 1.86. These live reviews allowed us to show progress in our project and how we are iterating through designs, etc.
Total	5	4.45