Tag Info

New answers tagged

1

44px is the minimum recommended size for tap areas. https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/MobileHIG/ContentViews.html As with all UI objects that users might want to tap, ensure that the minimum target area for each item in a collection view is 44 x 44 points. 16px is a default margin, from the screen edge, ...


0

According to Apple, yes you're doing the right thing. I disagree. For usability, using two action sheets does nothing but wastes time while providing the illusion of cleanliness. It manages this by keeping the map background and the animation of the action sheet disappearing and reappearing upon selection. Considering your selection type, I'd suggest ...


5

Android has an official guide from Google. And iTunes too So, to avoid Copyrights issues and all kind of related stuff I suggest to follow their guidelines.


1

This is a tough question to answer without really getting deep into your app, but I'll take a crack. Be consistent with primary wayfinding I think Google has done a nice job with the hamburger-becomes-back approach. It still makes me nervous. The "menu" button on mobile (whatever form it takes) is about exposing a higher level of navigation. This is most ...


2

According to Apple's docs on that, you can restrict it to iOS7 just by requiring a feature that needs iOS7. No needs to implement any special UX flow, since the store gives you ability to restrict the download to compatibile devices. ...


0

It seems like a basic, no frills UX that works. The first screen informs the user of their options. When users go into the app they are able to navigate elsewhere easily. It's simple and works well. It also looks as if the opening screen promotes the app. Person X likes it, and next time you login, or a few seconds later, you see that Person Y likes it ...


3

A toggle might take too much space, and will be unnecessary for people who only uses one language. Should you have a language selector screen instead? And change the text direction base on what language was chosen? Another way I can think of is to change it base on user's current keyboard, but I'm not sure if that's technically doable.


1

Use BrowserStack and test them all. It's the right thing to do. It's a VM environment that you can get for less than the cost of one phone.


0

Generally, I would pick the previous (current minus 1) generation ...although the decision will of course depend on the specifics of the app. Reasons: Apple does a lot of testing on the current vs previous generation. So apps that run on the previous generation are likely to also run on the current generation. There is a VERY large tail of users on ...


0

How long will development take? Do a SCRUM type approach--you and 3 others come up with the time you think creating the application will take. Average those numbers. Then consider the timeline of new iOS device releases. (IE: Does it happen every 3 years, every 2 years, etc?) What iOS device will be relative when it launches? It will be easier to find the ...


0

Very easy: The latest and newest device your budget allows. Technology will always go up and won't downgrade, so the older version you get, the less it will last. Another option is an iPod Touch + an iPad so you can cover a wider range of screens for around the same cost of a phone. But of course, you won't be able to use anything related to phone, so take ...


0

Apple must provide a visual clue if it cannot send a text message. Why not leverage that? Just googled (as I don't use an iPhone) and Apple uses an exclamation point. See: https://support.apple.com/en-us/HT204065


0

Android offers you the opportunity to use a Toast, iOS doesn't have such a feature. Apple actually tells you to serve people an AlertView whenever you want to show an error occurred.


0

Simply put, I'd chose Left Detail because that is how our eyes naturally move (for English speakers), left -> right. Info/label first, input/information second. Maybe I'm over simplifying it here, but that would be my train of thought.


1

Based on the details you provided, i would suggest a tableview with a cell containing a switch that toggles the category or sub category. After a change in the category and sub category update to the main list of products. The concept is similar to the settings page -> cellular data



Top 50 recent answers are included