Cool, thanks for the detailed reply. I guess I'll just have to make do
with what I have for now.
But if there are any Android OS developers reading, this would be a
really great feature to include in the future!
Brian
On Aug 1, 12:38 pm, { Devdroid } webnet.andr...@gmail.com wrote:
On 1 August
Or leave minSdkVersion where it is and use reflection to add features
from 2.2, testing at runtine obviously.
More info here:
http://developer.android.com/resources/articles/backward-compatibility.html
On Aug 1, 1:12 pm, { Devdroid } webnet.andr...@gmail.com wrote:
I have an app on Android
Thanks for the reply. The problem with making separate apps is that
existing customers will not be able to upgrade for free. And the code
refactoring idea doesn't work, because the main point of the exercise
is that I want the new version to contain all those resource files in
the .apk itself,
Actually, I wanted geo-load-balancing, so I'm using a content
distribution network. Plus, you have to consider re-downloads of the
content over several years by existing customers. At scale, based on
patterns I've seen on other platforms, I expect it to cost a couple
hundred bucks a month in data
Richard,
Thanks for the link to the article -- I hadn't seen that one. However,
it doesn't address my core need, which is to have the existing version
stay small, and the the new version have all resources packed inside
it.
Does anyone know how it actually works to publish an update with a
On 1 August 2010 19:25, Brian Rak seattlenice...@gmail.com wrote:
Thanks for the reply. The problem with making separate apps is that
existing customers will not be able to upgrade for free. And the code
refactoring idea doesn't work, because the main point of the exercise
is that I want the
6 matches
Mail list logo
