java script - using parse.com query with angular ng-repeat

Not sure if you already figured this out, but I was having a similar issue and found your post. I'm not sure what your HTML looks like, but I ended up using the Parse.Object's get method in my repeater like so:

<ul ng-repeat="list in lists">
    <li>
        <a ng-href="#/lists/{{list.id}}">{{list.get('title')}}</a>
    </li>
</ul>

I also looked into using promises so that the Parse query success callback actually updates the view when you set $scope.phones to the query result. My code is similar to yours but my object is List instead of Project. Here is what mine looks like:

// Define your Parse object
var List = Parse.Object.extend('List');

// Define a function that runs your Parse query. Use an angular promise so that
// the view updates when you set your $scope var equal to the query result
function getList() {
    var deferred = $q.defer();
    var query = new Parse.Query(List);

    query.find({
        success: function(results) {
            deferred.resolve(results);
        },
        error: function(error) {
            deferred.reject(error.message);
        }
    });

    return deferred.promise;
}

// Call the getList function on load
var promise = getLists();
promise.then(function(lists) {
    $scope.lists = lists;
});

So basically, it isn't that Angular doesn't see the response right. You shouldn't have to modify the result from Parse in any way. It's just that you need to use the Parse.Object get method like you would if you were accessing properties of the object, and make sure that you are using a promise so that Angular accesses your query result as it should in the view.

There may be better tools , frameworks to use.

line 188 is the fetch. It automatically loads json for the model into the collection defined at line 47.

Looping over entries in the result from the query on parse is all automated in the framework so that you can save yourself tons of time by learning a relevant framework ( ie backbone ). On backbone/parse you focus on business logic , not manipulating network io and query structures.

'phone in phones' from your question may just be a nested model or nested collection which IMO can be handled by more advanced manipulation of the basic backbone framework.