Ryadom Platform
Interactive platform design for processing applications with service centers
About
It's a ecosystem that unites access to offerings for households, technicians, and manufacturers of plumbing and engineering solutions.
Task
Design and prototype a clickable MVP platform that will be accessible to service centers and manufacturers of plumbing and engineering equipment.
Goals
Increase transparency in the scheme: Client → Warranty Repair → Service Center → Manufacturer;
Help manufacturers optimize the costs for warranty repairs.
Role
Senior Product Designer
Year
2022
1. Collection of requirements
The client came with a product idea and a rough understanding of the needed features. We held several in-depth calls to dig deeper, brainstorm, and organize everything clearly.
We identified three main roles in the workflow: Client (not involved in the platform interfaces), Service Center, and Manufacturer.
Designed the high-level structure of the main pages
And moved to the design stage
2. Design
Hypothesis "Chat-Superapp"
As an initial hypothesis, I proposed that the fastest and most convenient way for communication and tracking interaction history between the service center and manufacturer would be a text chat — a persistent element accessible across all relevant pages.
I created a prototype of the request page featuring this chat, where users can order warranty details, update the request status, and ask any questions. The chat also stores all dates and the full history of any changes made to the request.
We discussed the prototype inside the team, I liked the idea, but they came to the decision to change the concept.
Then I designed some sections in accordance with the previously received requirements
And then I joined a Zoom meeting to present and defend the prototypes in front of the client
Final design
During the discussion, we realized that the chat feature isn’t needed at this stage. The communication processes within the platform should be simplified as much as possible. The manufacturer is a complex entity and likely won’t use or be able to effectively engage with the chat.
In the end, the designed sections took the form of flows with carefully thought-out behaviors, scenarios, and all necessary pop-up windows.
The prototypes at the meeting defended and started the design stage
3. Design
The current site is taken as the basis of the corporate identity.
Dashboard
Users start their journey on the platform from a centralized dashboard, where manufacturers can see a comprehensive overview of the current status— including request statistics, service center info, and entry points to other sections.
List of applications
On the list page, the manufacturer also sees analytics on current requests, with the option to navigate to detailed pages. The requests themselves include intuitive bullet points highlighting the strengths and weaknesses of each service center, enabling informed decisions about rejection without needing to open the detailed view.
The detailed page of the application
I decided to implement a modular block structure across the entire platform, allowing for easy feature expansion at any time. On the request page, we introduced a useful feature: a QR code for the equipment that reveals its full usage history—purchase date, service center visits, and whether it has ever been involved in fraudulent activities.
On all pages for pluses and minuses, a single intuitive format of red and green icons is used.
List of service centers
The service centers list page also includes overall analytics, filters, and the ability to view the service centers’ locations on a map.
Detailed page of the service center
On the detailed service center page, the manufacturer has access to general information, a list of employees with their qualifications, and the service center’s open requests.
Detailed analytics
Also, on the platform there are pages of detailed analytics on which you can see data on a certain section for any time of time.
Other pages
Ultimately, more than 25 pages and conditions turned out, but unfortunately, the client asked not to publicly show the entire platform entirely.
