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 transfer. Much of this is from users of
the free app. So I would much prefer to pack all this stuff into
the .apk and not worry about it.
On Aug 1, 5:15 am, "{ Devdroid }" <[email protected]> wrote:
> > servers at first-run. However, this means that I must maintain
> > external infrastructure,
>
> Regular vhost shall do + some code to fetch data over HTTP.
> Nothing more is required unless you want additional server logic.
>
> > and it's also a bad experience for users who
> > must download the app, then start another download sequence (I already
> > have had several complaints about this in my user comments).
>
> There wil always be complains no matter what you do. Just make
> clear statament in app description that after installation app needs
> to fetch extra XX MB of data, so those who dislike that will drop
> will know in advance
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
