New answers tagged sliders
My suggestion is using tooltips where people can enter the value themselves.
Go with a list. This is a job listing page and the slider will infuriate people as they'll want to scan information quickly to pick out the job titles that suit them. A compromise might be to have a featured jobs slider with 3 or so featured jobs at the top of the page? That might satisfy your colleague but mean that the bulk of the information is easily ...
The only advantage of a slider over next/previous navigation is the possibility to jump (seemingly) freely to any index. In reality this would hardly work, as the user cannot distinguish the individual index locations and needs to hunt for the right position, even if they remember the general direction. Thus, I'd classify the slider the same as indexable ...
I've used Twitter Bootstrap button groups in the past for this same idea. Since they are actually buttons, and not parts of a slide, I don't think the selected states are confusing (and you can style them to be as unambiguous as you want). I think the bigger question to ask is whether it meets your needs and what you are trying to solve by implementing ...
To be honest you probably shouldn't be using a toggle if you have more than 2 states - a toggle by it's nature is an either / or switch - that's why you're having this problem. For your application it would depend on the number of states and the context, but most mobile OS handle drop lists very well. A series of Radio buttons would be another solution.
Obviously you could expect that some of your future users will be Mac users who know Time Machine (~9% OSX worldwide users, Statista January 2015, in German) therefore could know how to interpret your design. (I wouldn’t rely on it. Who’s doing backups anyway!) For me, thinking about ways to display timelines, I would assign the Present to the left and Past ...
Top 50 recent answers are included