I am using the Parse.com JS SDK for AngularJS project. I am using Parse promises and AngularJS $q service to bind Parse data to the AngularJS $scope object. I am wondering, though, are there any advantages to using JS SDK over REST API, except for the query syntax sugar and authentication management through currentUser method.
|
I guess you need to ask yourself this:
My experience is, when building apps with AngluarJS and Parse JS SDK, is that it takes some time to understand how the SDK is working - BUT when you familiarize yourself with it, the gains are enormous to how fast you can develop you application. As you are stating yourself - Sessionhandling, for when a user has been logged in and Query-building-syntax (not forget about relational queries) has just been taking care of for you. That is, at least IMO, enough for me to choose the SDK. Last takeaway from a AngularJS/ParseSDK developer is - try to avoid using Angular's $q-service for promise handling, and use ONLY Parse.Promise() instead. You $q-service IS NOT available in Parse Cloud Code, only Parse.Promise is (If you like me, start building all your datahandling in AngularJS and then merge it into Parse Cloud Code). Hope these points gave you some insight. |
|||
|
|
