From the documentation:
The Recline Library consists of 3 parts: Models, Backends and Views
Models
Models help you structure your work with data by providing some standard objects such as Dataset and Record – a Dataset being a collection of Records. More »
Backends
Backends connect your Models to data sources (and stores) – for example Google Docs spreadsheets, local CSV files, the DataHub, ElasticSearch etc. More »
Views
Views are user interface components for displaying, editing or interacting with the data. For example, maps, graphs, data grids or a query editor. More »
Make trial-n-error with interfaces easy, while you search for the one that users “like” in < 50 milliseconds. What if you had to hard code every interface change? How quickly would the rule become: Users must adapt to the interface? Not a bad rule, if you want to drive customers to other sites/vendors. (Think about that for a minute, then take Recline.js for a spin.)