unav-devs team mailing list archive

[Nekhelesh Ramananthan <krnekhelesh@xxxxxxxxx>]

Hi everyone,

On Fri, Apr 15, 2016 at 12:00 AM, Joerg Berroth <joergberroth@xxxxxx> wrote:

> Ha! alright, just read it on the phone and decided to re-pick my
> keyboard to answer instead of going to sleep.
> Now you are opening something I first wanted to keep calm about as we
> started to redesign everything. I just wanted to see where all this
> navigation goes, without starting to raise hands.
>
> To say it straight forward: it is right!
>

Nice to see we are on the same page on this one. :)


> Yes, let's remove them!
> And to be even more aggressive: Do we then need the route page at all?
> We could just define them all as header actions!
>

I think we shouldn't add too many actions to the page header. Instead here
is a mockup of how I think we can solve both the issues.
http://imgur.com/s0p2Ai3

In the mockup, we have 4 header actions which are Search, Menu, Location
and Full-Screen. The reason why I decided to just show these settings is
because they are important to the user when in the map mode. I then
converted the Route Page into a Route Popup which shows other actions like
Favorites, Settings and Coordinates which are less used.

What do you think?

This way users get really fast access to the critical search feature. The
nearby and share menu is removed. And we don't overcrowd the header by
moving some actions to the popup since a dedicated page for those 3 actions
is a bit of an overkill.


>
> And one more thing (answering your last mail,too [I never use welcome
> wizards by the way - the more intuitive the software guides me to my
> goal, the more i like it -, but I think most of the people like the use
> and fill of this user interaction, so great work!]):
>
> If we remove the "navigation page" we have the search function in the
> header.
>
> And for the search page in particular:
> I would like to get the actions performed with least clicks, meaning
> that I don't like to step into the search page and then have to trigger
> another search button to be able to search.
> The search page should always start in the search state. It might be ok
> to cancel it than, 99% of the time I want to search.
> Suggestion: start in search state, show the search history.
> On cancel-click the keyboard will disappear and the complete search
> history is visible. I would like that approach very much.
>
>
You are right about the search page. It was a bit of an oversight on my
part to change the search page into what we have now. I will revert it
back. Sry about that!

I would like to get a confirmation from both you and Marcos about my
proposed design. I can then proceed to implement these changes asap.

Cheers,
Nekhelesh