Splendidly responsive!

A jQuery plugin that lets you serve different content to different devices and makes your site swipeable.

Get it now

This is content for a small device.

If you're seeing this you're probably on a smartphone.

Responsive content - not just responsive CSS

With Responsive Swipe, you can create a RESS site that sends different content to different devices. Serve minimal content to mobile browsers: show higher res images only on devices that can handle them - it's up to you how you use it.

Responsive Swipe loads mobile content by default, then enriches it according to device.

Swipable

Responsive Swipe makes your site swipable on iPhones, iPads and newer Android devices - desktop users can navigate with their mouse as normal, or with right and left cursor keypresses. Try it now!

Light and agile

Responsive Swipe only loads the content you want to change in the area you define, making sites faster on mobile devices. This plugin turns your site into a one-page app.

A quick illustration

If you're on a desktop computer, you can see how content can adapt to different devices by adding #emulator to the URL of this page and refreshing, then resize your browser - or for the lazy, here's a link. The coloured panel above will change depending on your window width. (In normal use, Responsive Swipe chooses what content to serve based on the device's screen width, not browser window width.) While you're in that mode, check out the big logo image in Firebug or Chrome Developer Tools. When the page first loads it'll be a small image file, logo-small.png. At window sizes above 320 and 480 pixels, it'll be logo-medium.png or logo-large.png. It's a rough illustration of how Responsive Swipe lets you tailor the size of your image files to the capabilities of the devices viewing them.

What the dickens is RESS?

RESS stands for "Responsive Design + Server Side Components". It's an idea first described by Luke Wroblewski in 2011. Basically it means combining responsive CSS with back-end code that sends back different responses to different devices.

If you want to try a slightly different RESS approach, here's a tutorial by Anders Andersen.

Inner content loaded by Ajax from a PHP response
Inner content loaded by Ajax from cache.