Initialize Widgets on Startup (Optimized Story Experience)
In Optimized Story Experience, you can choose to initialize specific widgets on startup to influence the performance of your story if it uses viewport or background loading.
In the Styling panel of a widget, you can select Always initialize on startup. Then, for example, it's initialized on startup with visible widgets and ready to be accessed in the onInitialization event, even if viewport or background loading is enabled.
This option is only available to story developers.
This can also improve the story's performance if any scripts performed on startup need to access the widgets whose loading otherwise haven't yet been finished in the background.
-
Initializing a widget on startup won't work if you don't set its container to Always initialize on startup and the container is invisible. Therefore, if you use this option for widgets that are embedded in a container, make sure that either the container itself is visible in view time, or you've enabled Always initialize on startup for it.
-
If the widget set to Always initialize on startup is used as data pool only and never visible in view time, we strongly recommend placing it directly on the page or popup instead of in a container.
-
If you aren't sure if the widget is initially visible for low screen resolutions, for example, it makes sense to set the widget's view time visibility to visible with Always initialize on startup selected.