2012/3/8 Kostya Vasilyev <[email protected]>: > Other that that, take a look at various cloud computing platforms, > their terms of service and pricing. Or roll your own web server if you > feel confident enough.
In most cases, IMHO, it's not the developer's data. It's the user's data. Hence, the backup should be made to something the user controls, such as: -- external storage -- DropBox account (via API or Android client) -- email (via attachment) -- etc. The only case where backing it up to a developer-owned server would seem appropriate for user-owned data is if said server also had a Web app, or sync options to other clients, or something to allow the user to use the backup. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 2.5 Available! -- 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
