Hi, my name is Anna Sabotovich , I am a tech lead at Alfa-Bank (payments and transfers team), responsible for the development of the BDUI platform on Android. I will show you how we implemented analytics in the screen contract on BDUI and how we connected them with trackers. I will tell you what difficulties we encountered along the way, what restrictions we provided for and what tasks we put in the backlog. You will learn how we use BDUI at Alfa-Bank and how we collect product analytics when a user interacts with a BDUI screen.
Users not updating, removal
off page seo service from stores, compatibility, or Why do we need BDUI?
Let me start by describing the problem.
In mobile development, releases have always been difficult. The mobile release cycle and the time it takes to roll out changes to users is much longer than on the web or backend. In addition, even if we release a new version of the application, this does not mean that the client will want to update - he can sit on the old version of the application for years because he does not want to change anything or is afraid of bugs in the new version.
From the graph we can see that 42% of our users use versions of the app released last year.

This means that we need some mechanism that would allow us not to rely on releases, but to deliver new features to users bypassing the release cycle. And I will tell you about this mechanism further.
BDUI comes to our aid. What is it? It is when a mobile application does not know what to draw and goes to the backend for content.
The backend sends configs for rendering in JSON format, and the frontend layouts the screen using these configs.
This allows you to change the UI at the front end without a release and deliver changes to users as quickly as possible.
Alfa BDUI
We have several frameworks in Alpha that implement the BDUI approach. Today we will focus on one of them - it is multi-step.
Four years ago, the development of the BDUI framework began on the payments tab. We integrated a payment service that can send a set of different fields for making a payment. This set of fields depends on the provider, it is different for Moscow and Rostelecom housing and communal services, and also depends on the user's choice at each step.