NoNonsenseApps

OK, all major work concerning the password feature is now implemented. Thought I’d show some pictures and explain the implementation (will refer to the captions of the pictures).

The idea is that a locked note requires a password to be shown/edited. This also goes for lists as I show a small preview of the content there. So locked notes do not display any part of the note in the list (image 1). This also applies to widgets, and this will also be the same for android agenda widget.

Next, you open the note. Once loaded you will be prompted for your password (image 2). Note that if you have no password set, then locked notes will open directly in the editor but they will still hide their content in the list. As you can see from the image, the title and due date are not protected by the password.

Once a correct password is inputted, the note content will be displayed and made editable (image 3a). If you don’t input the password, the note field will remain locked and un-editable (image 3b). You can still change the title and due date however. Maybe I should add a password check to stuff like delete as well but that is not implemented right now.

The locked status IS SYNCED and so will carry over to your other devices if you have any. The implementation works by inserting a tag into the note (which is parsed when displayed). By looking at the last image, you can see how it appears in gmail where the tag is visible. It has two major advantages. First, all information is now synced. Second, forgetting your password is not a problem as you can re-install the app to get rid of the password and still not lose any information!

Notifications for notes will be implemented in much the same way as this, allowing you to have multiple notifications per note which also sync.This is also how other apps do it too (e.g. Calengoo). So if you’re using that app as well, you get seamless transition/compatibility with my app.

This implementation is not designed for hardcore security. If you have sensitive information, it’s a bad idea to save that in any place un-encrypted. This is only intended to prevent say your co-worker from picking up your phone and seeing what your computer password is.

I hope you’ll like this feature. 3.2 is on track for release this weekend.

First run of the password implementation :)

First run of the password implementation :)

Feedback wanted!

Got the indendation/server sort going, but need a second opinion on the indentation. Should it be more spaces? Less spaces? Should the space be before the checkbox perhaps? I want to know what you think!

Feedback wanted!

Got the indendation/server sort going, but need a second opinion on the indentation. Should it be more spaces? Less spaces? Should the space be before the checkbox perhaps? I want to know what you think!

Ideas for future projects

They all center around being tablet optimized and aimed at ice cream sandwich

  • Git library (would be used together with all the other apps, not on its own)

  • File manager (think dual-pane NortonCommander clone)

  • LaTEX editor (and now realize that it’d hook into the Git library)

  • Programming IDE (again, hooks into the Git library!)

Hunting ebay for a cheap Transformer to try some ideas

3.1 released!
Includes:

Widget (resizeable)
Integration with next version of Android Agenda Widget
Czech translation
Better icons (all matching color now)
Notes with no due dates are placed at the end when sorting on due date

3.1 released! Includes:

  • Widget (resizeable)

  • Integration with next version of Android Agenda Widget

  • Czech translation

  • Better icons (all matching color now)

  • Notes with no due dates are placed at the end when sorting on due date

Passed 2000 active installs today.

More than 3000 total.

Celebrations! Lets celebrate with a widget! And Czech translation! And new menu icons!

I also figured out why the app crashes on start up on the Galaxy Tab I installed it on (in a book shop). Honeycomb 3.0 is broken. Go figure.. Even crashes in a 3.0 emulator. No idea why though. Works fine in 3.2, so will move minimum required version to 3.2 in next version.