- Create a single service that integrates both API and Database experience while maintaining a familiar user experience.
- Define the features for a minimum viable product.
- Address the absence of similar interfaces and acknowledge uncertainty about user appreciation for the product's value.
To address this challenge, the following steps were taken. Firstly, extensive interviews were conducted with the stakeholder to thoroughly understand the overall scope of work and functionality of the future platform.
Secondly, a competitor analysis was done to understand common patterns and user flows.
Thirdly, prototyping and thorough user testing of the future system's screens were carried out. This allowed for validation of the functionality and effectiveness of the proposed solutions, as well as incorporation of necessary adjustments based on user feedback.
• We have planned a fairly large period of time for onboarding and gathering requirements.
• Considering specific area another important aspect of successful cooperation and obtaining the expected result was the involvement of the client at all stages of development.
We defined that there are no direct competitors on the market for our service so I conducted an analysis of our main indirect competitors (API and Database services). In this study I focused on common feature research to define a list of general features that would be valuable and useful for our service for MVP stage. Based on the collected data, I created a mind map.
We developed user stories to create user flows that show the steps that the user will take to complete a task or achieve a goal and to test the product to ensure that it meets user expectations.
User Flow for connecting API and Query:
Prior to creating the wireframes, I took into consideration the potential scalability of the service and focused on designing a clear and user-friendly navigation system that can handle a substantial amount of data and functions.
I identified the necessary features and functionalities required for API and Data Base interfaces and determined how the user would perform the required actions to connect the database request to the API. I created different scenarios to ensure that the user experience is seamless and intuitive. Overall I created 100+ screens during this stage.
During the process of creating the wireframes, we conducted user testing through interviews to assess the usability of our interface and gain insight into how well users could understand and interact with it.
How many prototypes do we need to test user flows?
In short, as many as will be enough to uncover usability issues, validate design assumptions, and refine the user experience. For this project, I've created 100+ screens constantly making changes. At the end of our contract with the client, he asked me to recreate same screens for user flows applying UI
We developed the Design System, since we planned to expand the platform and it will include several different services, and we want to maintain consistency.
After considering various design options and conducting several rounds of testing, we ultimately chose to use a dark theme for our interface because it is:
– visually appealing;
– reduces eye strain;
– provides a sleek, modern look;
– most of the developers we interviewed use dark themes.
