I’ve been experimenting with the new(ish) Mobile compatibility functionality and like the general concept.
However, I’ve come across a number of problems which basically makes it unusable (at least on Android)… it would seriously annoy the end user.
Problem 1
When refreshing(or starting) a Grid, the mobile phone opens the virtual keyboard (Taking up lots of real estate), even when there are no fields/text areas present.
I’ve played with a few settings, toolbar entries, etc. but I can’t make it stop.
I do get it to stop by removing the toolbar, but I’ve not followed that through to a conclusion, as the toolbar is needed!
Has anyone found any solution to this?
Problem2
A) If you use a horizontal menu, then the menu items are all over the place (I suspect depending on the icon you used) and it looks about as ugly as it is possible to get.
B) If you use a Mobile menu with the Navigate Option it looks GREAT… exactly what I want. However, it doesn’t work with Tabbed applications or with Dashboards as once you get to your app, there is no way back to the main menu and you are stranded. (Tabbed apps use the little x so don’t always have the 'Back/Exit button… Dashboards have no toolbar, so there is no way back. This option NEEDS a permanent back to Menu option similar to the usual hamburger)
C) If you use a vertical Menu that has a couple of indented sub-menus in Mobile mode, then it fills the screen with the high-level menu and indents the sub-menu left. (Great so far), however, the first menu item of the next level down overlaps the one you’ve just pressed and immediately activates the first item of the next level down… again making a good idea unusable. (If you are REALLY quick you can avoid this, but it would again be a big problem for the end users).
Any ideas/workarounds are welcome.
Problem3
If you rotate the phone into landscape mode, then some grids are not usable. The header and footer are there, but take up all the space and there is no area for the actual grid table. so something that works in portrait doesn’t work in landscape. For the record the non-mobile version works… albeit messy.
It seems like the good concept has been undermined by poor implementation… Unless I’m missing something!
I’ve effectively had to discard any hope of using the mobile configurations right now.