We’re noticing a trend with respect to enterprise app stores, one that’s encouraging because it demonstrates increasing endorsement of app stores themselves, but one that’s also concerning because it might be clouding perspective on what’s really required for app store implementation success.
We all know what an app store is (the internal distribution and management of mobile apps, both privately developed and publicly available iOS and Android apps ). And more and more of us know it’s something we want for our organization. Cutting to the chase of app store implementation, then, basically boils down to grabbing something off the shelf or doing it yourself — buy vs. build, in short.
Here’s where it gets troublesome. When it comes to resolving that build vs. buy decision, we’ve noticed that the lead decision-makers tend to be folks who are already in development or IT. They know how to deploy servers, write software, etc. That means they are already technically adept, and understand the resource demands an app store implementation might require. They know how to point to a file or an XML document and satisfy requirements for Android or iOS. It’s not rocket science, right? That certainly makes the case for a build. Why pay a vendor and deprive a capable techie in your organization with the chance to play in a new sandbox?
But consider that their ability might be the best example of a double-edged sword in all of IT. Yes, they understand the very real technical requirements, which leads them to the dangerous conclusion that enterprise app store builds are easy. That kind of thinking, in our experience, puts them on the wrong side of the buy vs. build dilemma. Sure, installs are easy, even fun. But once the store is “open for business”, as we’ve said before, the real work now begins. The tech savvy who built their own enterprise app store are now faced with the demanding reality of managing and maintaining that store — something often overlooked during the initial excitement of the in-house build.
Open the doors on your enterprise app store and aside from ensuring that it is well stocked with fresh apps (itself an ongoing requirement) you have to address AD, LDAP, VPP, user permissions, upgrades, authentication, and more. Setting up a web server so it has access to a file is without question old hat for most, but what about the fundamental follow-through of bringing in security? Prior even to these concerns is the bedrock UX requirement of making sure it runs properly on myriad devices, via different browsers, diverse screen resolutions and keyboard layouts, and just generally cooperates with a multi-vendor environment.
The complexities become evident pretty fast, which is why a bit of planning and preparation can go a long way toward making the right build vs. buy decision. Think of it like renovating a room in your house. Maybe it’s time to transform that unfinished basement into the perfect man-cave, and when your old college roommate tells you he can wire up the entertainment system for a case of beer and a pizza, you’re all for it. You get the speakers set up, the big-screen on the wall — but wait, the fiber optic connection is on the other side of the room. And you don’t have cable anymore. You’re going to use satellite and Internet for all your content. Well, plug in the HD antenna and at least you get local stations. That’s cool, right?
Clearly what’s begun in earnest can end in frustration if you’re not seeing the big picture. That expansive vision is critical for effective enterprise app store implementation, especially when you need to confirm how it generates revenue. In the same way companies evaluate their Intranets or platforms like SharePoint, you’ll need to sit down with your CIO, or whomever manages the budget, and convince them that it’s worth the engineering dollars and technical time to first set up your enterprise app store, but then more importantly to maintain your enterprise app store. To ensure success, you’ll need resources devoted to fine-tuning its idiosyncrasies, aligning platforms, addressing customer support and so many other needs. Is that the best use of your R&D dollars? If you want to change your job title to “enterprise app store manager” then perhaps it is. But if you’d rather stay focused on the mission of your particular organization, it’s worth it to weigh the advantages of buying an app store vs. building one yourself.
Talking App Stores at MoDevTablet Tomorrow
If you’d like to pursue further conversation on enterprise app stores, be sure to catch up with me tomorrow at MoDevTablet. I’ll be leading a discussion panel and making a presentation on app store options. Hope to see you there!
