I'm currently building an app for a client who wants to manage the apk afterwards, without publishing it on the Android market. He wants to provide the app to a limited number of users.
- To do so, I've first thought making a second app that will manage the updates of the first one.
- Then I thought it was a bit complicated and I found Pushlink. This is exactly what I need except one part of the terms and conditions that I fear :
1.1 PushLink reserves the right to update and change the Terms of Service from time to time without notice.
I've got actually two questions :
- Does anyone of you have experience using Pushlink, how supported is it?
- Is there any alternative to Pushlink?
Many thanks.
Romain
An alternative to your proposed solution would be to implement your own internal updating logic.
I've done this myself and it's very simple to maintain.
- Have a plain text file on a server that can be accessed from your application.
- This file will contain the most up to date version number.
- Every so often (maybe once or twice a week) check the server to see if the version numbers differ (Server # > In app #).
- Download your new APK from the server onto the SD card.
- Once you finish downloading the file you'll need to launch an intent to install the application. The user will still have to accept to install the update so its not %100 autonomous but you prevent the user from doing anything aside from clicking "Install".
- Check the answer to this question regarding the install intent
Menu
974
