Visual customization

Overview

Usually almost all campaigns have a visual representation. In our SDK, the entity responsible for the visual representation of a campaign is called creative.

If you have a campaign instance you can access the creative, to do this you need to cast campaign instance to ICampaignWithCreative.Creative.

The following are ways to handle all types of creatives.

Image creative hadnling

You can see the default handling of campaig with ImageCreative in the ImageCreativeCampaignHandler class.

The default processing is to determine what the screen mode is now (portrait or landscape). Then, depending on this, take the necessary portrait or landscape link and try to get an image (from the hard disk if the image has been downloaded before, or download it). Then use popup to display the creative.

Custom creative handling

You can see the default handling of campaig with CustomCreative in the CustomCreativeCampaignHandler class.

The default handling of this creative type is to use CustomCreative.ScreenId to display the custom creative via popup.

Bundle creative handling

Currently, Magify SDK does not have a default handler for this type of creative. We are working on adding one, but for now you have to implement it yourself if you want to use the BundleCreative.

The simpliest processing is to try to get an AssetBundle (from the hard disk if the bundle has been downloaded before, or download it). Then use popup to display the bundle.

Working with the asset bundles is a big enough topic so we've put it in a separate article.

Working with popups

Popups are the primary way to visualize creatives in Unity. Campaign visualization, products displays, product interactions - all this is done with the help of popups.

First we need to decide on the implementation of popups, Magify provides the following set of interfaces for working with popups IPopupBase, IPopup and IPopupWithProducts.

Out of the box, Magify supports loading popups through the Resources folder using the ResourcesPopupsProvider class. Another way - you can implement the IPopupsProvider interface and override methods for those types of popups that you are going to use and be sure to define a method UnloadPopup regardless of the number and type of popups, it must unload any loaded popup from memory. IPopupsProvider works with IPopupBase, IPopup and IPopupWithProducts interfaces, they are needed to allow Magify to show popups and visually interact with the player.

Embedded popups

You can use our embedded in SDK popups. They already provide the basic logic of opening and closing and also provide the possibility to change animations (by using the ease settings in the script or inheriting from them and adding your own logic).

Popups customization

If for some reason you can't use one of the ready-made popup scripts, then you can implement one of the interfaces (IPopupBase, IPopup or IPopupWithProducts) depending on which campaign you want to display the popup for, and implement all the necessary logic to display the popup the way you want.