An attempt at an implementation the layered approach mobile navigation pattern that can be seen in for instance the Path app. Swipeable is for use on responsive websites, so unlike a native app it has (or rather, will have) fallbacks for non-touch and non-JS devices.
On smaller devices, screen real estate is hard to come by. Navigation often gets in the way of content. With Swipeable, I'm trying to move the navigation out of the way, while still letting it be easily accessible. I'm doing this by implementing a navigation that's progressively enhanced:
When no touch or Javascript support is available, navigation should follow the footer anchor pattern. This means that the navigation is placed in the bottom of the page, and that a button in the top of the page with an achor link, will take you to the navigation.
If javascript support is detected, the navigation layer should be placed on a lower z-index than the main content, and placed below it, while the "extra" layer (contact info for instance), should be put on an even lower z-index and underneath as well. This will allow you to click the "MENU" button to slide the main content right to reveal the main menu, and click the button "CONTACT" to slide the content and menu to the left to reveal the contact info layer.
If the device supports touch, then touch support is added so that revealing the menu or the contact info can be done by swiping right and left.
Check out the JQuery demo (use a small touchscreen, this is not responsive just yet)
Check out the Zepto demo (use a small touchscreen, this is not responsive just yet)