Scrubs Fight
Mobile game
Scrubs Fight

Scrubs Fight is a mobile game for intellectual battles on a medical topic. This application was created as an additional tool for medical students - to make studying less boring.
Figma, Flutter Flow

4 weeks


Product Design, Development, Product Strategy, User Research, Integration, Visual Design, Prototyping & Testing, Product Development
Product video review
Understanding the problem
The problem of studying medicine involves constant studying and boring lectures. There are no tools that allow you to consolidate the knowledge gained during lectures in some form of play. The idea of a mobile game in the format of an intellectual battle quiz arose from a practicing doctor who remembered his learning experience as a student, and wanted to give today's students a tool that would make their studies more interesting and varied.
Defining the MVP
Based on the research, it turned out that there are similarities in the product vision. We have identified the following key user stories:

- Science oriented. A set of basic sections of medicine: cardiology, virology, gastroenterology, hematology and others.
- Community. Forming a list of friends with whom you can play in the future
- Competition. each user can challenge another user by creating a game.
- Rounds. The game consists of 4 rounds.
- Topics advantage. In each round the gamers alternately choose the topics of the round. Thus, every round the opponents have an advantage over the opponent, forcing him to play "on the opponent's field of knowledge."
- Game for 3 results. Win, draw, defeat.
- Point system. For victories, draws and (even) defeats, players receive points that can be used for various purchases in future versions of the application.
In order for the engineers to begin on the architecture, our designer mocked up the main screens for the MVP based off the sketches and came up with the following:

• Introduction screen
• Login screen
• Register profile
• Home page
• Friends search + adding
• Friend invitation to the game
• Game creation
• Round topic choice
• Questions answering
• Rounds results
• Finale result + adding points.
As time goes on, we've done some mockups of the main user path before moving on to the style we want. Mockups were compiled taking into account Flutter Flow restrictions to a visual design.
We have also developed several variants of logos based on references from the Customer.
We used Invision to allow the engineers to inspect the HTML and CSS of the designs. The team used Flutter Flow to develop the application.
To provide an intuitive understanding of the structure of the app, we tested the sitemap on site with potential users using what is called tree testing, their corresponding tasks such as "Where would you click if you wanted to get a result?" Based on the testing results, the sitemap has been adjusted accordingly.
Working process
Work plan

Week 1

1) Layout of prototype screens for authorization
2) Adding authorization via email and a unique username verification system
3) Development of a database for gaming sessions
4) Getting started with the layout and mechanics of game sessions

Week 2

1) Completion of game session mechanics development
2) Loading a database with categories, questions, correct and incorrect answers.
3) Debugging and testing the game session
4) Uploading test versions to stores

Week 3

1) User statistics
2) Adding push notifications
3) User profile layout

Week 4

1) Layout of the finished design
2) Full testing with real users
3) Debugging bugs
4) Build and add the application to Google Play.
Results and takeaways
Some key takeaways are that:

Focus on building an MVP. In a startup, there is only so much time and effort that you can invest so it's important to focus on the features that can deliver the highest value for your users.

Don't worry too much about the detail. Earlier in our journey, Clients made the mistake of worrying about the look of the UI design. Taking a step back and reassessing the user flows helped Clients to reprioritise the UX design. Ofcourse it's necessary to care about Usability, but do not set yourself the goal of reloading the product with various gimmicks.

Focus on the problem. At the end of the day, it is your users pains that you will be solving for so keeping that front of mind is important as it's easy to lose sight of this when you're bogged down in the day to day.

Aware your goal. That is why MVP is called so - Minimum Viable Product. Minimum - uncomplicated but main goals solving. Viable - proves it's necessity and urgency. Product - comlieted self-sufficient. Follow each letter of MVP definition and let it be created the new product.
Sinneo is a low-code development studio. If you want to launch business quckly and minimizing your financial costs, you can order the development of a website, mobile and web application, crm systems, task tracker, social network and other IT products from us.

Do you have a fantastic idea to implement? Contact us and let's start!
Build better with
Join our waiting list