Custom portal process

Create your own branded event app portal, from which attendees can access any number of apps. Portals may either require a unique code or show a list of available apps, which can be split into pages of different categories.

Step 1. Decide on your portal type

Option 1 - Code portal

  • Has only one button which opens an ‘enter code’ input screen.
  • You can define a “view all” code which will show a list of all visible linked projects/apps along with those recently viewed by the user.
  • Used in situations where you have:
    • Large numbers of projects/apps.
    • New projects/apps are being added continuously.


Option 2 - Tile portal


  • Show a menu comprised of a series of 'tiles' or buttons which can link to projects or sub-menus
  • Can have any number of tile 'screens' or sub-menus
  • Tiles can:
    • Link to other screens in portal.
    • Go back to previous screen in portal.
    • Show all visible, linked projects/apps.
    • Show a coming soon message.
    • Open the ‘enter code’ screen to access any linked project/app via the access code.
    • Be set to hidden (use this to hide tiles prior to use).
    • Can be semi-transparent.
    • Be images only (un-clickable) - common uses:
      • Titles
      • Dividers
      • Spacers (use a blank/transparent tile).
  • Used in situations where you have:
    • A predefined number of events, usually a series.
    • A need to break projects/apps into categories for ease of navigation.


Step 2. Wireframe your screens

If using a tile portal to ensure all stakeholders agree on the structure before moving to design phase. This can be as simple as a biro sketch.


Step 3. Design the portal graphics

  • All portal types use the phone/tablet splash screen as the background (keep them simple).
  • Code portal
    • Button must 640px wide.
    • Height can be anything up to 900px and is always centred in the screen. (tip: use transparency to position elements).
  • Tile portal
    • Button width must be 720px.
    • Height can be anything.
    • Mockup each screen for stakeholder approval before separating asset.

Next steps...

The Ignite team will build and test your portal in the Core. Once you are satisfied that the portal is working as required, you will begin the store submission process.