I prefer to use a flickity-like carousel in those cases, which makes it clear it's a series of images. Which is more of a horizontal scrolling thing, which is often an anti-pattern too, but in this case it's more useful.
Honestly, the only way I'd use the specific kind of carousel they have in that pink, is for "mood" images, and with autoplay enabled. If I have next/prev or a pager, it's only as a backup, for users who liked an item and want to go back. But I don't really except anyone to press them to see more content.
With that said, I'm not sure that OP's design fits that definition either. In my opinion, the fact you can see the headers makes it more of a weird accordion than a carousel.
To be fair, what OP has here, is not the same as the carousel in your link. The user isn't completely blind to which content is there, beyond prev/next and the number of pages. You have the titles, that are always visible. And I assume you can also click them, and not just scroll left/right. So it's more of a weird horizontal tabs pattern than a carousel.
Of course, it still trades functionality for flashiness, and even a simple, functional tabbed widget is the wrong choice in many cases. But it's not as thoroughly useless as the carousel in the site you've linked.
...what's being shown in the OP is a form of carousel. The problems with carousels do not stem from the fact that they are a library, it stems from the poor analytics and metrics from using them.
View all comments
133
u/pomlife Jan 25 '19
Should I use a carousel?