re: the data format being incompatible.

that fact that the format for beta and 1.0 data isn't 100% compatible doesn't stop you from writing import / export code. that's what import / export means. bridging one data format to another.

you obviously have the code to read beta settings and the code to write 1.0 settings. you should have added export to beta that wrote the data into an intermediary format. and had import in 1.0 that read the intermediary format and wrote it into the 1.0 format.

this is the sort of thing i expect in a paid, $10 app. as for adding back up and restore, i'd vote against it. if my phone crashes and i lose my locale data, that's the very, very least of my concerns.

the time for this feature was 1.0, it's of little use now.

I encourage you to provide backup support for your application by integrating with an application called MyBackup Pro, developed by RerWare, LLC. They have instructions on how you can integrate with their application for backup and restore functionality at the following link: http://www.rerware.com/MyBackup/integration.html
You can also contact their support team by email with any questions at the following email address: Support@RerWare.com

Thank you for a wonderful application, and I look forward to having the ability to backup and restore your application's data using MyBackup Pro.

I agree with Carter that Backups should be implemented only when they can be implemented properly. Therefore I suggest the following features for backup functionality:

* Backup files should carry version used to create them.
* Backup Data convert plugins can be developed and maintained by first- or third-party. Locale should simply allow that when a backup is imported, a backup data convert plugin can be called to chew the data. The backup data convert plugin can read the version of the Backup, knows the current version and should be able to convert or strip uncompatible and deprecated conditions.

Allow third party applications to add new Locale rules using intents. This will allow third party apps to automatically add default rules useful for novice and casual users (i.e. an app that can be launched via Locale can automatically set Locale to launch it at certain times, i.e. apk backuper, etc.). Precaution should be taken against dangerous rules implemented by third party apps - all rules added by third party apps should be manually approved within Locale before activated (i.e. they are added as deactivated rules, and must be manually activated to work).

I guess I'm not sure why this would be so hard, if it can be cleanly uninstalled, it can be copied. If the top of the code used a version check and a pop up to collect file/directory name, and backups are version specific, and a pop up says you have to have all the plugins installed that you had (spiffy it it listed them), it would be just a copy to an accessible part of the sd card. For me it's just a matter of a copy in a backup place that's moveable to appdata. If you wanted to get extra accomodating, the backup could include the apk of the version of the backup and revert to import the data, and then advise an update.

Don't forget, though, if the flashers are impressed and use an app, devs make cool ROMs and apps that work with a package because the perceived need is there. Given that this is an open source platform, that's where the cutting edge is. It's not as much with The originator as it would be with a closed source platform.