Rules to Better Kendo UI

To keep a good separation of concerns between your AngularJS controllers and your data service layers you should always call an AngularJS service or factory from your Kendo datasource logic.

Many demonstrations show a hard coded string in your Angular controllers calling your API but this means you will be making data API calls from your controllers, which is bad for several reasons:

1. You will end up with many API data calls from different controllers versus all being in your one location
2. Your controllers will be harder to unit test
3. If you want to call the same API endpoint somewhere else in your application you now have two place with this hard coded string, that might need to change in the future
4. If you keep all your data calls in one place your code will be easier to read and you can share business logic for making the API calls within your Angular service or factory, like a common error handling message for failed API calls
5. Finally you can perform actions while the promise is being resolved, like show a spinner animation or log out a message to the user

Icons make your user interface clean, but users sometimes need further information about the operation they are about to perform.

Use a standardized grid to display tabular information - you can sort, paginate, and filter data in your grid.