Tag Info

Hot answers tagged

4

The Settings should be in the header. Look at the Google Material design structure as a reference. A 3-dot menu doesn't take up too much space.


1

Assuming you are making an app for an iPhone, I would not have a keyboard short cut for edit, this adds in unnecessary steps as the keyboard is generally hidden inside an app so you are asking your user to bring up the keyboard and press key combinations. Whereas the edit button on the app is just one tap and is quick enough as it is. If you are making an ...


1

The cover flow responds well to hardly any real use case. Sure, it's visually nice effect to browse the items, but when designing for reality, there is no such use case as "a user browses the content." They are always making decisions on some criteria, whether actively or subconsciously. You could start by getting to the root of the user's decision making ...


1

The 10 Usability Heuristics are as close to a 'Bible' as you can get. Visibility of system status: The system should always keep users informed about what is going on, through appropriate feedback within reasonable time. and Help users recognize, diagnose, and recover from errors: Error messages should be expressed in plain language (no codes), ...


1

Yes, it's a normal practice. As you mention with an activity indicator and the option to cancel it'd be okay. A reason for this is because if something goes wrong you want to communicate it to the user as the first step after the "Submit" action. If you introduce more actions "in the middle" of that process, and that action can also have errors, it'll broke ...



Only top voted, non community-wiki answers of a minimum length are eligible