Learning & Support


Creating your app

Twixl Support Team Updated: - Created :

    Everything starts with the creation of an app on the Twixl platform. This article explains the ins and outs.

    1. Add Application

    1.1. Application Type

    When you add a new Twixl app on the Twixl platform, you can choose between several "templates" to get you started. For more info about each of these templates, see: Getting Started & Sample Apps

    1.2. Application Mode

    The next thing to select, is the Application Mode. The idea is that you start with a Development App and once your Development App has been tested and approved, you can then copy this Development App to a Production App. Of course you can start with a Production App right away as well.


    Development and Production Apps are linked to several Application Build Types. For a complete overview, see:

    1.3. Essential app options

    The following information should be entered:

    • Application Name
    • Bundle Identifier: This should be a reverse DNS name like com.twixlmedia.appname - only lowercase characters, numbers and dots should be used.
    • Application Title: Use this to customize the title shown in the home screen of your app. Leave empty to use the application name
    • Application Icon: Upload an icon that will be displayed in your app list - it will be resized automatically
    • Support Email: The email address where the support emails should be sent to.

    2. App options overview

    When you select 'Edit application' after your app has been created, here's an overview of all the options that can be set.

    1. Application Details: app name and bundle identifier - both are required fields when creating an app
    2. Metadata: here you can enter a title for your app, select an icon and enter a support e-mail address - this is also part of the new app creation process
    3. Privacy Policy: if you publish you app in the Apple App Store or Google Play Store, a Privacy Policy URL for your app is required.
    4. Search / Downloads: See this article for more info.
    5. Supported orientations (Android): Set the orientations you intend to support for Android tablets and phones. On iOS, orientation changes are handled automatically, and also support using your app in Split View on iPad.
    6. Navigation Toolbar: Set toolbar background color, toolbar foreground colors (i.e. for displaying the title), toolbar tint color (for navigation actions), app tint color (for messages in the app). For the Toolbar, you can also select custom fonts - see more on this here.
    7. Google Analytics Key: You can add a Google (Firebase Analytics) Key for your iOS and Android App and also for the Browser Client. Also see read this info about the Browser Client.
    8. Application behavior:
      • Prompt for App Store Rating: Prompts the user to rate your app in the App Store.
      • Keep All Data Offline: With this option enabled, an app will be forced to download all available content when starting up for the first time. See this article for more info.
      • Sharing on Social Media: When allowing sharing on social media, users can share articles. For more info, see this article.
      • Encrypt PDF Files: Enables on-the-fly encryption for PDF content items. That way, PDF files are protected on mobile devices (most relevant on 'open' systems like Android).
      • Externally Managed Content: Enable this when you have an external system that manages the content. This puts the content items and collections of your app in read-only mode on the Twixl Distribution Platform. For more info, see this article.
    9. Allow Users to access this Application:
      • Here you can define which other users can access this app. More info about Managing Users can be found here.


    Google Analytics for our Browser Client are actually Firebase Analytics but Google still calls them Google Analytics (that's confusing, we know).

    To generate a Google Analytics Key:

    1. Login to analytics.google.com
    2. Create a new Property of type Web
    3. Add a View for Web to the Property
    4. If needed, you can link this new Property to the old native Google Analytics property you used before. Look for the option User existing on-page tag

    Was this article helpful?

    0 out of 2 found this helpful