I'm developing a web app that puts great focus on simplicity and "just-use" mentality. The basic idea is to write notes. When planning the concept, we where very positive towards the idea of autosaving, so the user never needs to think about saving or worrying about lost content. Just type until you want to create a new note, then start typing again.
However, some use tests indicates that the autosave pattern is not very appreciated at first. All our test people started to type, then looked for the "save" button. So we put some more effort into directing the user into understanding that "you dont need to save, that is done for you, all the time". That worked, but then the user asked, "OK you autosave, but where is my text?" and "how can I be sure that the content is saved?"
My question is, is there a natural "good feeling" about autosave, but when actually using a text editor, we all want to "make sure" the content is safe?
Are there any studies around this subject or can anyone here share some valuable experiences when dealing with save patterns in application designs?
No comments:
Post a Comment