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).
Related
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 4 years ago.
Improve this question
this may be a simple question but i really want to know. When building an app, what is the cons of using a third party tool, for example photobrowsers, side menu or etc. The pros are of course, easy to implement and less headache to do on own but what about the cons?
let's take a scenario, if company ABC made an app and used many third party tools. One day it expanded and became a big company, will it face legal issues from using them?
As long as you adhere to the licenses etc. of tools or libraries you consume, legal matters should not enter into the equation. It's rare that companies get anywhere by suing those who use their products as intended.
I usually see it as both the pro and the con is "you didn't build it yourself". On the plus side it's work you didn't have to do and don't need to maintain. On the minus, you can't control what it is: it's not purpose-built for your use case and may not exactly match what you need.
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
I've recently started using groovy as an alternative to Java and I would like to develop Android apps in groovy. All the examples I have investigated seem to be quite old.
So I was wondering if it is possible to develop Android apps in groovy?
It's a great idea, and it's been tried with partial success - there was a project called DiscoBot that had things partially working - see http://skillsmatter.com/podcast/groovy-grails/groovy-android
However, it's a difficult proposition though, both because of the size of the Groovy runtime, and because much of what Groovy does to implement a dynamic language is not fully supported by the Dalvik VM.
That said, it is being worked on.
I'm guessing that the reason that you got some 'close' votes here is because you could have found all of this information for yourself with a quick search in your favorite web search engine.
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'm on the verge of releasing an app into the Android and WP7 marketplaces (and hopefully iPhone soon after).
The app in the marketplace will be free, but there will be features available for a monthly subscription. Since this won't be running through the marketplace like it would if I was simply charging for the app download, I have to set up this billing myself. Unfortunately, this is something I know very little about. What's the quickest path to do this?
Thanks!
Best way to do this is to go with a Subscription Billing System. We've looked at a few of them and decided between ChargeBee and Zuora. As our model is more complex, we went with Zuora. For your requirement, ChargeBee should be a good option. As they are still in the Beta stage, they should be able to help with customization if required. But I don't think that would be necessary.
http://www.chargebee.com
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.