Yeah, the backup thing was a stupid bug on my part (I didn't realize how easy this was to test, or I would have tested). It's fixed in the version I have here, but I'm making some promised storm improvements also, so it won't go out until tomorrow.
ag5bpilot is on the mark with BB development. Though it's unrealistic to do pretty much anything without app signing ($20 from RIM). Maybe a game or something, but as soon as you start wanting to do anything serious a key for signing is necessary. If you're going to try it, definitely use eclipse (you can also use RIM's dev env, but it sucks for development. Debugging and profiling, on the other hand, it's killer for). I used to *hate* java, but eclipse has pretty much fixed that for me. (I don't have to hand type a lot of the cruft java enforces anymore).
I actually like writing for the blackberry, since it's such a limited device (optimization is one of the funnest parts of development for me). I can guarantee PodTrapper will never use any more CPU than necessary
For example, I had originally wanted to do Podcast browsing entirely on the device (like Viigo, sort of). Except I don't have the resources to be hand selecting podcasts for inclusion, so my DB is like ~35 mb. Compressed down it's like 2mb, easily downloadable to a berry. But there's simply no way (with the huge limitation of stream only file access) that it could be done on a berry. I ended up getting it down to like 2 minutes to search, but that's unacceptable.
Plus, I'm a big fan of multithreading development because it's so hard. It's a total pita to get waits and notifies and locks in the write place to do multithreading right, but it's super cool to see the app use zero cpu when it doesn't need to.
If I had to list out the issues RIM really really needs to fix on BB, these would be they:
1) Allow 3rd party apps access to keys when in background
2) Tangentially, allow access to AVRCP and headset buttons
3) Random file access (how do they get away without this? It's obvious it's present in their code, otherwise their media player couldn't seek so well)
4) A startup mode that is called after all filesystems are initialized (the annoyance this causes is unnecessary)
Wow, this turned into a bit of a rant, didn't it? Hehe, oh well. Back to work. Gotta make my app look like an 8th grader