I don&#x27;t see it solving one problem so much as lots of them.<p>With a decoupled front-end you can make applications which are much more flexible for dealing with change.  Imagine swapping out the entire backend application, or completely re-writing the front-end - you can easily do either since the integration between the two is formalised and documented by the json contracts.<p>That also means a new front-end developer can clone down a Shunter application and start modifying templates with confidence it&#x27;s not going to break anything without having to run the backend, services, mock db, etc.  Great for working in big teams, or ones that aren&#x27;t co-located.<p>It can also run a single unified front-end across multiple backend applications (for example if your rails application wants to share a common layout etc. with your Wordpress-driven blog section, or whatever ecommerce backend is driving your &#x27;shop&#x27;).