Flamelink Multi-variant Configuration

Article author
Edward Herdemian
  • Updated

What is a variant? 

  • A variant is a different persona that a VenueNext app can take which will then change the Flamelink configuration of a page in app based on the selected variant. 
  • Examples of variants are Mens Basketball, Womens Basketball, & Football. 
  • Other examples include Ben Hill Griffin Stadium, Exactech Arena, & Florida Ballpark.
  • As seen, variants are dynamic and can be what makes the most sense in the context of the given mobile app.

What apps support variants? 

  • As of November 2020, new VenueNext app releases support multi-variants. 
  • If your app has not been updated in awhile, or you are uncertain if multi-variants are supported in your app version then reach out to VenueNext to ask or schedule a release.

How to configure variants?

  • The first step to setting up multi-variants is to contact VenueNext with the variants that should be enabled for the mobile app.  One of the variants should be identified as the default.
  • When complete, VenueNext will confirm the variant ID for each. 
  • For example, the variant name is Mens Basketball and the ID for it, provided by VenueNext, is mens-basketball
  • Steps to create a page for each variant:
    • Log into Flamelink, select the app collection, & click view
    • Each page shown will be for the default variant (i.e. Mens Basketball), there is no need to change the page name for the default (i.e. Home remains as Home)
    • To then create a different page for a 2nd variant (i.e. Womens Basketball), tap new entry on the top
    • Enter the page name followed by the variant ID provided by VenueNext (i.e. Home-womens-basketball)
    • Enter in the Flamelink content as you normally would, and described in other help articles
    • Currently the VenueNext SDK will continue to use a single org/ venue
    • All pages in the mobile app will share the same variants and each should have a page defined for each variant. 

How to select a default variant?

  • For existing apps with previous versions that do not support multi-variants then the default variant should be the variant for the context of the older app version.
  • I.e. if the older app version was for Football, then the default variant should be Football.
  • This helps to ensure that users on the old app version will continue to use their app with no issues.
  • Otherwise, the variant can be whichever one should be selected by default on first launch of the app.

What will the mobile app user see & experience? 

  • On each page, the user will see the variant selector (shown below)
  • When changing the variant, the content of the page will update accordingly
  • The previously selected variant will persist across pages and will be remembered the next time the user goes back to the app



Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request



Please sign in to leave a comment.