What pattern should I use for a mobile application when the user is filling a form and they want to make another entry that needs another form? The simplest case is tags for posts. But you can imagine if it was another more complex data type.
Got it. So the rule of thumb is make sure that losing data during the form input process is deliberate user choice? As in, if they need to add something else first, have them navigate back manually
5 Comments
bitfucker@programming.dev · 2 pts · 31d
What pattern should I use for a mobile application when the user is filling a form and they want to make another entry that needs another form? The simplest case is tags for posts. But you can imagine if it was another more complex data type.
Kissaki@programming.dev · 3 pts · 31d
The same applies for the second level popover. If they would/could lose input, don't. If it's a tag select, cancel is fine.
bitfucker@programming.dev · 3 pts · 31d
Got it. So the rule of thumb is make sure that losing data during the form input process is deliberate user choice? As in, if they need to add something else first, have them navigate back manually
Kissaki@programming.dev · 1 pts · 30d
If you need to control the user flow, whether due to form flow or user flow (unsaved input, possibility of loss).
That's what I took away from the linked article, yes.
beirut_bootleg@programming.dev · 1 pts · 31d
uh? yes..?