分发（和更新）的企业Android应用程序是在内部使用仅 [英] Distributing (and updating) an enterprise Android application that is to be used in-house only
问题描述
我要建一个Android应用程序的企业客户，将在内部使用（而非出售）。虽然我们有额外的身份验证措施，我宁愿不部署在市场上的应用程序。
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.
我只是想知道如果任何人有previously做了一些这样的了，只好建议。
I was just wondering if anybody had previously done something of this sort, and had suggestions.
此外，如果我们上传的APK，我们怎么能处理更新我们的软件吗？据我了解，在Android市场上处理更新通知，如果市场被使用。难道我们必须写我们自己的服务来监视更新？
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?
推荐答案
一个谷歌I / O 2011的谈话，以Android的工作，涵盖了这一问题，但没有提供一个非常令人满意的解决方案。见谈话的 YouTube上（约30:00和36:00），或<一href="http://static.googleusercontent.com/external_content/untrusted_dlcp/www.google.com/en//events/io/2011/static/$p$psofiles/taking_android_to_work.pdf">PDF幻灯片。
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.
在综上所述，谈话建议建立一个内部应用指南，这实质上是一个私人应用的市场的一个组织。所述 PackageManager API 的可用于查询安装的应用程序，并安装新的应用程序。你必须定期检查更新自己。
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.
如果该组织只使用一个单一的组织范围内的Android应用程序，它可能是容易实现在应用程序本身所有这一切，而不是在一个内部应用程序目录。
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".
更新2012/03/23：
由于我的我查了一些移动设备管理（MDM）解决方案的第一个答案。他们两个我认为是 AirWatch 和 MaaS360 。他们两人都有内置的企业应用程序商店，你可以用它来分发应用程序。他们最大的问题是定价 - AirWatch是最便宜的体面的MDM解决方案，我发现，在$ 3 /用户/月
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.
如果企业要充分MDM功能（很多企业做的），并且可以负担得起，去与MDM解决方案内置的企业应用程序商店。如果你只想要一个单一的应用程序更新， Pushlink 为发表雨果似乎完美。
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.
这篇关于分发（和更新）的企业Android应用程序是在内部使用仅的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
