I have not worked on Parse, but I believe as long there is a REST API available AngularJS can very well integrate with Parse.com. These links substantiate that fact
Said that, AngularJS is a very capable framework with a steep learning curve. The simple stuff is simple but one needs to put ones head down and start learning the not so simple stuff like directives once one starts building any decent size application. The more you invest in learning AngularJS the more rewarding it becomes.
It has a very clean separation in terms of view and code. The code is further organized into modules, factories, services, controllers, directive, filters etc.
But still nothing stops you from creating a mess with the implementation 🙂 What I have realized over the time is even if you create mess within AngularJS the effects are localized rather than affecting the complete application, due to the modular nature of Angular.
I suggest you try creating or looking at some samples with AngularJS (such as TodoMVC)
This is how i felt learning and implementing AngularJS solutions
Thanks for bring up our Parse x AngularJS boilerplate – we’ve just updated it today too.
Our entire site getbrandid.com is built with Parse x AngularJS and no servers of our own.
We built this boilerplate after because having spent a few years building BRANDiD, we had a lot of best practices to share with the Parse and AngularJS communities. We think it is a match made in heaven, and is the fastest way to build powerful complex, highly maintainable serverless apps.
We’ve basically extended the Parse SDK to support AngularJS bindings, we’ve eliminated a ton of boilerplate code, and most importantly, we’ve established an architecture for large serverless apps using Parse and Angular.
I highly encourage you to check it out –
Parse‘s documentation does not say that you have to use
Backbone, it just says that some stuff are compatible with
Backbone classes, like the
Collections object, which might be useful ONLY IF you use
The big hassle of using 3rd party stuff inside angular is its lifecycle, as it uses POJOs and only watches for changes in these objects at specific points in time – Check the
Scope Life Cycle documentation for more info.
Given that, when
Parse returns its callbacks,
AngularJS might no longer be observing those
Parse objets, so you need a way of telling angular that thing changed, and you have to do it inside the digest loop, for example using
The easiest way I found to communicate with the parse.com backend is to use the jimrhoskins/angular-parse Angularjs module that replaces the (backbone) ParseSDK.
Ads instant 🙂 I included it in this angular/parse boilerplate.
We’ve been using this method fairly frequently. We decided to document our experience. Its a 2 part series on building angular apps with a parse backend. Hope it helps!