Closed MatKallada closed 9 years ago
If going this route I propose somewhere we include a Seasponge header so users will know where they are.
I like how draw.io does it but the problem is if a user didn't know where they were there is no explicit indication they are on draw.io or a drawing application
I like how draw.io does it but the problem is if a user didn't know where they were there is no explicit indication they are on draw.io or a drawing application
We could have a SeaSponge header on the modal.
I am aiming to have this as a one-page web-app.
I think the one page feel is a good way to go :+1: so long as we keep the user in the loop about where they are and where they can get help and more information :)
we keep the user in the loop about where they are
Our application should (and will) be intuitive enough such that the user knows where they are without needing to be told explicitly.
As discussed during the meeting today:
Mozilla found people generally don't like modals
Good to know, but was there any particular mentioned reason why? Going through two separate pages for a web-app feels clunky, I feel that the modal would have coped with sentiment.
Mozilla has removed all but 1 modal in Firefox
Which modal did they keep? I find modals to be a great UX pattern, but if we are restricting ourselves from them, it would be good to know to what degree.
It is more intuitive for the user to have an overlay modal with "New" & "Load" when starting the application instead of travelling on two different pages.
Consider how draw.io does it