On 03/08/2012 10:23 PM, Mark Murphy wrote:
In most cases, IMHO, it's not the developer's data. It's the user's
data.
Agreed.
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.
Given the context, I'd also consider security implications.
Email message sizes are typically limited by servers to around 30Mb,
meaning 20-something megabytes of useful data if using base64 encoding.
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,
It just depends on the data.
Backup / restore functionality within one app is still valuable in cases
where the user gets a new device or resets his existing one (assuming
data loss), wishes to sync data between devices, or to protect against
unexpected device / data loss.
For example: Android can back up WiFI networks configured on the device,
including their passwords, but there is no web app to see this data.
or something to allow the user
to use the backup.
Yep, that's the point, isn't it?
The "something" can be the app's restore functionality.
-- K
--
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
