Spencer provides you with a native (installable) iOS and Android mobile app.
These apps are skinned to meet your brand identity, based on the Spencer rebrandability platform.
The mobile apps can be distributed using 2 mechanisms:
Public app store distribution
The preferred approach to distributing Spencer, across iOS and Android is to leverage the respective public app store per platform:
- How to enable App Store Distribution for iOS
- How to enable Google Play Store Distribution for Android
Users can simply browse the native app store on their device, search for and install Spencer – just like they would install any other app. It's easy, straightforward and most importantly, familiar. Subsequent updates are handled effortlessly and often fully behind the scenes. This option is superior to all others in terms of penetration and end-user experience.
Many enterprises opt for a (Mobile) Device Management solution to provision their corporate devices at scale, while maintaining efficiency, security, and visibility. If everyone is set up with a corporate MDM-enabled device, it’s also a really simple approach. MDM’s Achilles heel, however, is that more often than not, it suffers from very low penetration rates. Unfortunately, if few people have an MDM-enabled device, Spencer will never be able to reach its full audience potential.
In the MDM distribution flow, Spencer will deliver binary installation files (.ipa, .apk) to the customer’s MDM admin. Spencer delivered binaries are known to adhere to the binary requirements of most industry-standard MDM suites (e.g. Microsoft Intune, Microsoft SCCM, VMware Airwatch, MobileIron).
That said, the customer is expected to take full control of their enterprise (M)DM solution, incl binary requirements, initial distribution, update distribution, and more. Spencer does not claim expertise nor will it deliver support services to distribute apps via (M)DM – beyond binary delivery.
Ideally, Spencer leverages the beta-distribution features of both the Apple App Store (TestFlight) and the Google Play Store (Beta Tests). If that's not possible, we turn to Crashlytics, that's a Google-owned service that allows Spencer to distribute pre-release versions of the app to trusted testers.
If you believe you have a case wherein Crashlytics distribution is required, please contact your Customer Success Manager. You’ll be asked to specify a test audience (list of tester email addresses) and share with them this complete installation manual. Testers will then receive a personalized invitation email enabling them to download, install, and subsequently update pre-release validation builds.