Fair enough, but immensely good to know that it's on your list.
Originally Posted by krid
It's your time, but I would opine that at least for now put a "input password on launch" and work towards a fully-encrypted db, which it seems that you've done.
I guess I'm going to have to implement this. The easy way would be to just pop up a password dialog when the app starts. The better way would be to actually encrypt the entire db (titles, dates, category names, etc.). However, that would require a bunch of extra work.
Would it be "good enough" to leave the stuff that's currently stored in plaintext as is, and have the app-launch password just deny UI access to the data, or do y'all want it to be really and truly secure (and thus slower and more susceptible to bugs and the like)? In the former, someone who stole your phone or hacked in over the network could read the titles of the items. In the latter, they'd get nothing but an encrypted blob (well, that and the salt).
I would definitely vote for this program to be fully secure if it can be done well. But I'm a paranoid one - especially since I'd be putting password lists for work into the database once secure memo is implemented.
Thanks for the responses, krid - they're much appreciated.