Assets and Transforms

This guide will walk through a few of the core concepts of assets, transforms and how they come together with the UI to create an experience.

You can read more about what an asset is here. In short:

For all intents and purposes, views are equivalent to assets for this guide.

In general, the pipeline for user-content is something like:

Player will do minimal processing of each asset in the tree, resolving data in strings, applicability and any other generic processing it can. The processed tree is then sent to the rendering layer, where it is turned into a native component on the system Player is running on.

For simple Assets, like text, there’s no need for any asset specific processing. The output of Player is enough to successfully render and display the content to the user.

When dealing with user interactions(inputs, selections) or some further data/communication is needed with Player, we expose a mechanism for individual assets to augment Player’s processing with it’s own custom data. By breaking this out into it’s own discrete step (outside of the UI), we allow asset state to exist outside on an individual rendering, and thus sharable across platforms. These augmentations are processed through a stateless function called a transform.

Transforms can be added through the asset-transform plugin, and they run as part of the core player’s reconciliation step. This improves performance, as the transforms are cached between updates to the view, and re-usable as they can be registered across platforms to share common logic for assets. You can refer to the cross-platform guide on sharing Player logic across multiple platforms.