[garindra]

It's a nice fun little tool -- but it's rather inefficient in terms of the number of AJAX requests that it needs to do in order to fetch the templates. The rather simple linked page needs a total of 3 AJAX requests, one for each template. As your app (especially mobile apps) needs more templates, it probably won't be very performant. There's a reason why Ember and other frameworks prefer their templates to be embedded right in the HTML -- no need for separate AJAX fetching.

[Kiro]

Default behavior for ngView in Angular is to fetch the template with Ajax. You have your view html files in a partials directory.

[ZaneA]

I believe Angular will search for inline templates first, so as long as you use the same path for the template name it won't attempt any AJAX fetching.