This is indeed an interesting approach. Backend as a Service usually fixes the problem for the developer. Which is to make it easy on the developer to create di

This is indeed an interesting approach. Backend as a Service usually fixes the problem for the developer. Which is to make it easy on the developer to create distributed systems. BaaS improves UX in a small way by just making things faster and more accessible. But the focus is still the developer. The no-backend approach removes the backend all toghether, by focusing on UX, basically on the end-user. This is an amazing idea. Not because of how revolutionary the technology is, but mostly because it is a very creative way of improving the user experience. Obviously not all websites would benefit from this approach, but there is a large application for it. For most application, a hybrid approach would bring the best results. Zumero (http://zumero.com/ http://zumero.com/) for example keeps the data on the user device for mobile applications. It makes sure the application stores everything in the device, so that apps don't require an external backend. In the case of Websites, ExtJs (http://www.sencha.com/products/extjs/ http://www.sencha.com/products/extjs/) has its store, which represents a local storage for web applications. It is not persistent, but there are ways to keep it in the user machine. Don't dismiss the idea because it seems radical, try to integrate it into your app and I am sure you will see the advantages.