How the app works

Ola is an app built with both a client and an admin side, though we will focus more on the admin side of the app.

Responsive image

After the admin logs in the app, the dashboard page will appear with some key information and statistics.

Responsive image

The admins are the only persons that are allowed to add new products in the app and for every product a code must be generated in order to track them efficiently. Moreover, the admins must also set the visibility of the product for the users, due to the reason that some of the products might need to stay private.

Responsive image
Responsive image

The app usually relies on the users when it comes to buy a new license or extend the current ones, but in case something goes wrong, the admin has the ability to generate a new license. (There is also a superadmin option where it allows you to delete or edit the user licenses).

Responsive image
Responsive image

The calendar offers information about the upcoming server maintenance schedule and licenses that are due to expire soon.

Responsive image
Responsive image

(Admins' profile can be modified only by a superadmin).

What I learned

First of all, there is no right way of building a perfect licensing management system and usually it comes down to the preferences that the buyer needs. Ola was created from a general point of view, which means that it could be improved alot more, such as adding an email/messaging contact support for the users or providing more essential information on dashboard pages. When I designed the app I debated between using the current UI or one based more on tables (which would have been better if this app was inteded to store big data for corporations).