New answers tagged

0

Its a fairly broad question to be honest, I' start by looking around at both playforms UI patterns to identify the differences between the two before you start to research, sketch and prototype and test this will make it easier when you come to design and prototype it. Assuming you mean mobile (not tablet) the main thing is getting the screen size right in ...


3

The iOS HCI Guidelines suggest that you should follow the Modal View in order to have the user complete a task and have complete knowledge of the task they are doing. Although the button suffices the purpose of the context, I would still recommend using the title to adhere to the guidelines. iOS users are accustomed to the layout and know the difference ...


0

I always feel it's confusing to have 'Cancel' button to cancel a 'Cancel' action. "Continue editing" might sound better. BTW, Apple's guideline also recommends to use red color for destructive actions such as deleting or removing data.


0

The Android time picker is pretty good. You first select the hour around the edge of a clock face and then you pick the minute. No need for scrolling or lists. The below example is a recreation taken from ESTimePicker. The 12-hour clock is similar.


2

Change the size of the text and the tick colour of the subsections, for example:


2

I took a similar approach in solving this with a 24 hour circle. I found this much easier to use. Once implemented, most users loved it - others felt like its was hard to set smaller 15 min increments. However, fine tuning into these increments depends on where on the circle the user would tap (on the outer edges are best as more surface/touch area) and ...


0

Even though Apple recommended (and surprisingly still recommends) pickers for dropdowns, not even they use it anymore. Spoilers: In both these cases, the "logic" would dictate to use a dropdown + picker. Apple chose a much better solution for their own apps. Still, a whole screen to pick between "Female" or "Male" (pardon the binary example) seems ...


1

Excellent that you are working with Sketch! 1.0) No, you should not design for each device separately. You could certainly make higher fidelity mockups this way but, trust me, it will be a pain to make any changes. And there probably will be many changes. There are a few different schools of thought here, but the consensus is pretty much that you should ...


0

Best practice states you should follow the UI standards and conventions for each platform. The big challenge of course is iOS and Google Android standards are not always that compatible, plus it can be more expensive to build two different looking solutions, even though this would be best for the person using the phone. So you really only have two options: ...


2

Just a quick suggestion, you could possibly disable the submit button, but have the text on it change to 'Submitting...' and also disable all of the form fields, so that the user can't then submit the form using the keyboard. download bmml source – Wireframes created with Balsamiq Mockups I don't know about the feasibility of adding a loading ...


2

I would do both 1 and 2, but also present the user with a message. Having a message will guide the user's expectation and avoid unnecessary concern by the user. The message doesn't have to say much, even just that the form is submitting and will take up to 30s.


2

You can add some visual clue showing the icon can be changed. Maybe a little pencil or an arrow


2

If I understand the question, the answer is that it depends on the content you're trying to display. What it sounds like you're describing is a split view. [ This is a standard iPad pattern and it works well if you have many menu items AND don't need all of the screen real estate for your content. I would guess this isn't a good pattern for you as you're ...



Top 50 recent answers are included