xiao8579 / QuickCapture-Testing

Repo for feedback and issues during QuickCapture testing events.
0 stars 0 forks source link

[Exercise] Bigger Buttons #26

Open xiao8579 opened 4 years ago

xiao8579 commented 4 years ago

Description

The idea of introducing bigger buttons is to provide an option for users to maximize the usage of the screen for data capture. We've seen a lot of amazing projects from users, some have many buttons, while some have only one or two. For projects with few buttons, having a bigger touch area will help speed up the data capture process. image

Test

Scenraios Create a QuickCapture project that can meet one of the following scenarios:

  1. You work for the transportation department, please create a simple project to help field crews report road conditions (bad, good) with QuickCapture while driving on the roads.
  2. POI (point of interest) check-in. A QuickCapture project that allows tourists to click a button to submit a POI that you have visited in the city.
  3. Your own use scenario.

Sign in QuickCapture

Sign in to QuickCapture designer QA site with your ArcGIS account, following the instructions on the WIKI page. If you already don't have any projects yet

We expect design validations from you

  1. Do you think the current implementation meets with the purpose/requirements in the Description?
  2. What do you think of the new design (a slider with discrete values) for button size options?
  3. Would you need an even bigger sized button in the future? How would you want the big buttons to display on your device?
PaytenSamuels commented 4 years ago

Do you think the current implementation meets with the purpose/requirements in the Description? If you have more than 1 column in your group, the ability to increase height is a little weird (pictured) but it still meets the purpose/requirements in the description and is a great enhancement! What do you think of the new design (a slider with discrete values) for button size options? I like the slider to change the size - it's easy and intuitive Would you need an even bigger sized button in the future? How would you want the big buttons to display on your device? The biggest button is PRETTY big - I couldn't image needing a bigger button.. screenshot

rHMilleriii commented 4 years ago

The bigger buttons work well and fit the purpose and description. The issue that I am having is that the labels do not fit in the button in my iOS device and on Windows as it does in the web designer.

image image

As for a bigger button, I think the biggest button is sufficient.

menzelc commented 4 years ago

Testing with Android Do you think the current implementation meets with the purpose/requirements in the Description? response: The option will be very useful to meet accessibility requirements. Are you considering having an app option where the user gets to change the button size?

The one hurtle I see is for Grouped items with 2 or more columns. The large icons look strange (meaning long vertical) and may not help those that need assistance seeing/working with the app in terms of accessibility compliance. Maybe the designer automatically moves to one column when the button gets to a certain size.

What do you think of the new design (a slider with discrete values) for button size options? response: The slider works well.

Would you need an even bigger sized button in the future? How would you want the big buttons to display on your device? response: can't think of a reason at this moment for a bigger button.

ChaseFisher commented 4 years ago
  1. Yes, works as described and didn't see any issues with the reasoning...
  2. Slider was intuitive and simple and worked nicely.
  3. I don't imagine there should be any need for anything larger. I think the bigger the button the more simplistic the app will be for the end user especially when the user is not tasked with collecting a lot of fine grain data. It has its time and place but it is a nice enhancement.
mw1m commented 4 years ago

Do you think the current implementation meets with the purpose/requirements in the Description? Yup!

What do you think of the new design (a slider with discrete values) for button size options? Slider with discrete values works fine

Would you need an even bigger sized button in the future? How would you want the big buttons to display on your device? The largest size is sufficient, and could be useful for very common/high profile observations, or possibly be more useful for those vision impaired? Although for spacing it's definitely preferred to keep buttons of the same size next to each other, or you end up with a lot of vacant space like this. image

J8L commented 4 years ago
  1. Yes
  2. Slider is good
  3. Buttons seem big enough

I agree with the other comments about mismatch between buttons in more than one column. In this example, both buttons are the same size, though one has an icon and one doesn't. I would generally have all icons or no icons, I wouldn't mix and match, so this is more of an observation.

BigButtons