=============================
A minimal mobile UX navigation library.
Mobile UI frameworks try to do too much and don't address the UX issues that actually make for a good user experience. They are too complex, too big, and focus on rich interfaces and superfluous animations instead of good UX and project maintainability.
These principles are my own, you may disagree with them and someone else probably has a better list somewhere and that is ok. This is my guide for how gambit should work.
- Performance matters
- Perceived performance matters more
- Give as much feedback to the user as possible.
- Transition contexts quickly and always before any expensive operations.
- Show throbbers frequently.
- Don't be afraid to omit transitions.
- Tiny
- Zero Dependencies
- Performant
- Reasonable device/browser support (meaning: don't be stupid about it)
This work draws inspiration from David Kaneda's JQTouch and TJ Holowaychuk's Express. It is the result of many discussions and experimental code written between Rob Ellis, Brian LeRoux and Myself. Thanks to all who have helped make the mobile web better.
Credit to Brian LeRoux for the name ;)
Copyright 2012 Chloi Inc. All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.