I haven’t written about about Appaloosa before, but now is a good time to take a look. Most of their customers are in Europe, but this year they plan to expand their marketing and sales efforts to the US. As for Appdome, you’ll remember them from my profile back in October. For this article I spoke to Appaloosa CEO Julien Ott, as well as the team from Appdome.
Appaloosa was created in 2011 as an enterprise app distribution tool at Octo, a French consulting company. (Octo was acquired by Accenture last fall.) In 2014 Appaloosa was productized and launched as a subsidiary.
Here are the basics of what Appaloosa offers:
- Cloud-based app distribution platform with granular app assignments.
- Integration with various development tools and app signing.
- Native app catalogue clients for iOS, Android, and Windows Phone, with push notifications and feedback collection.
- iOS and Android SDKs to ensure that apps are up to date, devices and users are authorized, and that devices are not jailbroken or rooted.
Appaloosa found that customers would often receive compiled app binaries from contract developers, and then need a way to integrate SDKs, to they turned to Appdome. Appdome’s “app fusion” tool can integrate third-party SDKs into pre-compiled apps. (It’s like app wrapping, but can work with a variety of SDKs.) Appdome also has their own MAM features that can be embedded into precompiled apps.
Here’s the process for Appaloosa customers:
- Upload apps (that customers are distributing with the permission of the developer, of course) to Appdome’s platform.
- Select Appaloosa SDK features to integrate.
- Also select Appdome MAM features to integrate, like data loss prevention, encryption at rest, or other security checks like anti-tampering. These are freestanding, so once they’re added, you don’t need Appdome for ongoing management.)
- Run the “fusion” process.
- Transfer the finished app binary over to Appaloosa for distributed and management.
Beyond this, Appaloosa is now also supporting Android for Work (now just referred to as Android’s enterprise capabilities), including the app-based mode for Android 4.x and Work Profile mode for Android 5.0 and higher. Remember that the MAM capabilities in recent versions of Android differ from SDK and app-wrapping techniques, in that they depend on device-level frameworks. (Learn about the differences here). Appaloosa considers themselves a MAM-oriented vendor, but find that the strong work and personal separation in recent versions of Android aligns well with their approach.
As I wrote recently, MAM is an important part of most EMM deployments; so it’s natural that more vendors like Appaloosa and Appdome are arriving to take advantage of this. This partnership is also another vote for Appdome’s SDK fusion concept. I’ll be following both companies closely this year.