Add-ons Store

My role

Category

Scope

UX/UI Designer,

UX Researcher

Case Study

2 months

2024

Year

Landingi is desktop platform where users can create their own landing page and then take a series of steps to help optimize their marketing campaign.
 

This project involved designing a new functionality for the landingi.com application, where users can buy add-ons to expand the scope of their account. 

Brief

 Dependence on Support

Buying add-ons was done “manually”. - Support had to set up the entire configuration. The user was forced to wait for the purchase to be finalized.

 
⤷ A lot of steps! 

User had to go to a separate subpage, where he had to fill out a form and .... wait to be contacted by support (wait for an email response). From the user's point of view, this is quite a lot if he wants to buy just a few extra domain slots.

Problems statement

  1. User can purchase or run a free trial period on his own.
  2. User has access to a single place from which to manage add-ons.
  3. User learns about new features in an accessible way, and has the opportunity to try them out.

Goals

I started my search by looking at competing solutions and best practices in other SaaS systems.

 

I looked at Marketplace solutions presented on the web as well as directly in the application by: Asana, Intercom, Hootsuite, Semrush. In this way, I analyzed how a given company approaches the presentation of Marketplace in marketing vs. app version.

Competitive analysis

Each add-on is divided into categories - the most common are: popular, new, for a specific industry, team, etc. - the user can easily find what he needs.

Categories

After selecting an application, the user sees a profile where he gets a simple and condensed description of the application, add-on, etc. This is usually limited to sections: Overview, Features, Pricing, Privacy & Security.

Add-on profile

Each marketplace consists of a tiled layout, which contain the logo, name and a brief description of a given application - the minimalist layout ensures readability for the user.

Layout

Conclusions

It took me quite a while to...

Then I sorted out the information of all Add-ons (by the category they come from) + badge and all the states they may be in.

A good box layout was also an important aspect of the project (a couple of variations were created), and here, too, the help of the other members of the UX team in making the final decision became invaluable:

find the most useful layout for the overview Add-on. I presented my thoughts and quick designs to the rest of the UX design team - together we chose the clearest version in terms of UI implementation:

Based on the research, I started sketching the Add-ons Store concept and the application profile. Due to the relatively small number of add-ons that the Landingi platform currently has, I decided not to include categories.

Ideation

There was also a need for single plan variants - the user's choice of plan is mainly determined by the number of visits to the landing page and secondarily are the domains.

Those associated with the user in sales lacked a place that directly invites the user to provide possible consultation.

The current price list presented the total amount on an annual basis. The user of changing the billing period has no sense of how much he is saving.

I ran two iterations of the tests, which showed the following findings:

Usability testing

Final project

Thanks to this project, I was able to have the opportunity to create from scratch a part of the platform that can significantly affect the ARPA rate. I worked hard to reconcile the business model with the current user needs.
The challenge was to prepare the design documentation, first of all to anticipate and design each user flow:

 

  •  I had to reconcile the design with the current technical capabilities of the platform.
  • I had a relatively small amount of time to complete the project.

 

During this project, I worked a lot with the PM, who supported and helped organize the information architecture, and we agreed together to divide the project implementation into three iterations. 

Reflections 🤔

Email me 

LinkedIn

Let's be in touch!

Feel free to contact me if having any questions. I'm available for new opportunities or just for chatting.

Strona zrobiona w WebWave.