README File:

Team Members:

• Roshankumar Loganathan
• Sahaja Thota
• Abhinaya Sree Talluri

Game Objective and Rules

Objective

"Would You Rather" is a virtual interaction game designed to be played by a group of people on a video call. While the game interface is controlled by a single player, all participants actively engage in the game by making decisions, giving instructions, or answering questions. The game presents participants with two intriguing alternatives, prompting them to choose one, leading to lively discussions and debates. The game can be found here: https://sahajathota.github.io/WouldYouRather/.

Rules

• Two Options: Players are presented with two distinct choices, which can be humorous, challenging, or thought-provoking.

• Single Player Control: One player controls the game interface, presenting questions and recording answers.

• Group Participation: While one person controls the interface, all participants actively engage by making decisions and discussing choices.

• Making a Choice: The group must discuss and select one of the two alternatives that are given. Their decision is final, and if they wish, they should provide justification. The game shows the percentage of the general population that chose the same option as they did.

• Discussion and Debate: The group may discuss based on the result of their choice and recuperate or deliberate the results.

• No Opting Out: Players cannot refuse to respond; they must decide even if both possibilities are unattractive.

• Respectful Play: The game should be played with good humor and respect. Avoid having any potentially harmful or disrespectful conversations.

• Winning or Score: The game "Would You Rather" isn't normally one where there is a winner or score. Instead of maintaining score, the emphasis is on having fun and talking to others. This game could, in a way, let you know what your friends think about various choices and could reveal the kind of person they are.

Technology Stack Used

A simple and effective technology stack was chosen for the technical implementation. The frontend's primary building blocks were HTML, CSS, and JavaScript, which offered a flexible and engaging user experience. We found this technology stack to be a good choice since it allowed us to focus on the game's content and functionality while streamlining the development process. As part of our technical implementation, we integrated the "emailjs" library to enhance email functionalities of the "Would You Rather" game. Using Emailjs, you can send and receive email from a web application with ease.

• Frontend: HTML, CSS, JavaScript.
• Email Integration: Emailjs - For seamless email functionalities within the game.
• Website Tour: Introjs- Is to create a walkthrough of the website.

Setup and Deployment Instructions

1. Clone the Repository: The project repository may be downloaded or cloned to your local machine. Git Clone: https://github.com/SahajaThota/WouldYouRather

2. Open in Visual Studio Code:

   • Launch Visual Studio Code.
   • Navigate to File > Open Folder and select the cloned WouldYouRather directory.

3. Install Live Server Extension:

   • In VS Code, go to the Extensions view.

   • Search for "Live Server" and install it.

     

4. Launch the Game:

   • Right-click on the index.html file in the project directory.
   • Choose "Open with Live Server". This will launch the game in your default web browser using a local development server.
   • After the extension has been installed, choose "Open with Live Server" from the context menu when right-clicking on an index.html file in the project directory. This will launch the game in your normal web browser and launch a local development server.

Credits for Third-Party Assets and Code

• Emailjs: Integrated for email functionalities. Learn more about Emailjs on its official website.
• ChatGPT: Assisted in certain aspects of coding and debugging.
• Introjs: Assisted in website walkthrough. learn more about introjs on its official website.

Reflection

Design and Development Process

Our journey began with brainstorming sessions where we deliberated on the game layout and formulated an intriguing set of questions. Once we had a clear vision, we designed a prototype version of the game. This prototype served as our foundation, allowing us to visualize the gameplay and user interactions. As we transitioned from the prototype to the main version, our focus shifted to refining the user interface, enhancing the user experience, and adding aesthetic appeal. The transformation from a basic prototype to a polished game was both challenging and rewarding.

Challenges Faced

One of the initial challenges we encountered was coordinating among the three team members. Allocating tasks, ensuring everyone was on the same page, and setting up regular meeting times required careful planning. Thankfully, tools like when2meet facilitated this process, enabling us to find common time slots and maintain consistent collaboration. Later we faced poblem making the website responsive in all types of devices and screens. After testing the project our website isn’t responsive for small screens. Later we as a team fixed the problem. The other challenge we faced is learning Emailjs library and implementing it. We have divided as subtasks and learned using the emailjs library and successfully implemented it.

What Worked

Our prototype version was a testament to our team's synergy and vision. It functioned seamlessly, validating our core game mechanics and logic. The success of the prototype gave us the confidence to enhance its visual appeal. We invested time in refining the design, experimenting with color schemes, and optimizing the layout to ensure an engaging player experience.

Firstly, the selection of HTML, CSS, JavaScript, Emailjs as the technologies worked well for our project. At the start of the project, we thought JavaScript would be a perfect fit for our project to fetch questions randomly and it went well as we thought. With the help of HTML and CSS we got a well-structured site with uniquely styled designs. Another thing we have had as deciding factor is between using PHP or using Emailjs. We tested the mail delivery system using PHP, unfortunately it didn’t work as we thought. Later, we used Emailjs library for sending and receiving emails for any support and it got worked well. Lastly, our webpage is responsive and supported all type of screens and the alignment is also fitted in all type of screens.

What Didn't

Initially, we were enthusiastic about incorporating images for each question, envisioning a more dynamic and visually rich game interface. However, as we delved deeper into the development, we wanted to keep the game simple, straightforward, and accessible, so we decided to drop the idea of integrating images.

Lessons Learned

Throughout this project, we learned the importance of flexibility in design and development. While it's essential to have a vision, being open to change and adaptation is equally crucial. We also realized the significance of effective team communication and the value of iterative development, and we got to know about the importance of assigning the roles among team and breaking down the project into sub tasks where we tracked our progress along with our mistakes. Starting with a prototype and progressively enhancing it allowed us to test our ideas and make informed decisions. We also got to learn about the importance of the testing part. We have tested our game continuously to find issues and fix them. Lastly, this project reinforced the idea that simplicity often leads to a more user-friendly and enjoyable experience.