It is important to consider what style of portal you will be using for your event in order to design the correct assets. Before discussing the portal with your designer, it is recommended you know which assets you require based on the list below.
Portal / Standalone App Store Listing Assets (required)
A full-screen graphic that appears briefly as the portal loads when it is first opened and will act as the background for your portal on a phone.
A full-screen graphic that appears briefly as the portal loads when it is first opened and will act as the background for your portal on a tablet.
The icon that will appear when the portal is downloaded on an iOS device.
The icon that will appear when the portal is downloaded on an Android device.
Android feature image
The feature header image used as part of your portal listing on the Google Play Store.
Tile Entry Portal
An image that, when clicked, directs an attendee to a linked project from within a portal. Portal tiles typically contain information about the linked project (e.g. event name, date, location etc.). Tiles must be 720 x any.
Navigation tile used for multi-layered tile portals
Logos and other images can be uploaded and linked to actions such as moving between portal layers or could simply be a static image. Images must be 720 x any.
Image that links back to the previous portal layer
Code Entry Portal
Enter Code Image
This image sits on top of the Phone/Tablet Background/Splash. This is a static image that, when clicked, will direct an attendee to the 'Enter Code' screen. This image will often have some kind of call to action (e.g. Tap to enter event code).
All assets must be supplied exactly as specified. The Core will not accept assets with any deviations from the specifications. Read more.