Welcome! This is online home for my book, Mobile ASP.NET MVC 5, which will be published by Apress in the next few days. When it comes out, I would appreciate any feedback that you have. You can email me at firstname.lastname@example.org, hit me up on twitter @mallioch or find me at my website, http://ericsowell.com.
This site is primarily for all of my samples in the book that are meant to be tested in the browser. Not every chapter has these, so to get all of the samples, including these, you can get the source code from the Github repository here .
Note that most of the sub-pages have no styling. This is on purpose since most of the pages are meant to be bare examples. And they are meant to be used in conjunction with the book, so those not following along in the text will have limited use for them.
There are several ways to get the source code. First, APress should have the source code up on their website. It has been submitted so it should show up soon if it isn't already there.
Second, you can download the source code using Git. The following should do the trick, assuming you have Git installed: git clone https://github.com/Mallioch/MobileMvcSamples.git. You can also browse the code on GitHub.
Third, you can download all this code as a zip file. Go to my GitHub page for this project and click on the "Download Zip" button.
This book is primarily designed to help ASP.NET MVC developers develop for mobile browsers. If this fits you, you should find this book helpful as it covers a range of topics from Responsive Web Design, conditional rendering, feature detection, performance, HTML5, touch development and more. See the chapters below for more detail.
That is okay. Most of the material here is about client-side development, so there is a lot still for you.
Then you may not want it but most of the material is about client-side development, so there is a lot still for you.
No it is not. This assumes some small bit of familiarity with ASP.NET MVC in any version.
In this chapter I discuss the basics of Responsive Web Design, which I think is the right place to start when starting a new mobile website these days. This chapter is the overview, chapters three through five are the deep dive into the approach.
Chapter 2 is for all those developers who find layout in CSS hard unless they use tables. It's not so bad, once you know the rules.
Now that chapter 2 has equipped you to create layouts in CSS, this chapter shows you how to make layouts that flex and reshape based on context.
Flexible navigation is a special case of flexible layouts but is an important one. We go through a number of ways of solving layout problems in responsive scenarios.
Flexible layouts are useless if your content can’t adapt. After all, our websites exist to show our content. So here we discuss having flexible text, images, tables and video.
In this chapter we dive into ASP.NET MVC, discussing its ways of rendering markup and how we can leverage those to provide the flexibility we need for mobile.
Sometimes it is crucial to know something about the device visiting the page or its capabilities. Here we discuss strategies for doing this.
Performance is particularly important for mobile so we have a discussion of various important techniques for making your mobile websites perform better.
A chapter exploring what works well on mobile devices today. Despite being a bit buggy, mobile browsers are surpisingly capable.
One of the great things about mobile browsers is that all the modern ones have nice touch APIs. In this chapter I discuss the basic APIs, give a few samples and show how to program for the various touch programming models.
This chapter will include more samples of touch programming and go through more concepts around making a better touch experience.
This book is primarily about the core skills and techniques to do mobile development. But sometimes it's good to use a library instead of coding something yourself, so we discuss a number of different libraries to use when making mobile websites, what they are good for and in some cases the drawbacks to using them.
No one is perfect and books created by these imperfect people also have issues! This book is no exception. Many thanks to those who are willing to point out issues with the book.