Case Study
AJAX Beta Testing Platform
Interface
Desktop/Web Application
Role
Product & UX/UI Designer
Timeline
May - Aug 2025
About the project
This project was part of the Product Design course at Projector Institute, where we workedwith AJAX Systems to design dedicated platform solution for their Beta testing program.
AJAX Systems is the largest security systems manufacturer in Europe. Before launching new devices AJAX conduct an open beta testing with real end users in real-world environment, alowing the team to polish devices and experience based on real world usage data. But thats where the problems begin - the program is scattered across different flows, causing problems and inefficiency. AJAX need new, dedicated solution.
The problem of beta testing
And our challenge
Submission Problem
Many foreign testers often do not submit reports or submit them very late. AJAX assume that the problem lies in their Telegram bot - the main tool for submission, not only its UI is not user-friendly, but foreign testers don't like and don't use Telegram in general.
Communication Problem
Current communication with testers heavily relies on direct manual intereaction while also being fragmented across different platforms like messengers, email and even physical mail. AJAX need to automate communication processes and minimise manual touchpoints.
Current communication with testers heavily relies on
direct manual intereaction while also being fragmented
across different platforms like messengers, email and
even physical mail. AJAX need to automate processes of
communication and minimise manual touchpoints.
Processes Fragmentation
The whole program is fragmented and across different services: different tools for communication, separate Telegram bot, CRMs, spreadsheets for tetsers base and rating and many more. We need to find a solution that adresses all problems and bring efficiency of the programme.
The whole program is fragmented and across different
services: different tools for communication, separate
Telegram bot, CRMs, spreadsheets for tetsers base and
rating and many more. We need to find a solution to
adress all problems and brings efficiency to programme.
Research and problems that forced us to adapt
our approach
In this project research stage was truly the most important and mandatory stage, as we needed to understand all the complexities and intricacies of the testing process, as well as testers' experience in it. We chose qualitative research through user interviews as our primary method, we defined it as most suitable for our context and conditions.
But right from this moment we faces complications - we didn't have direct communication with AJAX, all our requests and questions went through our course mentor, which slowed down wholle communication. But this was only the begining, took significantly longer than expected to find testers, pushing us behind schedule and delivering only half the participants we needed.
Key hypotheses and findings
driven from research results
Unified Platform
Feedback & report interface
Feedback submission and bug reporting are scattered across different tools, inconvenient for testers and impractical for AJAX to manage and process.
A unified interface for feedbacks and bug reports will simplify the process, make it more convenient and clear for testers.
And a proper architecture of the submission flow can reduce cognitive load, increasing completion rates.
Motivation and Rating
Notifications center
Information updates - a crucial part of testing, currently it is very inefficient. Our solution - Updates Center, similar to notification center in smartphones, it organise all updates in one place. Combined with push notifications, this will keep testers informed, and reduce manual communication.
Ajax Systems is a Ukrainian technology company that develops wirelessand wired security systems and is the largest manufacturer of securitysystems in Europe, with over 4 million users in 187 countries.
AJAX have an open beta program for testing their devices close torelease. This is specifically open beta, which goes after their closed betawhere they test products for every cases and scenarios in strictly controlled conditions. Open beta is completely different, this beta goes among end users, chosen by team. AJAX find number of testers and give them devices for testing. The testing lasts for a few weeks, usually up to a month, during which time the testers shouldcomplete several test cases specified by the AJAX developers andsubmit reports for the testing period. This final testing allows the team topolish the device, find and fix bugs, as well as refine the user experienceafter receiving real-world feedback and seeing real user interaction with the device.
Dashboard as a central control panel
of the whole platform
Submissions & Reports - a unified solution to
simplify the process and experience.
Submissions & Reports - a unified solution to
simplify the process and experience.
The Dashboard serves as the platform's central hub - the first page testers see and a crucial
element in our design solution. It provides a structured overview of the most important
information, keeping testers informed and action-oriented.
Active Tests is the primary component, displaying tests that have updates or require action.
Tests are prioritized by urgency: a test needing feedback appears above one with a software.