*in partnership with André Gonçalves
We have already talked about the advantages of having a Developer Portal with your API business. However, in addition to making information available to developers, it is necessary to understand the behaviours that occur when accessing information and to identify if the user experience is meeting the needs and is easily and clearly understandable.
So, conducting a behaviour analysis and inserting tools that can help this goal will always allow improvements and evolutions in the Dev Portal. In this post, we will teach you how to perform a behavioural analysis applied to your Dev Portal and what tools you can use in this process.
Behavioural analysis of users is a practice usually performed in multiple ways by a UX Designer, requirements analysts, marketing professionals and other roles related to digital platforms.
This activity basically consists of comparing the various actions that each user performs during their behavioural pattern when using a system, in addition to making comparisons among usage patterns within the same group and even with the rest of the world.
The two main goals of Behavioural Analysis are to identify usage patterns of a system that would be considered normal activities for using the tool, as well as finding abnormal behaviours that deviate from an expected routine.
When combining different information collected during the analysis process, it becomes possible to identify suspicious behaviours through abnormal usage patterns, which can be an indication of a security problem. It makes the investigation and proactive resolution of this crisis more dynamic, in addition to making it possible to apply information from normal access patterns to generate a more concise, fast, intuitive, and dynamic application flow for your user.
It is common to often forget to treat developers as normal users of applications and, consequently, this fails to address some problems that are common for developers. It is necessary to use the information acquired in conducting the behavioural analysis to raise the demanded requirements to bring the best experience to the developers, focusing on crucial aspects of this specific group that will consume this type of content.
Throughout this process it is also possible (and necessary) to use tools/plugins, as there are several available on the market and which can be added to the Developer Portal and assist in monitoring the user experience and information, which will together support this behavioural analysis.
These metrics may assist in identifying areas of improvement in documentation, accessibility, navigation clarity and usability gaps.
Two of these tools are already well known and provide us with information and data about access and experience in the usage journey:
They are used to control access to the Developer Portals, and are able to identify the most accessed pages (heat map) and eventually what may be outdated or not clearly understandable.
In addition, it is possible to identify with this map potential failures/improvements in the distribution of the documentation, so it can be easily located by the developer.
Another particularly interesting information that is available is the recognition of how the developer arrived at the channel/Portal Dev as their final destination (search methods).
That is, it is possible to identify if it was through a specific post, directly by searching on Google, or other access methods.
There are also other additional tools that are complementary in extracting and understanding usage and information, such as Google Search Console.
Tool that will help to identify which improvements should be applied, starting from items such as duplicate titles/information.
It also shows which pages have the best performances, thus highlighting the strengths of your Portal.
All these actions and monitoring will support the partner developer in the onboarding process and ensure quality in the inputs, information distributions and user experience on the Developer Portal.
A difficult onboarding process, complicated documentation to read or a lack of support can make a potential partner to give up using it.
Thus, conducting the analysis of the use of your Dev Portal, with tools for monitoring the entire user journey, ensures that you find possible gaps, and thus can make the necessary improvements, so that developers have the best experience using your portal.