Experiences of a FileMaker Pro Database Developer

Usability: A Lesson From Evernote’s Penultimate 6 Blunder

Penultimate 5

Penultimate 5

As software/app developers it’s critical that we understand usability. We must learn who our users are and their behavior. Essentially, we build use cases and user personas. It’s our job to figure out what is working and what doesn’t work in their workflow. People are creatures of habit and they get used to work-arounds, double entry, etc., so our job also involves retraining once deployed. To me, the most enjoyable part of development is learning about the users and how they work and then understanding how you can create something to make their life better.

This week Evernote released version 6 of Penultimate, their handwriting-note-taking application for iPad. Some of us still like to take handwritten notes, but want the convenience of digital. I loved Penultimate. It was like a digital version of a Moleskine notebook. I could have a notebook for every client or every project. And, it was great for a personal journal too. The best thing, I could still doodle.

To me, what they have done with Penultimate 6 is to completely disregard who their user is. The biggest lesson I learned is to turn OFF auto-updates for apps. At the very least, if the upgrade is no longer intuitive (a mistake), make sure the help and user guides are updated. Here are a couple of snip-its from their forum posts:

Notebooks have pages – people look through pages to find what they want – bring that back.
The hand writing engine is a joke, its the nail in this “updates” coffin – makes it unusable.

In short, this version that is touted as having a “New UI for focused writing” makes it impossible to focus on writing because it gets in the way of that single activity — the core functionality of the app, mind you — at every turn…. Revert, re-think, re-do. Or just re-release the old version — under a “Penultimate Classic” name if need be — until you are ready to make this one work for its intended purpose.

The comments on the Penultimate forum and the Evernote blog post illustrate exactly what NOT to do when upgrading an existing app — ignore the user. This should be a lesson to all developers.

http://blog.evernote.com/blog/2014/11/13/new-penultimate-6
https://discussion.evernote.com/topic/74848-really-unhappy-with-new-penultimate-version

Thank goodness I had a backup of the previous version in iTunes! Two hours later, all was right again in the world of note taking.

Post to Twitter

It’s Been a While

It's been a while since I posted to this blog. No excuses, just adjusting to working full time. There has been a lot going on with my FileMaker development and I even heard from Commander "Devil Doc" Baker who's now stationed at Camp Lejeune. It was … [Continue reading]

FileMaker 12 Review – Part 1

We've been running the FileMaker 12 family of products since August 2012. These are my impressions and experiences in a real world, live development environment. My experience is taking an existing FileMaker 11 solution and converting it to run in … [Continue reading]

Creating QR Codes with FileMaker and KAYWA API

I want to thank Kevin Murphy for submitting his FileMaker QR Code solution using the KAYWA API for creating QR Codes. With the fate of Google's API for creating QR Codes unknown, it's good to see alternative solutions. Kevin's recent submission has … [Continue reading]

Recent Changes

I've recently made several changes and have been absent for a while in both the FileMaker community as well as my blog. I hope to be on track in the next few weeks as I dive into some new tools for optimization and new areas with FileMaker products. … [Continue reading]

A Time for Thanks

It's that time of year to celebrate Thanksgiving, to be thankful for the many blessing that we all have. This year, I have the pleasure of working with a military psychiatrist, CDR Alfredo “Devil Doc” Baker, MD, MC, USN, who is stationed in … [Continue reading]

Helping Our Soldiers Quit Smoking, Part 3

TCPChart

Planning the Database The way I see the Tobacco Cessation database laying out is that there will essentially be two tables. One table stores the Marine & Sailor's basic information. This is the people table. In this table is everything that … [Continue reading]

FileMaker Server, Please Abort Cancelled Finds!

I'm usually not one that likes to rant or get on a soapbox. I find this unproductive and I'm not really sure it does much to contribute, plus I feel that most readers don't like a complainer. However, there is one topic that I'm in a uproar … [Continue reading]

Helping Our Soldiers Quit Smoking, Part 2

Recommendations for Resources: Where to start with FileMaker Pro This is part 2 of a case study that will follow the development of a FileMaker database by a military psychiatrist to assist with his smoking cessation program for his Marines & … [Continue reading]

Helping our Soldiers Quit Smoking, Part 1

*This is part 1 of a case study that will follow how we get organized and setup a relational database with FileMaker Pro. Today was an interesting day and one that makes me a bit more proud to be an American. Although I have relatives and friends … [Continue reading]