So I hope you're read my previous posts why you should migrate to Razor ASAP, what it is and why WebForms and ASP.net MVC are all dead. In my 5th Post of my series The Future of DNN Speaks Razor I would like to delve into WebAPI, why It's awesome (especially for Apps) and why JSON-data is the future - especially combined with AngularJS or similar frameworks.
The Future of Web Apps is JSON, AngularJS and More
Think about the "cool" UIs you see today, like a powerful mail client (Google, Outlook), a neat game, a stylish business UI. All of them have in common, that the entire View is client rendered typically using AngularJS, knockoutJS or Kendo.
From what I can tell, this trend is unstoppable. Meaning: in a very short time, there will be loads of people that master these tools/technologies and will produce awesome web-apps and SPA-solutions - making others want to do the same. This causes a self-reinforcing loop practically eliminating all alternatives. I'm convinced that for such applications, all server-attempts to do the same will simply fail.
The Server Is Becoming What it Used To Be: A Data Backend.
But it does leave some very important jobs for the server to perform - and the better the server is at these jobs, the more successful the platform. Thank God & Gates that Microsoft figured this out just in time - and introduced ASP.net WebAPI.
I Love ASP.net WebAPI…
Probably the best thing since WebForms (or for the more progressive: since MVC) is WebAPI. And yes: it's part of MVC, but you must admit that it has nothing to do with the view generation. It's a very simple technology (embracing current web architectures) to degrade the function of the web server to simply exchange data! That's right: no focus on "we create the best HTML" or anything like that. Simply data input and output through JSON.
For web applications and SPAs (Single Page Applications) it's the way to go. When you have custom data (say a list of users) for your application to manage, the way today is to create an SPA, some interfaces and voila! The choice of server is not important for such an application - because everything happens in the client.
The Ideal solution for Admin-UIs and Data Consumption
Data consumption has a similar need: fast, quick working with data. Here's a screenshot of a help-application we created on DNN/Evoq for Ricardo using knockoutJS early 2012:
Later we choose to focus on AngularJS - here a simple responsive References-App based on Angular:
The question knockoutJS vs. AngularJS is a great discussion for another post (anybody?) but spoiler alert: AngularJS wins.
…but WebAPI is not ideal for Content Presentation…
Ok, I'm getting ahead of myself. ASP.net WebAPI is great for data input/output. It's main strength is that I can give it a typed object (anonymously typed is also ok) and it will take care of the interface to HTTP/JSON etc. in both ways (in and out)
That's perfect for applications.
It's great for searching and list-filtering.
It's not very helpful for normal content.
It's terrible for SEO.
Data input/output is mainly relevant for management-applications and for application-style consumption (searches, lists, details).
But normal web content is 1% editing, sometimes data-consumption (list, search, filter) and between 70 and 95% content presentation & consumption. Content-consumption is usually focused on visually appealing content like a page showing the team of a company. This kind of content is usually highly customized for every customer and page page - and must be HTML-based for search engines. Not exactly your data input/output scenario…
…for which we need Razor!
In general, a piece of original content which should look good, be responsive and unique is usually placed on a specific page by an editor, edited there (and only there). It must be delivered as HTML - in pre-designed templates.
…because then I'll continue with some getting-started helps posts :)
With love from Switzerland