Range Slider

The Range Slider allows the user to pick a value from a predefined range. It comes in 4 distinct forms:

1. Single Handle
   The Single Handle is a slider that can be moved to any value in a range.

2. Dual Handle
   The Dual Handle allows the user to set a min and max value for a range.

3. Single Stepped
   The Single Stepped slider sets predetermined values that the user can set. When moving the handles, they will snap to each point.

4. Dual Stepped
   The Dual stepped works like the Dual Handle, except it can only be moved to predetermined values.

The Slider can accept an icon either side of it to give content to the value being changed.

States

The Range Slider Handles have two states - default and active. When being dragged, the Handle has a light blue border that expands out behind it. The current value of the slider is also displayed above the handle whilst active.

Abstract Link

https://share.goabstract.com/5f8a9ab2-04c2-4c67-b3f1-213d71dab6ab?sha=74525fb118324de4b30f5fb0cbeb3b2b11476ced

Comments

• Can I have a use case for a vertical slider? I can't think of a use case where this would be appropriate. The only one that comes to mind is a vertical zoom slider, like the ones that appear on maps. However this would be a separate component specifically for maps as we a) don't know what the mapping software we're going to use supplies out of the box, and b) these components aren't suited for backgrounds that aren't a flat white colour. We'll have to rethink the design for maps.

from design-system.

• In the original issue, we mention the types of labels it should have (descriptive and value(s)). Where would the descriptive label appear? Or can it be in a number of different positions (below || above || left || right of the component)? When it comes to the docs and sketch/abstract, that'd be useful to show. Assuming I've understood what you mean by 'descriptive' label.

• Should we also acknowledge the min and max labels for the slider? You've used dark and light icons in your example? I assume they are things we're expecting the user (dev/designer) to specify. Do they always need to be icons or can they be text too?

Your Q about vertical: we should include vertical in the designs (i.e. not rule it out), even if we can't think of any specific examples. It'd be good to get some user feedback on vertical and horizontal - it might be that RN users prefer one due to how something else is presented to them (either in existing apps or commonly used hardware)?

from design-system.

This is now just awaiting design documentation.

from design-system.