Welcome to our Consumer Lab page. While you will find many mobile research surveys kicked off by our teams, you will also find polls and discussions created by fellow members.
You're invited to complete any surveys that are still open and by all means create a poll if it relates to general mobile preferences. If your topic only pertains to one product, please create your poll within the respective product forum.
After a period of time Consumer Lab Polls, Surveys & Discussions will be locked. They will still be viewable for historical data.
Newest Consumer Research Invitation:
No Current Research. Check back soon.
Actions
Categories
- 8.5K Forums
- 10.2K Products
- 185 Axon 10 Pro
- 20 Specifications
- 6 News & Reviews
- 13 How-To Tutorials
- 2 Shot On Axon 10 Pro
- 6 Axon 10 Pro Developers Thread
- 59 Blade 10
- 9 Blade 10 Specifications and Owners Manual
- 1 #ShotOnBlade10
- 6 Reviews & News
- 4.9K Axon (A1P & Axon 7/Mini)
- 284 Developer's Lounge
- 21 Blade A7 Prime
- 2 Blade A7 Prime Specifications and Owners Manual
- Blade A7 Prime News and Reviews
- 107 Blade MAX VIEW
- 1 Blade Max View Specifications & Owners Manual
- 10 Blade Max View Reviews
- 2 Shot On #BladeMaxView
- 1 Blade Max View How To Videos
- 706 Other Products
- 39 Visible R2
- 31 Blade MAX 2s
- 417 Blade Z MAX
- 180 Axon M
- 209 Quartz
- 7 Sync Up Drive
- 101 SPRO
- 136 Blade X MAX
- 111 MAX XL
- 224 Blade V8 PRO
- 822 ZMAX [Series]
- 103 Grand X [Series]
- 18 Sonata [Series]
- 17 Trek [Series]
- 24 Warp [Series]
- 37 Accessories
- 201 Rumor Mill
- 109 Mobile Education
- 4 Announcements
- 2K Labs
- 1.8K Beta Lab
- 161 Consumer Lab
- 328 Blog
- 6 Site Help
Featured User of the Month
Moderators
Which design would you prefer for our countdown timer?
Consumer Lab would like to learn about which design you would prefer for our countdown timer.
In order to solve our users’ pain point to set the countdown timer, we have two different designs which will improve the user experience. We would like to learn about your preference about these two sets, which one do you prefer, Design A or Design B.
Design A: Besides being able to set the time, as usual, we also put three different options on the bottom horizontally. You can simply click one of them to make a quick set. You can also long press the pre-build time, and edit your frequently-used time.
Design B: Besides you can set the time, as usual, the timer will remember the three history records you have used previously. If you want to make a quick set, you can simply click the “History” icon in the bottom right corner, and choose one of them to use.
Please
1）Select one of the options below and
2）Reply with your reasoning
3) Leave the countdown times such as 10 minutes, 15 minutes or 30 minutes etc. you frequently use in your daily life, we can make them as the default time in Design A for reference.
Design A
Design B
Although there is no correct answer, please provide sound reasoning to support your selection.
Which design would you prefer for our countdown timer? 63 votes
51 votes
12 votes
Comments
I picked A. It looks cleaner to me.
I went with A as well. I prefer clean layouts without a bunch of buttons cluttering things up. Making the history accessible by a long press on the hourglass would be a nice option in my eyes; all the functionality without additional clutter.
I went with A also, prefer it's cleaner layout and less information to just make it simpler.
I prefer design A it looks more cohesive and integrated this way without a pop up. My most common timers I set would be 1 minute, 30 minutes, and 60 minutes.
I like A because it's cleaner. I prefer, when possible and practical, not to hide quick functions behind buttons.
A. Clean, consistent. Is there a stock app for this?
Pick "Design A"
Is clean and more practical without hiding data that can be easily display like how is showing in Design A.
A is the way. Clean and simple.
I chose A for the same reason as everyone else. Simple, intuitive is best.
I also pick A. Though I feel that the 3 presets should be more like a button and slightly larger to make them easier to tap.
Design B
Because it looks cleaner to me. I would rather have the history pop up than to have it at the bottom.
the most common timers I use are:
25 seconds
45 seconds
1 minute
Definitely Design A. Much cleaner looking and unobtrusive. The common times or last used amounts under the digits could be highlighted a bit though.
I picked B, because I think the history should be hidden in favor of a cleaner and uncluttered interface. There aren't any times that I tend to use more frequently than others, so I suspect that the history would be of very limited value to me.
Oops, clearly I did not pick B. My mistake.
I chose B, I like the history popup, and it just seems to add functionality to me.
Sounds like you actually did want B. History is hidden with Option B unless you push the history button. With Option A the history is always present above the start button. It seems like some are confused by the pictures and are assuming that the second picture for option B is the default view.
Option B for me. Like others have used as their reasoning for Option A, I prefer a clean interface and B provides that. The extra buttons below the number pad just take up space, in my opinion, and it's simple enough to tap the history if I'm using a repeat time.
A looks much cleaner. However, with A, can the suggested times along the bottom be customized? That would be a plus.
The description says you can long press those times and change them.
I like have the option of choosing a frequent history timer.
A seemed more straight forward to me.
Design A, it's nice clean and minimalistic.
id prefer design B
Design A is clean and simple
I like B as it keeps the ui cleaner
Cleaner to me and 10 should be enough.
I voted B but I rather the history button be on the left side of '0'. It would make the layout look more balanced. Otherwise, A does look cleaner, I only worry about hitting the template timers on the bottom by mistake.
I chose A. It's not a feature I would likely use very often, but it's less obtrusive.
Design A
My immediate thought with the history concept was a) how many entries would you save in the history. Too many and you'd spend all your time scrolling through the list looking for your particular entry. Quicker simply to enter the value manually.
I would be tempted to design it (if possible) such that the 3 default values are saved each time, and the "3 most used" are the ones shown each time. For example, I use 10, 20 and 30 a number of times. I then use 40 5 times, whereupon one of the 3 (10,20,30) gets kicked out and replaced by 40. That way, the app is flexible to MY use of it, rather than being written in the simplest way for the development team
A is cleaner