51–60 of 98 posts
Clever move to make the slide transition timeout juuust a tad too fast to read, further driving home the point that carousels are a shit way to present information.
auto: {
enabled: true,
interval: 3000
// HA HA! I HATE MY USERS!!! Especially the ones that aren't speed readers.
}Clever move to make the slide transition timeout juuust a tad too fast to read, further driving home the point that carousels are a shit way to present information.
Clever move to make the slide transition timeout juuust a tad too fast to read, further driving home the point that carousels are a shit way to present information.
Every time I do UI stuff, I tell my boss that timers are a code smell. They're either too long, and the user gets bored or confused, or they're too short and the program bucks the user off and runs on without them. "Skip" buttons don't work. If you can have a Skip button, just make it a Next button and kill the timer.
Clever move to make the slide transition timeout juuust a tad too fast to read, further driving home the point that carousels are a shit way to present information.
From the source: auto: { enabled: true, interval: 3000 // HA HA! I HATE MY USERS!!! Especially the ones that aren't speed readers. }
But yeah, carousels moving too fast is almost always an issue when I actually want to read the contents. It's one of those design patterns that just makes me want to close the website.
(I'm unsure why Gary removed these tweets, maybe something did change his mind on this.)
Earlier quoted context omitted.
Every time I do UI stuff, I tell my boss that timers are a code smell. They're either too long, and the user gets bored or confused, or they're too short and the program bucks the user off and runs on without them. "Skip" buttons don't work. If you can have a Skip button, just make it a Next button and kill the timer.
I mostly agree with this. I've seen one valid and helpful usage of timers though: in Waze. Some things start automatically after some time, like navigation after selecting and address, or dismissing a notification. The time remaining is indicated on the corresponding button itself in a progress bar fashion.
I'm forgetful when it comes to short term memory, and it would annoy me deeply.
I've often found Carousels do a good job when there is repetitive information, E.g. testimonials - you got one big testimonials but you also have a dozen more and you don't want to fill up your page with just that.. so you use a carousel.
How much does "My daughter loved the gift. Sue K., Topeka" add to your impression of an offer or product?
Carousels are the type of UI pattern that is only okay if you ask for it. Amazon is a good example of a carousel done right. If I want to see the full-sized images which are part of a customer's product review, I click on the thumbnail representing these images, with the expectation that some larger, more obvious version of the images will be made available. Once a carousel appears in an overlay, it's not disturbing…
If you're not familiar with the term, this image viewer pattern is generally called a lightbox rather than a carousel. I generally don't see the two used interchangeably, but there's similarity to the prev/next controls, of course.
I had a client that said they wanted one because it made them look like they did all kinds of stuff. They didn’t care if it was used. It was all an illusion. It needed to portray: “We are big enough for you to consider doing business with us and to buy our services”
- Web design is politically subordinate to marketing/product.
- We don't value your time or attention.
- This website was expensive and we can afford it.
... etc.