Testing your app offers the following:

  1. See how the app will look and feel for users before publishing
  2. Allow time to find and correct any mistakes before the app is live.

Testing your app

  1. After making changes to your app in Fliplet Studio and before publishing your changes to the live app:

    1. Test the app in Preview mode.

    2. Test the app in Fliplet Viewer on iOS and Android. If the changes affect security or the initial screens it is recommended you delete the app in the Fliplet Viewer and download it again otherwise you may not have access to the security or initial screens.

  2. If the changes are OK publish the app inline with the following criteria:

    1. Notify your colleagues involved in the project that you are going to publish an update and ask them to review it once it is live.

    2. Only publish when you have time to review the update immediately.

    3. Review the update in the mobile and web app:

      1. On all mobile platforms – iOS and Android.

      2. On all web browsers that your users could use e.g. Chrome or IE.

    4. Publish with plenty of time to undo the change if there are problems.

    5. If your checks pass ask your colleagues if they have successfully received the update.

Note: some changes to the app will be higher risk than others.

High-risk changes include:

  1. New features.

  2. New or removal of screens.

  3. Altering links or key screens.

  4. Modifying security rules.

  5. Modify data structures.

Low-risk changes include:

  1. Text or image changes within a screen without modifying links or the screen structure.

  2. Adding or removing records to a data source without modifying the data source structure.

What does not require you to publish an update:

  1. Data source changes, most components retrieve data source updates without requiring the app to be published.

  2. Components that retrieve data from an external data source, such as RSS or login components that always retrieve the latest data from the server when used.