I am currently working on an Android app and I am wondering which would be the best way to distribute it to customers. I understand that one can create a private channel but I haven't been able to determine whether our customers would be able to use it. From what I've gathered, a private channel is for internal distribution; I wonder if someone without an e-mail account from our company would be able to download it this way?
If Google Play is not the answer, what would you do? I know the app can be distributed through e-mail or links to download it but I'd rather avoid having users change their devices' configuration to allow installing APK from unknown sources.
Not sure what your beef with Google Play is but even if you're not intending to publish the app at all, you can still take advantage of the beta testing mechanism -- you can distribute a Google Play to limited audience -- i.e. a list of google accounts.
Apart from that, if I'm not mistaken TestFlight supports Android package distribution. Looks like they dropped Android support
Related
I have a app created in xamarin forms, I already know how to create the APK, the app is to be used internally, i dont want to publish to the appstore, how can the app be update when is available a new version ?
Depending on your resources at hand and requirements, you have a couple of options. These options include, but are certainly not limited to:
Visual Studio Mobile Center (link): probably the most obvious choice. Out of the box support for Xamarin, and 'just works'. You can set up different groups of users, add analytics and crash reporting, etc. In the future you might be able to take your configuration to its big brother: VSTS. But beware! The product is in preview right now. Preview in Microsoft-land means free for now, but doesn't have to be in the future. While I expect it not to cost much/anything for basic functionality, it is something to be aware of. Not sure on this, but I think you need to invite your users by hand, so you have to know who you want to invite.
Google Play Store (link): It's kind of a mis-use, but you could of course leverage the Google Play Stores capabilites for Alpha/Beta testing. Also here you have the ability to create groups and have some basic reporting options. In terms of delivering your app you have some nice options here like A/B testing and unlike Mobile Center (again, I didn't verify this) you can setup a link with which people can enroll themselves. Depending on your needs, this might be nice. In terms of costs, this will set you back 25 dollars once. And you could develop and distribute other apps if you'd like.
Manual: send the APK file manually or hosting it on a shared location. I would prefer this least of all. People are not notified of any updates and you don't have any insights apart from something you might have incorporated in your app. Also you don't have any control over who installs or sees the app, etc.
But of course the prefered way would be to do it through the Google Play enterprise program. See this website. This provides you and your end-users with a private app store basically. Or as they say:
A managed version of Google Play is used by enterprises and their employees to access a rich ecosystem of work and productivity apps.
You can have private apps, only available for your targeted audience and still leverage the power of the Google Play store. The experience for your end-users will be unified with the regular app store.
I couldn't find a straight answer, but it seems the private apps will also cost just 25 dollars once and is included in the regular Play Store developer license.
You have a good way to do that : Use Beta this a service provided by Fabric, you can upload your app with different versions and get access to different teams in your company. It's easy to use and quick to manage.
Hope it helps.
You have multiple options at your hand:
use Bitrise or Visual Studio Mobile Center (aka HockeyApp) to build and provide a downloadable version of you app
in addiont to Bitrise or VS Mobile Center you can set up your own store. Take a look at Relution for example
build locally on your machine and push it to:
a fileshare
an FTP-site
the user by mail.
I have a subscription based web-service that allows you to monitor industrial machines. It supports Raspberry PI and Android.
Right now, the Android APK is downloaded from my website, but I want to put it in PlayStore to be able to push silent updates (most of the devices running it don't have a screen).
My question is how to make it "hidden" in PlayStore ?
I want only people coming with a link from my website to be able to download it. I want it to not appear in searches or in any Store listings (new apps, popular, etc). The only reason to have it in the store is for silent updates that are not possible in any other way.
I don't know if there is an official solution for this, but Apps with only Alpha and Beta apks are always hidden in the Playstore.
Google Play now allows you a new way to distribute internal applications(Google Play Private Channel):
The Google Play Private Channel for Google Apps (the Private Channel)
allows Google Apps domains to distribute internal Android applications
to their users through the Google Play Store.
Here you can find the announce on Google Enterprise Blog and here the instructions to set up this feature.
I'm building an Android app which for various reasons cannot be listed publicly on the Google Play store.
I have found information about the Google Play Private Channel but if I understand it correctly, this can only be used when all your users are within a Google Apps domain (which mine are not).
Are there any similar methods that I could use to deploy my app (and get the benefit of easy installation for users, an updating mechanism etc.), or is my only option to publish an APK file manually?
From what I can tell, manually publishing APK files is the only choice, but this seems strange to me since my situation must be common for "private" business applications.
In particular, I am concerned that it would look unprofessional to have to guide users through the process of turning on the "Allow installation of apps from unknown sources" setting.
Any advice welcome, thanks!
I would just deploy your app using Google Play "Beta testing and staged rollout":
https://support.google.com/googleplay/android-developer/answer/3131213?hl=en
Your users have to join a Google Group or Google + community that you create so you can limit you audience and make the app non-public on Google Play but still allows your non-public users to update the app via Google Play instead of manual APK installation.
The only downside is that the members of the Google Group or Google + community will only be as private as their Google account provides. So, app users are known to each other but your app will not be public on Google Play.
Can you not use BETA or ALPHA pushes
Is it possible for an android application to act as a custom market place?
The imagined behavior of the app:
Download XYZ app from the built in Google Play Store
Opening XYZ app yields a UI similar to that seen in the Play Store
The user can navigate through XYZ app and select a custom app supported by XYZ to install on their phone
This custom app would not be located on the Play Store and the .apk would be directly installed from the context of the XYZ app/marketplace to the users phone
I did some research and found alternative Android App Stores such as:
Amazon App Store for Android
GetJar
SLideMe
F-Droid
But is it possible to have an alternative marketplace like this that can be accessed from an app that was downloaded from the Google Play Store? Does google allow this type of practice?
So I suppose the heart of my questions is: Is it possible to create an android application that has permissions to install other 3rd party applications directly to a users phone? (without needing to leverage the Play Store or needing to jailbreak the phone)
Thanks in advance for the answers and insights! And please let me know if anything I'm saying doesn't make sense.
(Extra Credit: I would also be curious to learn about the feasibility of doing this with an iOS app as well)
To add to the other answers, you will have problems with some of Google Play's rules. AFAIK they don't allow your app to direct users to a different store. So you won't be able to keep your app on Google Play store in that case.
EDIT
It is not in the Terms and Conditions, as confirmed by #Cumulo Nimbus.
It is in clause 4.5 of the Developer Distribution Agreement:
4.5 Non-Compete. You may not use the Market to distribute or make available any Product whose primary purpose is to facilitate the
distribution of software applications and games for use on Android
devices outside of the Market.
My interpretation of the above was, and still is, that we can't point people to a different app store.
Kudos to #zmarties for pointing me at the Developer Program Policy which links out to the Developer Distribution Agreement. I knew I'd seen this somewhere...
In terms of iOS, Apple does not allow different app stores unless you jailbreak (iOS-speak for rooting) your phone. They are not as open minded as the Google.
Android apps don't need to be rooted in order to install third party apk's. The use just needs to allow this in their settings. The apps you have listed simply instruct their users to enable this setting.
The best example of a third-party "free as in freedom" app store would be F-Droid
Technically it's possible.
The current Developer Program Policy does not seem to prohibit it either - all they have to say on the matter relates to installing "dangerous products" from outside the play store:
Dangerous Products: We don't allow content that harms, interferes with the operation of, or accesses in an unauthorized manner, networks, servers, or other infrastructure.
Malicious scripts and password phishing scams are also prohibited on Google Play, as are apps that cause users to unknowingly download or install apps from sources outside of Google Play.
Having said that, I can't quickly see any alternative apps stores that are themselves in the Play Store.
So, I have a few little android apps now, and am thinking about releasing the in the Amazon App Store. However I have one fundamental question I don't see answered anywhere.
How is Licensing handled if you release the app on the amazon store? I am currently using the Google LVL licensing in my paid apps to ensure the user is licensed to run them. I assume that an app sold on Amazon, isn't going to have any connection to tell Google, hey, this app was purchased, they are licensed, so send them an OK TO RUN status when they launch it. Or am I mistaken?
Does Amazon have its own LVL type code? Or do you just have to forget licensing all together if you want to sell on Amazon?
Simply remove all LVL code from your app (making it unprotected), then select the copy protection radio button when submitting your app to Amazon. They'll add the licensing code to your app before resigning it and releasing it on the Amazon Appstore.
No store-provided licensing code works in other app stores. Many have rolled their own, with varying degrees of simplicity.
I have an app in Android Market. What should I do to ensure the app
works in the Amazon Appstore?
You should make sure that your app does
not include any copy protection functionality (you have the option to
apply Amazon’s DRM technology – see our FAQ on DRM). You should also
take a moment to understand the different signing options available to
you (developer signed or Amazon signed) and choose the option that
works best for your users.
Source