Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Distributing (and updating) an enterprise Android application that is to be used in-house only [closed]

Tags:

I'm building an Android application for an enterprise customer that will be used in-house (and not sold). Though we have additional auth measures, I'd rather not deploy the application on the marketplace.

I was just wondering if anybody had previously done something of this sort, and had suggestions.

Also, If we were to upload the APKs, how could we handle updates to our software? As I understand it, the Android marketplace handles update notifications if the Marketplace is used. Would we have to write a service of our own to monitor for updates?

like image 998
Siddhu Avatar asked Jun 02 '11 16:06

Siddhu


People also ask

What is enterprise application in Android?

Android Enterprise is a Google-led initiative to enable the use of Android devices and apps in the workplace. The program offers APIs and other tools for developers to integrate support for Android into their enterprise mobility management (EMM) solutions.

How the apps are distributed on mobile market place?

You distribute your Android apps to users in any way you want, using any distribution approach or combination of approaches that meets your needs. From publishing in an app marketplace to serving your apps from a web site or emailing them directly users, you are never locked into any particular distribution platform.


1 Answers

A Google I/O 2011 talk, "Taking Android to Work", covers this problem, but does not offer a very satisfying solution. See the talk on YouTube (between about 30:00 and 36:00), or the PDF Slides.

In summary, the talk suggests building an "Internal App Directory", which is essentially a private app market for an organisation. The PackageManager API can be used for querying the installed applications, and installing new applications. You'll have to periodically check for updates yourself.

I would think this is a common problem, but unfortunately I haven't found any good existing solutions for this, and it seems like you'll need to implement all of this yourself (both client-side and server-side). You can check out this question, but I didn't find the listed solutions appealing.

If the organisation only uses a single organisation-wide Android application, it is probably simpler to implement all of this in the application itself, instead of in an "Internal App Directory".

Update 2012/03/23:

Since my first answer I checked out some mobile device management (MDM) solutions. Two of them I considered were AirWatch and MaaS360. Both of them have built-in enterprise app stores, which you can use to distribute the apps. The largest issue with them is the pricing - AirWatch is the cheapest decent MDM solution I've found, at $3/user/month.

If the enterprise wants full MDM functionality (many enterprises do), and can afford it, go for an MDM solution with a built-in enterprise app store. If you only want updates for a single application, Pushlink as posted by Victor Hugo seems perfect.

like image 67
Ralf Avatar answered Oct 15 '22 10:10

Ralf