Cancelling an action in Progressive UI

[LuchoTurtle]

Having read @nelsonic 's Figma wireframe suggestions and designs on a progressive UI, I found the decisions behind each action clear and concise and "just make sense".

However, I had a question regarding Level 2: Categorization (tags). I will just copy my question from the comment I left.

When the person starts typing an issue, the rest of the page is hidden, focusing solely on the save button and textfield. However, what happens if the person decides he wants to cancel the action and go back? Is he meant to delete all of the text to "go back" and see the navigation buttons? Does he click away from the keyboard?

I find that either option has its pros and cons. The first can be time-consuming but it has a "clear path". However, in the latter scenario, the user might click away by mistake and lose all the progress writing the item.

I think this issue should be addressed, as onboarding a person, even though has a happy path, we ought to take into account these scenarios that deviate from it.

[nelsonic]

Excellent question! 🎉 Thanks very much for looking at the UI/UX in Figma. 🙌

Consider the UI/UX when creating a new issue on the GitHub Mobile App: 🆕

The "Cancel" link/button in the Top-left of the screen can accidentally be tapped,
and the person will lose everything because GitHub isn't saving anything as a draft.
This is a potentially horrible UX. 😢

As @seaneady noted this morning on our call,
tapping on the @dwyl Logo is the "escape hatch"
that allows people to reset back to the home page of the app and see all their items.

But don't worry, I'm not totally dismissing the idea of "Cancelling" input / item creation.
Just in this iteration of the MVP, we want to avoid any 🤦‍♀️ 😡 moments
and gently guide/nudge people through the journey.
If they want to "Cancel" they can always click/tap the Logo.

In future iterations we can explore how to remove the Save Button completely ✂️
and just have something similar to the iOS (built-in) Notes App UX:

This question & answer is captured visually in:
https://www.figma.com/file/WrpkKGJNYZbeCzMRDVtvQLbC/dwyl-app?node-id=1512%3A4730

[nelsonic]

@LuchoTurtle does that answer your question or anything unclear? 💭

[LuchoTurtle]

It does, thanks 👍 . Clicking the logo doesn't feel like "the normal path" to cancel one, more like a "last case scenario", but I understand your reasoning.

[nelsonic]

yeah, agreed. clicking/tapping on the logo is not the best UX.
But it's a reasonably well-established UX pattern.
I feel like a cancel button is clutter and don't want to risk people clicking/tapping it accidentally. Eventually our UX will mimic the native notes app on your smart phone which doesn't have the concept of cancel. 👌

[nelsonic]

Closing as no further action required. ✅