2

I am designing an app with some forms. I have looked at other Cocoa apps to see how they handle the submission of forms. Some apps don't have a submit button and update their backing datastore (or whatever) when, say, a control loses focus or a window is closed. Other's however use a submit button. Is there a rule or heuristic for when to use a submit button and when not?

  • From my personal perspective, I don't like that google calendar don't have a save button, when you adding more notifications. I always reopen it to check if it saved the changes. I know it did, but I stil have to check. – Ada Jun 21 at 16:06
  • For anyone stumbling over this later on: this question discusses the topic of auto-save and has a few discussions worth reading. – Big_Chair Sep 2 at 11:28
0

Anything that makes the user be afraid or have any doubt is a bad thing for UX and conversion rate.

As the biggest part of formularies has a submit button is natural the user expect it. Then if you don't have you will lose submissions.

But if you truly believe that your formulary doesn't need a button because it's a special formulary with unnormal usability and your user don't expect it you should try to remove the button but do it and measure to compare.

P.S.: If you try to convince me that the form doesn't need a submit button, you will rarely do it because I still thinking strange don't have a save button on a Google Docs.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.