Some libraries like Backbone are very liberal in their demands. They provide a very basic scaffolding around which to build your app. However, you are on your own when it comes to developing much of the higher level code. This isn’t necessarily good or bad - just one philosophy on what a framework should provide.
A framework like Ember provides a more comprehensive solution. Developers get everything they need to craft an application from top to bottom. The trade off is flexibility - although you don’t need to write a lot of boilerplate code, you must be willing to buy into the framework’s methodology. Again, this is neither good nor bad just a different philosophy.
Segmentation in the framework marketplace
Ease of use
To achieve our goal of creating a library that’s easy to use, we abstracted the most frequently used features of the API - namely Entities and Collections - into simple objects that can be used in any app. Using these data structures in your app should be a natural extension of the API.
To learn more about using it, check out the Launchpad. It’ll walk you through creating a small HTML5 app that makes backend calls to Apigee’s App Services.
We’ll have more soon on building bigger apps with the SDK, so stay tuned!