>The problem (in my view) with all these samples or tutorials is they create a "typical" web application; like for example, online store. My use of the application is "simulating" windows application in the web UI. For example, for me it would be very helpful if they would create a simple tutorial/walk through that would do the following:
>1. Get records from a database for a table
>2. Display these records in a grid view
>3. Allow user to select a record, click on Edit button and display the record in the Detailed View (my records have so many columns that editing in the grid is not easy).
>4. User makes a change to the record and clicks on Save or somehow saves the record.
>
>The above (in a simplified way) is what I have to do in my application a lot.
>
This is exactly what this tutorial teach and what ASP.MVC provides right out of the box with a very minimum efforts.

1. You need to create a model - classes for your objects

2. You need to associate these classes with your database (if you already have a database). This is EF code first approach

3. You can use default routes or you can create your own routes (I think defaults should be OK)

4. You define controllers (you can use them with templates).

5. Then define view for each action (you can let MVC generate it for you based on your model).

Basically, that's it - you have your application.

Then you'll start adding more logic, can add some bells and whistles, etc.

But the bare bones process with MVC 3 (and MVC 4 even easier) is what I described. Simple stuff if you don't need anything too complex.

MVC 4 provides a lot of support for Mobile development.