New answers tagged ipad
1
There's a good step by step guide here where one can follow an example iPhone app being ported to iPad. It brings up some of the features/controls suitable for the generous screen space of the iPad and which controls it can substitute on the iPhone.
0
You would use the popover for smaller, more transient tasks.
If there are multiple views that the user can find under this view, you would use a modal view.
For example, if the user is simply viewing the details (with the option to edit) of an entry in your table, then you would want to use a popover. This is what you mentioned in your question, so in ...
0
1) Is it possible to "mix" a navigation bar and a toolbar, and display back buttons and toolbar items at the same time? In iPad, only had navigation on one side. There has to be an extraordinary reason to allow drilling down on both side. Yes, you can include toolbar items on a navigation bar, UX wise and dev wise.
2) Is it possible to display a segmented ...
0
Edit in the same Detail view.
Your user will be use to this if you've done this on the iphone.
Master & Detail view.
Refer to Settings app to display a list of items (Master) and the item on the right (Detail)
0
1) If there is no drill down in the right pane - do as @siddharthkp says and drill down in the left pane.
2) Another option is to use a form style modal view.
Remember that depending on the IOS version the left hand pane is either a swipe over, popover view or compressed on the same level as right hand pane. So the first option is preferred.
0
Agree with @Stephen that should avoid the back button on a new row as it is wasting precious screen estate.
I have came across app that has a different approach to this. When i navigate to the 2nd level page, the "back" button will appear to the left side of the "menu" button. Which means the "menu" button will be slightly push in to the right to make way ...
3
I would say that there are some obvious drawbacks of how the layout is set up now, both regarding the edit CTA's and also the search field.
Let me start with the search field. The search field is in a top bar of the app, covering both the list container (left) and the item details container (right). This makes it quite confusing for a user to establish ...
0
Thank you all for your comments. The final solutions I suggested was to re-think the way navigation should work on the mobile app.
This should be based on the idea that a back and menu tray cannot be together in the same interface, therefore I suggest to remove the menu-tray from all of those pages placed underneath the first level of navigation.
0
I think this all depends on how you want your users' story to be.
Do you want the user to browse the 'list' content while being able to browse the options? Do you want to lower the chances of the user getting lost. Then a flyout might work.
If you want to focus the user and 'break' their "flow", then a modal might work. A modal will make them pause, and ...
1
The element you are referencing in the mockup is called 'Action Sheet' in iOS terminology.
An action sheet always contains at least two buttons that allow users to choose how to complete their task. When users tap a button, the action sheet disappears. An action sheet doesn’t include a title or explanatory text, because it appears in immediate response ...
0
Why not fully embrace the navigation model of iOS?
Selecting and item would open the item in a new screen that would slide from the right (giving the impression of diving deeper towards the right hand side). From there, a back button would show on the header, with which a user can return to the list of items.
0
I can state that I haven't encountered such a design, which might hint that it's novel. Not being bad by itself, just don't expect people recognizing it from before.
By itself, I'm not sure this design is a good idea, since it breaks user's expectations. This is most probable due to the inconsistency between the options that open content on the right pane ...
0
A navigation bar is a class which could, even though it does not, be a subclass of the toolbar. Both have a set of items (usually buttons) which can be manipulated. The navigation bar has the additional capability of pushing or popping a view controller onto or off of the presentation stack. Further, the navigation bar has a title label by default. However, ...
1
For the programmers, it's like this:
A nav bar is something at the top of the screen that controls a stack of views. Each view other than the first will have a back button. If you put extra buttons on there, it's still a nav bar.
A toolbar is a bar at the bottom of the screen, that only contains buttons.
For a programmer they are different classes of ...
Top 50 recent answers are included
