AngularJS vs Model View Whatever frameworks


In mobile applications, as more and more logic ends up being executed in web view, Javascript front end codebases build on different frameworks grow larger and difficult to maintain. Mobile web and apps are moving towards a data driven architecture where browsers are responsible for dynamic rendering and two way data binding.

To increase productivity and maintain Codebase I have been developing and testing mobile apps using various frameworks ranging from Backbone.js which provides models with key-value binding, collections and connectivity to all existing API over a RESTful JSON interface to Google’s latest super heroic, MVW(Model View Whatever!) framework which can extend HTML vocabulary and bring it to next level

People say AngularJS is what HTML would have been, had it been designed for building mobile/web apps. Other frameworks abstract HTML, CSS, Javascript by providing an imperative way for manipulating the DOM whereas HTML was not designed for dynamic views. AngularJS comes packed with features like two way data binding, templates, directives, dependency injection and the best part is that it comes with end to end and unit test runner setup. What else could you ask from a framework?

Keep visiting for updates and tutorials.

Categories: Tags: , , ,


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s