The following aspects of your app will need to be reviewed. This document explains the aspects of maintenance and how regularly Fliplet suggests the different types of maintenance is performed.

  1. Native app updates

  2. Content updates

  3. Functionality updates

  4. Functionality updates

  5. Security checks

  6. Competition

1. Native app updates

Risk description: Operating system, device changes, native app code maintenance, app store changes, expired distribution certificates and new features added to the native app code are resolved by updating native apps.

Recommended frequency: Every 6 months.

Notes: At a minimum apps will need to be reviewed and possibly update Android Q2-Q3. iOS Q3 due to updates from Google and Apple

Process: Rebuild the app in Fliplet Studio and submit the new build to the app store or enterprise app store for distribution.

 

2. Content updates

Risk description: Content will slowly go out of date over time and should be reviewed to ensure it is still relevant or updates applied.

Recommended frequency: Every 6 months.

Notes: Content can have different stakeholders so multiple people may need to review an app to ensure all content is reviewed.

Process: Update the content in Fliplet Studio and publish your changes. Test the live app to make sure it has received the updates.

 

3. Functionality updates

Risk description: Functionality can sometimes break depending on changes to the operating system, device, code, or data. To ensure this doesn’t happen functionality should be reviewed and potentially updated.

Recommended frequency: Every 6 months at the latest. Every month is preferred.

Notes: Functionality issues can be broad and the best way to avoid issues is to use your own app regularly and demo or use the app with customers.

Process: Make the functional updates in Fliplet Studio, test them in Preview mode and Fliplet Viewer, then publish the changes to the live app via Fliplet Studio. It’s important to test on all platforms where your app is available (iOS, Android and/or web).

 

4. Functionality upgrades

Risk description: Over time functionality will become old, outdated or too simple. Apple, in particular, has been progressively increasing the expectations they have of apps and do not allow app updates that do not meet their guidelines. To address these risks apps should be enhanced periodically to ensure users have a reason to continue using the app and that the app remains competitive.

Recommended frequency: Every 6 months at a minimum.

Notes: Functionality is usually a mixture of features and content although functionality can often be copied and tweaked from other apps or Fliplet app templates to reduce the technical skills required.

Process: Make the functional updates in Fliplet Studio, test them in Preview mode and Fliplet Viewer, then publish the changes to the live app via Fliplet Studio.

 

5. Security checks

Risk description: App security, like features, should be tested regularly to ensure there are not issues. This includes testing the security and reviewing the apps usage to ensure any security issues are detected and addressed such as high usage from a specific users, lots of new users, users accessing the app without appropriate security, and other anomalies.

Recommended frequency: Every 6 months at a minimum.

Notes: Assess issues by reviewing analytics usage.

Process: Make the updates in Fliplet Studio, test them in Preview mode and Fliplet Viewer, then publish the changes to the live app via Fliplet Studio.

 

6. Competition

Risk description: Competitors who produce a superior app can result in reduced use of your app. Apps can be superior because they offer new features, remove friction such as do not require a login, or position and market their app in a new way.

Recommended frequency: Every 6 months.

Notes: When reviewing competitors it’s important to predict where the market is going, not just take the current action of competitors as the only thing you need to assess. It is better to assume competitors will be continuing to evolve their apps than assume they won’t.

Process: Review apps via the App Store or use Google to find press releases or news from competitors about similar apps. Review their promotional materials