Slippry uses the newest web standards and the latest jQuery coding best practices, but keeps graceful degradation in mind for browsers that don’t support these modern features.
The project incorporates lessons the creators learned from using and researching a lot of other free and paid responsive sliders so that they could make a better one.
Why create another jQuery slider plugin when there’s so many out there?
"As we developed our slider more we realised we should future-proof this as much as we can, to be usable in our future projects. We looked at other sliders for inspiration on vital features as well as features offered that we didn’t see necessary," said design studio booncon, the creators of Slippry, in a blog post.
Below are some notable things I found with Slippry.
CSS-first transitions. If a browser supports modern CSS transition properties, Slippry will use them, which leads to significantly better performance for end-users compared to analogous methods in jQuery’s Effects API.
What’s awesome, though, is that Slippry will gracefully degrade to jQuery methods for old browsers.
Project development philosophy. Slippry is built with the newest best practices, modern web standards, future-proofing, and scalability in mind.
Simple out of the box (but with many customization options). This has been a dilemma of mine with sliders (and other pre-built website components): I want them to be simple so they can be implemented quickly and with no trouble, which is crucial when I’m trying to meet a deadline and when I’m already dealing with plenty of other (more important) moving parts.
But, also, I’d like to have the ability to extensively customize and make them do very specific things. These things might not be in the project’s feature set because they are unique use-cases that most other developers won’t need. So I’d need to have the option to create them myself.
Many free responsive sliders I’ve tried are either:
- Very simple, but limited in customizability and too opinionated (like when you’re required to give the slider’s HTML elements a certain class or ID that you can’t change)
- Very customizable, but difficult to implement and not production-ready right out of the box
Slippry’s out-of-the-box configuration is great. But if you decide later on that you need it to do more complex stuff, it has a lot of fine-grained configuration options, such as being able to bind DOM events at different stages of transitions.