New answers tagged ios
0
These elements are specifically recommended against in the Android design guidelines: http://developer.android.com/design/patterns/pure-android.html
While the guidelines are simply guidelines, it's important that they be broken with purpose. As Google says on the Pure Android page: While a "design once, ship anywhere" approach might save you time up-front, ...
1
Apple's own Reminders app has a good example of the functionality you are asking about.
Reminders has a left column of checkboxes next to the items and a disclosure chevron on the right side of the reminder column. Touching a checkbox selects the checkbox and touching the reminder slides the user to the details page.
Link to image: ...
1
Or is it a new tendency regarding UX, regardless of having both Android and iOS versions of the apps?
It is a great solution for having more than 5 (bottom bar) menu items available. The slide-out menu means you don't lose track of where you are, a problem when accessing a menu through pagination. Since most apps use a fixed header at the top of the ...
0
My opinion is that there are a number of different reasons for the 'trend' (I've seen this used in some very old applications before, so apparently it is popular again). Interestingly enough, before everyone had wide screen monitors, there were different strategies for hiding information, and this was one of them. I think many designers struggling with ...
1
Since the user will be reading in downwards direction for each article, it would make more sense for each next article to be below the current one. This way a user can just keep on scrolling to go through the article, instead of switching downwards, sideways, downwards, sideways. One app that does this well is Reeder on the iPhone, but there are many others. ...
2
If you are using sliding animations between screens, you should stick to the convention that pushing a new view from the right = forward, and from the left = backwards. Otherwise your sliding animation not only looses its purpose, but it actually then causes confusion by implying something that isn't true.
The second part of your question is more ...
1
There are already usage patterns for this type of interaction that are standard on iPads. Granted, none that I know of with a tab bar, but that shouldn't change the principle at all.
I would recommend not doing this, but rather having an optional overlaying sidebar in portrait mode, which then becomes an always visible sidebar in landscape mode. The Mail ...
0
The issue with a split view is that it creates another point of focus for the ipad and also uses up valuable screen estate. However you can utilize the split view well by allowing the user to retire it as needed and slide it out as needed. To quote this article on creating better Ipad applications
The classic example of the split view (which also helped ...
1
If you need a back button to navigate around an iOS app, then you clearly need a navbar with a back button.
If however, you have a simple app that doesn't need any navigation, you can leave the back button out, or where it can be navigated entirely by using a tab bar, then a back becomes unnecessary.
Apple do this with many of their default iOS apps. ...
2
The first interaction pattern that you show is very close to the way that apple handle it in their built-in apps. The difference being that they don't have an "add new row" item. They use a clear + button in the navbar to achieve that - which is the right way to go.
If you use an item at the end of the list to add new items, you are not only breaking user ...
1
I don't know the answer to your first general question, is it a technical concern?
Regarding 1: Since it's an either/or option you shouldn't present UI elements for both text and image selection at once. Instead use some button in each cell that indicates "insertion", like so:
and then show a popup menu action sheet with options for text, camera or camera ...
3
iOS developers/designers usually honor design patterns established by the millieu of the platform. This creates a sense of consistency across apps that makes users feel that the device is easier to use.
Example: Pull-to-refresh was first established by Tweety on iOS and has now been adopted by countless other apps. Even Apple themselves jumped on this ...
0
I would consider having a task action bar at the top of your list view that scrolls out of the way when the user scrolls down, but is easy to "pop over" the list again using a button in the top bar. This would make those tasks discoverable, while saving screen real estate during the scroll task.
download bmml source – Wireframes created with ...
0
Given your question is specific to Apple iOS I will refer to the Human Interface Guidelines (HIG):
Use a modal view when you need to offer the ability to accomplish a
self-contained task related to your app’s primary function. A modal
view is especially appropriate for a multistep subtask that requires
UI elements that don’t belong in the main app ...
1
Just say swipe. No one ever looks up for information. Think about the worst case scenario- fraction of a second lost if they make the wrong choice.
0
should I say swipe up or swipe down?
It depends. Which way does the user have to swipe to perform the interaction?
If they have to swipe in the direction from the bottom of the screen to the top, then obviously say 'swipe up'. If they have to do the reverse, say the reverse.
0
I would say that the primary reason for using a modal view is for a user to complete a single task that they should not be interrupted from. This means that all the information required for the user to complete the task should be contained within the modal window it self, because the behaviour for a modal window is designed such that they cannot access other ...
0
Use "Swipe Down" as this is consistent with the movement of Scrollbar which we SCROLL DOWN to see the content lie underneath.
3
You should use neither of them. When you are referring to vertical content, you should say "scroll up" or "scroll down".
Vertical content movement has been used for decades now, and there is no good reason to change the terminology. Yes, you are swiping, but you shouldn't refer to how it is done, just what you want to achieve.
We say "click on X" not ...
3
Yes. Apple use the terms "swipe up and swipe down:
http://www.apple.com/iphone/iphone-5/tips/
The Apple HCI Guidelines may be of use here in conveying defined actions:
On avoiding redefining gestures: ...
0
Swipe up - The finger and content will both be moving up
1
I do agree that users will tend to scroll regardless of any indication, however if you still want to use any sort of indication, this is way I suggest.
The fold is a good idea when you have a fixed screen, however, the apple products have now many screen sizes (iphone5 and the ipad)so it will be harder to calculate the grid. Is possible to do, just have ...
2
That boucing stuff is scary. The user is never going to expect that on first time and it is useless when they get used to your application.
I cannot prove that idea is not going to work though. I would propose you do something like this:
The tiles are within a non ended canvas that suggest there is something else when scrolling.
That said : I am pretty ...
2
There are quite a few ways to communicate below the fold content.
The most natural way I have seen is just have content overflow the fold, so some part of it is visible while some is missing. This just tells you there is stuff down there.
download bmml source – Wireframes created with Balsamiq Mockups
If you are dealing with plain text, ...
1
A couple easy ways for dealing/ignoring the longer iphone are:
Use a scrolling/long page interface (facebook, twitter, etc.) so the longer screen gives you more room. That's it!
Depending on the type of application, you can think of locking your app in a particular orientation. OR Have some different interaction depending on the mode. eg: Yahoo weather app ...
1
For most apps, your portrait view will be fine as you simply have more space. However, your landscape view may need significant changes.
The reason for this is that the width of a screen is usually a constraining factor on a design more than the height is. Especially on touch devices, the vertical height is in effect much longer than the screen shown, and ...
0
If there is a primary choice to make between a small number of options, you can use this. Take a look at the 'Add Mail Account' screen (Settings > Mail Contacts, Calendars > Add Account > "Other") — on the second screen you will see the control is used in this manner.
Edit:
Thanks for the welcome. - I hope this clarifies things:
To clarify - in my ...
0
For what concern the Apple HIG, the only thing that is stated in the guideline section is exactly:
Use a segmented control to offer closely related, but mutually
exclusive choices.
For what concern the effect of selecting a segment, it doesn't sound that strict.
It says that can display a different view, but it's not imposed.
Given that some apps ...
1
iOS segmented controls are only recommended for switching views, as stated in the Apple HIG:
A segmented control is a linear set of segments, each of which functions as a button than can display a different view
You can think of them as the iOS equivalent to Android view control spinner.
If every mutually exclusive choice open a new set of fields and ...
Top 50 recent answers are included
