New answers tagged smartphone
0
It depends on what problem you are addressing? What is the task being performed, who is the user, and what is the context. You may be able to offer both solutions (and a Desktop one) by designing a task flow using the same data in different ways even.
We use different UIs and devices around the same data all the time, for example on LinkedIn or eBay (see ...
1
Tablet is an excellent conceptual bridge between mobile and desktop. It is not, however, often the primary profit driver. It's very important to keep this in mind.
I still tend to work on desktop first, accounting for touch affordances and critical path as I go. That's because, though mobile is on the rise for my clients, most of the dollars are still ...
0
I'd scale with the most common to your organization / project / country / target audience.
I often find mobile inadequate: a cheap android's screen is simply too small for anything useful, and no matter what, the device will be held around arm-length, and it just won't magically scale up: the "window" to the virtual reality inside just doesn't occupy too ...
5
Start with the smallest form factor first (in your case the phone) since the lack of space will give you the opportunity to require you to define the primary focus of the app and what is the primary content that must be provided to allow the user to do his task and not allow you to add too much extraneous stuff.
While moving up to higher form factors, ...
0
I suspect it has to do with the frequency of users using the different buttons.
The menu button is a quick launcher to multiple settings and would be useful to most users to get to what they are looking for while the back button is generally used to move back to the previous screen and can be achieved by using the menu option or the power button (provided ...
Top 50 recent answers are included
