unav-devs team mailing list archive

[Joerg Berroth <joergberroth@xxxxxx>]

Hey,


this would be the suggestion for the Route-Menu:

http://imgur.com/e4ab4ao

For bike or walk mode, those icons are not visible or we put some
others. I do not see the quick access that critical as for the car mode.

This functional menu can be adopted to future additional route options.

For the Search page ( had no time to do a mockup.)

The more I think on the search Page, the more I like the sections
approach (instead of header actions).
But I would recommend not to have a separate history section. i would
put the history below the search Field.
Than I would add a "favorites" section. -> "+" as overlay in the page?
and Coordinates -> another section in the page for the choice of input.

Best Joerg


Am 2016-04-17 um 01:31 schrieb Nekhelesh Ramananthan:
> Hi Joerg,
> 
> Actually in my last email, I mentioned the following,
> 
>> May be instead the better solution would be to show a "Destination" header action in the main menu. Clicking that "Destination" header action shows 2 buttons -> Cancel Route to Destination Button and the Nearby Destination Button in a popup (similar to in nik's mockup).  What do you guys think? If you disagree, then we need to find out how to show two header sections in one page which is not ideal in my opinion. With my idea, we get the best of both the mockup, after all "Cancel destination route" and "nearby destination" can be grouped inside the "Destination popup".
> 
> This is in line with your idea of merging the "active route" functions
> into a popup. In my end, that would be the destination popup which is
> opened via the destination header button (replacing the cancel header
> button). And in the next uNav version, we could explore about your
> nearby favorite ideas in that popup.
> 
> Btw what do you mean by add coordinates and favorites to the header? Do
> you mean as header actions? If yes, why? Why not use header sections
> instead? After all coordinates and favorites are just additional search
> sources similar to the search history/location feature....
> 
> And yes, mockups will help explain your idea better.
> 
> Cheers,
> nekhelesh
> 
> On Sun, Apr 17, 2016 at 1:12 AM, Joerg Berroth <joergberroth@xxxxxx
> <mailto:joergberroth@xxxxxx>> wrote:
> 
>     Hi all,
> 
>     hey nik, thanks a lot for the work! Now I am home again and can explain
>     myself on a real keyboard, I don't like touch devices ;-)
> 
>     Thanks also for the step analyses. It shows both have almost the same
>     step behaviour.
>     But that's not really my main concern.
> 
>     Right now it seems a bit of "where is there some space left to put
>     something". instead of blowing the header we are blowing the search
>     page.
> 
>     We should do it still more functional/logical.
> 
>     This is a navigation app. The driver will use it for that primarily.
>     We should cluster the function to use-case blocks for the different
>     states of the app. The most important after actually finding and getting
>     a route is "active route".
>     All related actions to that state should be at a quick access place,
>     easy to access, all together.
> 
>     What I like on nik's implementation of marcos mockup:
>     Moving the search field into the page. That frees space in the header
>     Great. Why not use it?
>     Instead of creating sections we could just go on like this:
>     -Put the history below the search field. Search field gets the header
>     "Search"
>     ( Cause for me search history is almost as important as search itself,
>     just think about all the white screen app fails where you hve to restart
>     and find the destination before again ;-) That's actaully the history of
>     why I integrated that :-) )
> 
>     -Put favorites and Coordinates into the header
> 
>     The "AT destination" nearby does not make much sense to me at that place
>     as I would not expect it to be there.
>     As I set before, the "active route" functions could be clustered in a
>     central place. This is where for me the popup comes into play still.
> 
>     I will go for a mockup also. We'll have the best things out of three
>     then ;-)
> 
>     Best and thx a lot again!
> 
>     Joerg
> 
> 
>     Am 2016-04-17 um 00:11 schrieb Nekhelesh Ramananthan:
>     > Hey guys,
>     >
>     > You can find my implementation of the 2 mockups at the following
>     links.
>     > Please test them and see which one is better. Please note that
>     there are
>     > still rough edges that will need to be fixed when we choose to go
>     with a
>     > particular method.
>     >
>     > Nik's Implementation
>     > ----------------------------
>     > Branch at https://code.launchpad.net/~nik90/unav/new-menu-navigation
>     >
>     > Marcos's Mockup
>     > -----------------------
>     > Branch is at
>     https://code.launchpad.net/~nik90/unav/marcos-menu-structure
>     > Screenshots at http://imgur.com/a/RTf1o
>     >
>     > I did note one problem with Marcos's mockup. As you may notice
>     both the
>     > search page and nearby page have header sections. The question is
>     how do
>     > we integrate them? As a short-term solution, I just open the POI List
>     > Page when you click on "Nearby Destination".
>     >
>     > May be instead the better solution would be to show a "Destination"
>     > header action in the main menu. Clicking that "Destination" header
>     > action shows 2 buttons -> Cancel Route to Destination Button and the
>     > Nearby Destination Button in a popup (similar to in nik's
>     mockup).  What
>     > do you guys think? If you disagree, then we need to find out how
>     to show
>     > two header sections in one page which is not ideal in my opinion. With
>     > my idea, we get the best of both the mockup, after all "Cancel
>     > destination route" and "nearby destination" can be grouped inside the
>     > "Destination popup".
>     >
>     > Cheers,
>     > Nekhelesh
>     >
>     >
>     > On Sat, Apr 16, 2016 at 9:57 PM, Nekhelesh Ramananthan
>     > <krnekhelesh@xxxxxxxxx <mailto:krnekhelesh@xxxxxxxxx>
>     <mailto:krnekhelesh@xxxxxxxxx <mailto:krnekhelesh@xxxxxxxxx>>> wrote:
>     >
>     >     Hi Joerg,
>     >
>     >     First thing is that the idea to include Route Settings like Nearby
>     >     Favorites is something we can revisit later in the next release
>     >     since it isn't applicable to current issue which is the menu
>     >     navigation structure. So @Marcos @Joerg, let's discuss that in
>     >     another email later and not dismiss it so quickly. I do believe it
>     >     does have potential to be a really good feature.
>     >
>     >     Coming back to our discussion about the 2 mockups we have now,
>     >     personally I believe that Marcos's mockup borrows the advantages
>     >     that my mockup brought forward and does it better. Let me
>     explain my
>     >     why reasoning why I think we should go with Marcos's mockup
>     for our
>     >     menu navigation.
>     >
>     >     In my mockup, the most easily accessible options were undoubtedly
>     >     the search feature and the access to those route options like
>     Nearby
>     >     Destination, Cancel Route. Favorites and Coordinates. Let's
>     look at
>     >     the number of steps it takes to get to those features,
>     >
>     >     Nik's Mockup
>     >     ------------------
>     >     Search -> Step 1: Press the search header and that's it. You can
>     >     start searching right away.
>     >     Nearby Destination -> Step 1: Press the menu action header. ->
>     Step
>     >     2: Press Nearby Destination
>     >     Cancel Route -> Step 1: Press the menu action header. -> Step 2:
>     >     Press Cancel Route
>     >
>     >      Marcos's Mockup
>     >     ------------------------
>     >     Search -> Step 1: Press the search header icon and that's it. You
>     >     can start searching right away
>     >     Nearby Destination -> Step 1: Press the search icon -> Step 2:
>     Press
>     >     the Nearby Destination subheader and that's it.
>     >     Cancel Route -> Step 1: Press the cancel route header action and
>     >     that's it.
>     >
>     >     So as you can see, Marcos's mockup involves the same amount of
>     steps
>     >     (sometimes even lower) than my mockup when it comes to getting to
>     >     those features. Also I love the way he integrated the search
>     feature
>     >     so well in one page. I feel it is a lot more logical.
>     >
>     >     The only thing I am not a big fan of in Marcos's mockup is the
>     >     favorites action header. I personally believe it doesn't deserve a
>     >     spot in the main header. But that's a tiny issue that we can
>     afford
>     >     to overlook.
>     >
>     >     > And i personally would go for as much popup as possible,
>     csuse its
>     >     realky great while driving. Thats what i dont like for the page
>     >     approach you ptoposed.. It is difficult to use and not very
>     >
>     >     @Joerg, you mention that a popup is great and that it reduces the
>     >     number of steps. But as I described below, it doesn't reduce the
>     >     steps. It is the same :).
>     >
>     >     @Marcos & @Joerg, Here is what I suggest we do. I am going to
>     >     implement Marcos's Mockup. It should take me about 15-30 mins max
>     >     ;).  Let's do real world testing of both to get a better idea
>     >     instead of just *thinking* what might be better. How does that
>     >     sound? to be honest I am personally preferring marcos's
>     mockup. But
>     >     that's just me.
>     >
>     >     Cheers,
>     >     Nekhelesh
>     >
>     >     On Sat, Apr 16, 2016 at 9:33 PM, joerg Berroth
>     <joergberroth@xxxxxx <mailto:joergberroth@xxxxxx>
>     >     <mailto:joergberroth@xxxxxx <mailto:joergberroth@xxxxxx>>> wrote:
>     >
>     >         I think quick access to the things you really might need is the
>     >         important thing.
>     >
>     >         m Samstag, 16. April 2016 21:30:11 CEST schrieb Costales
>     >         <costales@xxxxxxxxxx <mailto:costales@xxxxxxxxxx>
>     <mailto:costales@xxxxxxxxxx <mailto:costales@xxxxxxxxxx>>>:
>     >
>     >                 Than we do no show the grid or an alternative
>     >
>     >
>     >             1 important point more please: A UI should be always the
>     >             same as possible.
>     >             Hide/show items is so crazy as user :(
>     >
>     >
>     >
>     >
>     >         --
>     >         Versandt, mit Dekko von meinem Ubuntu-Gerät
>     >
>     >         --
>     >         Mailing list: https://launchpad.net/~unav-devs
>     >         Post to     : unav-devs@xxxxxxxxxxxxxxxxxxx <mailto:unav-devs@xxxxxxxxxxxxxxxxxxx>
>     >         <mailto:unav-devs@xxxxxxxxxxxxxxxxxxx
>     <mailto:unav-devs@xxxxxxxxxxxxxxxxxxx>>
>     >         Unsubscribe : https://launchpad.net/~unav-devs
>     >         More help   : https://help.launchpad.net/ListHelp
>     >
>     >
>     >
> 
>