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 }" wrote:
> On 1 August
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
higher
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 t
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, whic
Hi there,
I have an app on Android Market right now with a minSdkVersion
corresponding to Android 1.6. I'd like to make an update that is only
visible to users of Android 2.2 and higher (there is a good reason for
this, which I will explain below). So I have two questions:
- First, if I publish a
Hi there. I too am trying to make use of the
manifest directive to support both newer and older phones, but I seem
to be hitting a catch-22.
In order to use , you must build with the 1.6 SDK or
higher. However, the output of such a build will not install on my
Android 1.5 developer device. The ou
6 matches
Mail list logo
