iOS Assets

The assets package looks like this, every image resource here can be customised:

Important things to know:

the images on the Benefits slides can have any name/number but they have to match with the ones specified in the KBActivation.json file. Here they are denoted with “ac_[1,2,3,4]_image”.

each keyboard theme has a preview image and a theme logo image (possibly the same logo image). Again, the name and number of those images can vary, but it needs to match the respective fields in the KBThemes file. In the example, they are:
"kbtheme_preview_large_keyborders[0,1]” and "kbtoolbar_items_logo[0,1]”, for the 2 themes. See:

In the toolbar-icons group we have the icons of the main toolbar buttons. In the more-icons group we have the icons of the more toolbar section buttons. This is a convention, but sometimes you can have a main button with an icon from the more group, or viceversa. Again, the name and number of those images can vary, but it needs to match the respective fields in the KBToolbar file. In the example, they are:
"kb_toolbar_items_repository_*” and "kb_more_items_repository_*”. Depending on the customers current UI, only some of the images are used. It’s up to the customer to manage the images here. See:

besides from the asset types specified above (the ones that are synced with json files), all other assets have fixed name, by which they are identified in the SDK.
some more “generic” assets (not the ones discussed above, that are synced with json files) might even have defaults in the SDK.