When I lead mobile business intelligence projects, part of my job is to rebrand and compile the MicroStrategy Mobile iOS SDK into an .ipa file. In layman’s terms, rebranding MicroStrategy Mobile consists of exchanging MicroStrategy’s mobile app’s name, icon, launch image, and login page with your organization’s using the mobile iOS SDK.
There are other customization options available with mobile iOS SDK, but I will not be covering them in this article. What I will be covering in this article is the basic rebranding of the mobile iOS SDK, its hardware and software requirements, high-level steps on how to sign/compile the app using Xcode to generate the .ipa app file, and the distribution of the app over the air or through an Enterprise Mobility Management (EMM) platform like VMware AirWatch or MobileIron.
The two images below show a Mobile BI app (AESalazar) that was rebranded and compiled using the MicroStrategy Mobile for iPad iOS SDK.
Over the years, I’ve developed the table below with a high-level comprehensive list of requirements to help MicroStrategy Professionals, Project Managers, and anyone involved in a Mobile BI project understand what is required to successfully rebrand and compile the MicroStrategy Mobile iOS SDK.
1. Update the Bundle Identifier.
2. Update the Version.
3. Update the Preferences XML file to point to your environment.
4. Update the App Icons.
5. Update the Launch Images.
6. Update the 4 Login Page Background Images (starburst-landscape.png, firstname.lastname@example.org, starburst-portrait.png, email@example.com). Location of images: MicroStrategyMobile > Resource > FinalBundle.bundle > Contents > Resources.
7. Update the Bundle Display Name (this is the app name in iOS).
8. Update the URL Schemes.
9. Verify that the Code Signing Identity and Provision Profile match.
10. Export the app for Enterprise Deployment and save the .ipa file.
1. Share the .ipa app file with your EMM/Systems Administrator.
2. Test app install, performance, and functionality.
3. If the app security is driven by a persona/user role (Executive, VP, Director, Manager, Associate...), create test user IDs for each role and test security and functionality.
4. Make sure the SDK version the app is compiled with is compatible with your existing version of MicroStrategy.
5. Check with MicroStrategy Support if the Xcode version that will be used to compile the app is supported by the SDK version.
6. Load test the infrastructure with the number of users it is intended to support.
7. Train your users how to use the annotate and share feature to report any bugs or issues with the mobile app.
8. Disable the ability via your EMM for users to upgrade to the latest iOS version as the rebranded app may not work correctly in the new iOS version.
9. To ensure a successful rollout of the Mobile BI app, assign dedicated resources to monitor and quickly resolve any reported bugs or issues.
10. Configure Enterprise Manager to track usage and make continuous improvements to the Mobile BI app.
Helpful Links: iOS 11 Support for MicroStrategy Mobile