Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I've published an Android applications on the Android market and now have an update to do.
I want to know if any of you have already done that, and what experience can you share about it :
How to manage version conflicts ?
What to do with databases ?
Can you make appear a message with "what's new" if it's an update, but nothing it's a new installation ?
Should you backup old data before updating, and how ?
Did you run into any trouble and how did you solve it ?
Can update be partial (like, just a patch) ?
Any advice is welcome.
I'll comment only on what I've experienced:
Android market will not let you have package version conflicts. It examines the package and if the new version is less than or equal to the old version it will refuse the upload (it did with me).
All updates appear as a patch to the user, although I believe they aredownloading a whole new package and not just the changed bytecode.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I have an Android application,already live on playstore, but due to certain changes in the requirement, I have to add one more activity to the app without updating the app again on playstore.
Also for future projects, how can I make the application update some part of its code, or patch a broken code without updating the app on the store.
In advance thank you!!
You cannot do that, unless your app is explicitly designed and written to support i.e. dynamic UI based on your external resoiurces/files etc. This is not the case so answer is "no".
or patch a broken code without updating the app on the store
You can download APK from external source and init its installation.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
How can a double version of an app be realized, for instance a Free and a Premium one?
Is possible to have some controls, like EditTexts, Buttonms, etc, be shown only in a Premium version?
Of course it is. You can do findViewById(R.id.premium).setVisible(View.GONE) in your free app to hide controls that should only be visible in the premium version.
You might also be interested in In App Billing Documentation.
I think the best way is separating both versions into two library projects; so in one you would add just the free version and in the other one the full version.
Each of them should have their own structural files, such as drawable resources, Manifest... You'll be able to find more info in several other StackOverflow questions such as this (just googleing a little you'll find a bunch).
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I have an app on the store that I want my users to upgrade quickly. I have made several updates before and things went smoothly: in about a week 80% of my users had the new app. Now, however, I have more users and they are taking longer to update to the new version. It has been about 3 weeks and only 55% are using the new app. I know that I could put out a message within the app saying "hey you should really update the app", but I'm also wondering: If I release a small bug-fix update do you think I will get more people to update? If I release again will a new notification go to them saying they have an update available for my app? Is this a good idea?
Thanks.
This question is too broad and doesn't really belong here, but anyway:
I would not update your app more frequently if it's not necessary, and I would especially not nag your users by frequently displaying an update notification if it's just bugfixes or minor improvements. (It's different if your users really need to update for functionality, but I guess that's not the case here).
Simply put: it's not in your hands if your users update, and imho it shouldn't be. Provide value with each update, and if your users feel it's worth it, they will update.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I've got an app that needs developing cross platform with sporadic updates depending on season and to go with PR, etc.
I know I can set an initial availibility date for iPhone distribution and I can do the same for updates. However I cant seem to find if I can do this with the PlayStore. I'll need to time the initial release then time updates depending on seasons and would like to do this in advance.
Anyone know if its similar? If you know if similar can be done on Windows Phone OS too that would be an extra bonus! hehe
You can't. You have to submit your APK a few hours before you want the App to be available in the Play Store. Play Store does not provide a "publish from date".
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I want to develop an app like this. Is there an API for this?
http://ipclineapro.com/ticketscan/
The TicketScan app is made specifically for the Webconnex platform (i.e someone buys tickets on Webconnex). So it isn't intended for other platforms, which is why it only provides a ticket number.
We do not, as of yet, have an Android app. When we first created TicketScan it only supported the Linea Pro (iPod accessory, now also for iPhone), but we later added support for QRCodes for the camera.
If you are wanting to make an Android app that works with our platform, we do have an internal REST based service the app uses. This service isn't documented, and we don't intend to release it publicly in its current form, partly because it may be changed in the near future.
Currently we are working on a revamp of our platform, which will have a slew of API's available.
I recieved the reply to my mail from Webconnex. They said that there is no API open for us to use.