Can anyone share idea?
We have two applications
ApplicationA
ApplicationB
ApplicationA has menu button to call ApplicationB and before this it checks if application is not installed, it popup msg to install from play but now we want to merge these two projects in one.
We are thinking few possibilities but do not know if technically they are possible
1- Make one installer on google play and when user install ApplicationA, ApplicationB should install automatically but I heard it is not possible.
2- Marge these two projects as one but there are many resource files , language files has same name.
Any idea
If you're just linking to the other Apps you has published, one alternative to consider is Deep Links. This will allow your app to link to other specified applications. If the specified application is not installed, the user is prompted to install it via Google Play.
Another simple method, assuming this is for the applications you has published, would be to link to your Product List.
Related
is it possible to create an android application that is meant only for internal use? Basically a private application not meant to be installed by non-approved phones?
If so what is the basic process of deployment? How do you get the app on the employees phone's?
thanks!
The easiest way is to email it to them. Any email with an .apk attachment will get an "Install" button that you can tap to install the app.
Installing from non-market sources needs to be enabled -- which is a bit of a security risk -- but the user will be prompted to turn that on if they need to, and even given a button that will take them right to the appropriate settings page. The whole process is really quite slick. :)
Alternatively, you can copy it to the phone (e.g. after connecting the phone in USB storage mode) and then use a file system app to locate the file and install it.
Emailing it is the easiest way, however.
Edit: I'm assuming you meant private as in "only sent to certain individuals" and you're not actually looking for a method that will prevent the apps from being run on non-approved devices should they end up on one.
There's a proper way to do it now: Google Play Private Channel for Google Apps. You publish app on Private Channel and then send invitations to users. It won't be seen by other users of Google Play.
Option 1
Using Google Play Private Channel is probably the best way, but is useful only for Google Apps users.
Option 2
You can use new Developer dashboard options that let your app be in Alpha or beta phase and is available to only selected google accounts (using groups or google plus circles). Your app can stay in beta indefinitely so not become visible to other users. if you like this method you can also use services like TestFlight.
Option 3
Mail distribution is also ok it's even mentioned in documentation which I find a little bit odd, but I would advise you to use some file storage like Dropbox and just distribute the link to selected people.
Two major ways:
You can either use the non-market application installation method, or adb from a connected PC to install an apk which you distribute as a bare file. The downside is that anyone in possession of the apk can install your application.
Alternatively, you can distribute the application through the android market, but make it require an account on a server you control in order to do anything useful. The upside is that possession of the apk doesn't get an unauthorized user much; the downside is negative ratings from confused randoms, and that you've made your apk very available for interested parties to know about and decompile. (There is or was also a way to put an app on the market but not list it so it was only accessible via a full url, however don't rely on that)
Yes. As of right now I use such a method, I have to manually load the app on the phone, however other techniques can be used. Once loaded the app checks the main server to see if it is up to date. If it is not, it downloads and installs the new version of itself.
If you go to your eclipse workspace and go to yours app's folder, in the bin folder assuming you develop with eclipse, you will find a .apk file somewhere in there. Copy it to the phone and then use something like EZ File Explorer (or something like that) to access your android filesystem, click on the .apk and it will install and be ready to use.
I want to create an app which uses an aidl interface of another app. I was wondering if there is the possibility to make the other app automatically downloaded when the user install my app
See here: http://android.amberfog.com/?p=98
Basically, you cannot directly install the other app, only launch the thing that actually can install it. You would have to include the other apk inside of yours (in your assets folder perhaps), but if it's not your apk, then that's probably not a good idea unless you have the original author's permission.
If that other apk is published on Google Play, you could use PackageManager to check for the presence of the package name of that apk on the device. If you don't find it, invite the user to download the other app from Google Play using an Intent. This post shows you how to open Google Play to a specific app.
I have a bit of situation where I want to use another app features in my main app. I wanted to submit two .apks so user could install both apps at same time. I know how to communicate between two apps. But is it possible to submit two apps so user can get both apps one installation?
Please help.
Yep it's possible, in Developer console you have to first upload your main apk (up to 50MB), and after that you can upload another one, up to 10GB.
http://developer.android.com/google/play/expansion-files.html
Remember how Facebook posted an update awhile back that included a 'Camera' app as well as the regular Facebook app? How can I package 2 apks together in the market so when you download the main application, your actually getting 2 separate applications that are related to each other?
I would rather have my users get both applications at once then trying to hunt for both of them individually. Thanks
Remember how Facebook posted an update awhile back that included a 'Camera' app as well as the regular Facebook app?
No.
How can I package 2 apks together in the market so when you download the main application, your actually getting 2 separate applications that are related to each other?
You can't.
The closest you could get would be to package App B's APK into App A's assets, then when App A is run, copy App B to external storage and initiate an install. This will cost twice the storage space, since you have no way of removing the copy of App B from App A's APK. And, the user will have to go through and approve the install of App B.
My guess is that what you think are two separate applications are really two separate launcher icons, which can be handled in a single APK by having two <activity> elements with the <intent-filter> for MAIN and LAUNCHER, instead of just one.
A very interesting question. I asked that question myself too. But did not get an answer to that. The only thing I could came up with was to use tge (unifficial) Google play store API and then after the User starts the App you could download the second App trough the API. But I assume thats not very elegant
Here's the scenario i am trying to achieve:
Publish/have an app in the Android app store
However - i do not want it to be searchable through the android market search, etc.
The only way people can access the app is if i give them an explicit link to download
Is above possible? If so - how? All FAQs/instrucitons i have seen publish & make it searchable for the whole world - but i want it only accessible through #3 above.
Thanks.
Try this site https://www.push-link.com/, you can upload apk on your private account and only can be accessible thorough automatic generated link and QR code. This service contains user notification on new versions and bug reports.
Two things that are problematic with the link to an APK approach:
Some of the devices out there (I m only aware of the Motorola Atrix) don't have the "Unkown Sources" option, meaning that this won't work on them.
You loose the ability to auto update the app if you want.
I would recommend adding a login process where only your users will have access to the actual application. This way, you still have the Market advantages and only those people can activate the application.
The main disadvantage is that the application will be open to search in the Market, but as far as I know, this won't be a problem since people will immediately uninstall it since they won't be able to activate it.
In your case, what I do is, I dont upload the application to the Market and distribute it from my server.
I mean this is simple, sweet and it also saves my $25 for the market account...
Don't do this. Just publish the APK to your own website, then give the users the URL to the APK, they can download and install it directly. The only thing they'll need to do is ensure that Menu-Settings-Applications-Unknown sources is ticked.