User Interfaces for Relap.io

Publisher's account, Adroom, Statistic dashboards and Design process
I selected the focus points so that it was clear how I think when I design. That I am focused on business interests, but I always try to take care of the user. Ultimately, this is business care.

Publisher's account of Relap.io

Any site owner can install a Relap script on his site, add any number of widgets and customize their design to the site features. It remains to enable monetization to start earning.

I used several onboarding patterns so that you can easily install and enable advertising even to the average person with the default best settings and hide all expert settings. Each step is preceded by clear instructions and helpers. Feedback reaction from the system has been considered for all user actions. The current state of the system is always in front of the user's eyes.

Images are clickable:

Relap Adroom

With the development of a recommendation system and an increase in the number of publishers, there has been a demand for a platform for the distribution of advertising. The recommendation system has become a network of native advertising. It took a family of interfaces to run ad campaigns and load creative content into them. Manage audience segments and targeting advertising campaigns. Watch and control the progress of ad campaigns.
Track critical metrics and export reports.

I met with the manager account managers and sales and team lead development for in-depth interviews. While the developers were building a rough, but working prototype using open source, I designed the future platform and built up the required functionality.

Statistic dashboards

Relap users critically need convenient access to reading current data and key metrics. How effectively widgets work, what fill rate of advertising, topical reports with data on the quality of advertising budgets are important for account managers and sellers of advertising.
Design process
I start with the information architecture and semantic organization. Then I do an analysis of the relevant references, working on logic, making drafts of components and layouts of the future system. I specify details, draw screens and assemble a clickable prototype to test logic and usability and coordinate the result with the owner. If necessary, I draw flowcharts for developers. At the end, I describe the task, decompose the large tasks into stages, and prepare a task pool for developers and assistants. I work alone or in a team, which is much more effective.


Retrospective
I always analyze past experience. I compare with the present moment, with modern design patterns and see what I would change now. If you have the resources and time, I suggest making an update. You can always improve what is already there. Make it work better and look cleaner. It hurts me to look at the first versions of the product, but such is the thorny path to a high-quality product.
© 2019 Egor Abaturov