Where to place call to action on the iOS mobile form?

Question

I've simple password change form. I'm wondering where to place call to action buttons.

1 option:

• big blue call to action is placed under the text fields
• focus on the first text field - we display "next" button on the keyboard bringing user to the next text field
• focus on the third text field - we display "save" button on the keyboard

---

2 option:

• link save is placed on the right side of the header
• focus on the first text field - we display "next" button on the keyboard bringing user to the next text field
• focus on the third text field - we display "save" button on the keyboard

---

3 option:

• there aren't any other call to action, excluding call to actions on the keyboard
• focus on the first text field - we display "next" button on the keyboard bringing user to the next text field
• focus on the third text field - we display "save" button on the keyboard

---

Best solution:

I think that the best solution is the the first one, because it would be easier for the user reaching call to action button "Save". If call to action is on the keyboard or on the right side of header it's harder to reach CTA according to this:

Answer 1

I wouldn't opt for any of presented options. Two latter fall out of question, because CTA is too far and detached from the action it submits. First option has a doubled CTA, and doubling essential controls confuses users.

There is also no need to show "Next": users know when it comes to confirmation, it's a sequence, a wizard of a sort. You cannot jump to last step without completing all that comes before, and in certain order: 1. enter existing password, 2. enter new password, 3. confirm new password, 4. submit.

All you need to do is to deactivate Save button until all other forms are filled in correctly.

Answer 2

The 2nd option is the best, and complies with apple's UI guidelines. In my own words; the centre of the navigation controller should contain the name of the view; the right button should indicate anything important related to the view, like a '+' to create something or done to save

This is followed by many popular applications. For example:

My answer ends here, below is a different user flow I think you could use.

Different approach:

Now if you want to change this a little bit. Don't ask the user to retype the password in the form. Your form will include only the old and new password fields. On clicking next/submit after the new password field, open a modal box with the input as confirm password. This way your submit button is right in front of the user and and hidden anywhere.

I saw this in an application, and found it pretty interesting. You could try it. But I'm not sure of usability advantages. It's just a different method.

Answer 3

I like option 1 as it is very clear what the user should do, and as you stated it is the only option that fits right in the easy-reach zone for both right- and left-handed users. I often find forms that use option 2 confusing because the CTA isn't where my eyes are when I reach the bottom of the form, so I have to search for it. It's also difficult for lefties to reach unless they have absurdly long thumbs. IMO, option 3 also falls into the same traps as option 2.

Answer 4

The first one is the best choice, at it is the most expected location for this type of view. On the other two, I'm looking for the "finish" button and not finding it right away, making me think someone made a boo boo.

Answer 5

I think second option is slightly better than the others. The first one is pretty good, but if you have form with more than 2-3 inputs, the "Save" button will be hidden under keyboard. And on iPhone 4 or Android phones, the height of display could be even shorter.

Answer 6

The first one is the best option: easy to reach and the colour makes it very easy to see where the 'save' options are. Option 2 is okay - but someone not as familiar with iOS may not see the button straight away as it isn't quite as obvious as the blocks of blue. Third one is a big no no for me - will take the user too long to find the button/if they can find it at all.