Adaptive design of the application for each user

I am of the opinion that mobile apps should be more personalized. I don't need some functions, others I use more often. But for some reason we equalize one size fits all, so that by a little bit, but to please more people. A little further in terms of personalization went news feeds and social. networks that provide unique content to everyone.

But what if you go even further and, in addition to content, provide people with a personalized UI ?!

Theory

Concept

1. The application itself understands what you often use and brings the frequently used functionality to the first screen.
2. Places items in order of importance on the page so that you would not need to reach out with your thumb.
3. Depending on how often this element is used, its content will also be very different.
4. There are also triggers: a push notification has arrived, a specific date or user action. This trigger has its own specific gravity, which is assigned to an individual element for a short time.

Logics
')
Calibration phase

The person uses the application.

And the program itself analyzes the number of clicks on each element and gives the unit a specific weight.

Smooth implementation phase

After the initial calibration, we can carefully deploy the most popular request to the main page, in a separate block.

Item Verification Stage

We analyze the frequency of visits and determine whether an element is worthy of staying on the main page.

And if it is worthy and it is used often, then we consider the option of expanding this cell, so that the user performs the target action even faster.

Practice

Application implementation example

A good example is banking applications.

Why?

1. They are multifunctional
2. As a user, I don’t need most of the functions, but they may be more important to others
3. Some of the functions may be needed only at some point.
4. Everyone uses these applications, so it’s easier to understand the concept

Here I will try to show at the stage of sketches as I see it should be. If the post is interesting, then I will already make a demo application on iOS.


Scenarios

Each person has their own scripts that he performs. They are not always logical, and the task of the application is to make it easier to achieve this goal.

Scenario 1 : I often transfer money to the same person (younger brother, child, wife).

We can add a block with the ability to quickly translate it to him.



But the block itself can evolve like Pokemon. If we see that they are often used.

Level 2 block:



Here we can translate directly from the cell itself by clicking on the translate button

The application understands that this function is not only used often, but also the amount is the same, so we go further and change the cell so that the default amount is set for this operation.

Level 3 block



Scenario 2 Once a month I pay for an apartment, here the date trigger works.
The application understands that approximately this number every month I give money for an apartment.
And it is logical for us to show this particular block on that day on the main screen and remove it after making the payment.

Scenario 3 Close the loan after receiving the RFP.

Trigger. I got a sn on the card and the application understands that usually after this action for a day or two I close the loan that hangs on me.

The payment now appears in the block.

Scenario 4 I use chat with support

Often, if we correspond in chat with support, then this process is not fast, we can turn off the application several times, go about our business and come back later, so we can communicate with the chat, take it to the first screen. As we know when he started the conversation and when, in principle, he solved the problem.

Scenario 5 I withdraw money from the current account to the card

A trigger triggers the receipt of money p / s, and I suppose we always distribute them among my cards:



I wanted to convey the idea that the user experience can be improved by trying to help him accomplish what he wants as quickly as possible, of course it will be more difficult for us as developers, but this will be appreciated by our customers. Tell me, what do you think about this approach?