FAQ

DivKit is a cross-platform library based on the Server-Driven UI approach. It lets you build the user interface of apps and websites using their layout description in JSON format.

This a development concept used to generate the layout of web pages and apps on the server. Next, the layout description is sent to the client, where the UI is automatically rendered based on this description.

Using this concept, you can:

• Change the appearance of your app and add new visual elements without releasing a new app version.
• Use the same page layout on different platforms.

The client side of DivKit supports iOS, Android, and Web.

The AppStore and Google Play rules do not prohibit updating the UI of apps based on data received from the server, provided that these updates do not change an app's original concept.

Yes. DivKit is an open-source library released under Apache License Version 2.0.

In our experience, it takes less than 16 ms on average to render heavy web pages. DivKit runs in multithreaded mode and can reuse previously rendered elements. This lets you quickly estimate text elements (such as large volumes of text or tables) and speed up the interface in general.

A card description in JSON format can be stored on the server or locally on a device.

To generate card layout descriptions in JSON format, you can use the json-builder library that is available for Kotlin, TypeScript, and Python.

The pydivkit library contains components for generating JSON from Edadeal.

The layout of a card should be described in JSON format according to a particular scheme.

To prepare a JSON description of the layout and see a preview of the card in web format, you can use DivKit Web Playground. Next, you can transfer your JSON file to the DivKit Playground app for Android or iOS and see how the layout is displayed on a mobile device.

DivKit supports actions that can be called when clicking on an element. Using actions, you can change the status of elements, upload additional data, or invoke event handlers that are implemented at the host application level.

DivKit also supports variables and triggers. A trigger is fired when the value of a variable changes and triggers one or more actions.

Yes. For example, using variables. If the value of a property is set via a variable, when the variable is changed, the view is rebuilt.

The logic can be handled using variables, calculated expressions, and triggers. DivKit also contains a set of functions for working with strings, dates, and numbers.
For example, if a user enters text in a field, this value can be passed to a variable. Changing the variable value fires a trigger that triggers a certain action.

Yes, DivKit supports several types of animation: transitions when switching states, clicking on buttons, and displaying and hiding elements.

Yes, you can. For example, in Yandex applications, DivKit cards are often integrated into one or more screens.

Yes. To do this, use the div-input element designed for text input.

Yes. DivKit has elements that provide accessibility for disabled people.

Special localization mechanisms are not provided. To localize your interface elements, generate individual JSON layout files for each language.

We don't have a ready-made solution to deploy the server side with. DivKit contains libraries for generating JSON layout files that you can integrate into your server.

Use variables. For example, you can get a palette from the server as a combination of two colors for each element. On the client side, you should set variables that indicate the colors to be used for elements.

For proper logging, make sure log_id is unique. For example, when logging cards in a carousel, each card must have its own log_id, otherwise only the first card will be logged, and all the others will be considered duplicates.

In animation, specify "name": "no_animation".

To add a Lottie animation, set the extensions array in image. For more information, see Customization.

If you need a block that will just take up space, use separator and specify a transparent color for it in the color parameter.

It isn't worth it, it will affect performance. Try not to create unnecessary wrappers.