Mobile workshop at DevConnections 2013

I could be wrong but it really seems that I haven’t been in the US for two years now. First week of October, I’ll be back in Las Vegas, proud speaker at the DevConnections show. I will have quite a busy schedule, with three breakout sessions in two days and, to finish with the flourish, a mobile architecture full-day workshop the Friday, Oct 4. Here’s my schedule:

• Oct2 04:15 – 05:30 PM — Fast Facts of Social Network Programming
• Oct3 09:00 – 10:15 AM — Domain-Driven Design, CQRS, and Event-Sourcing for the Busy Developer
• Oct3 03:15 – 04:30 PM — Do’s and Dont’s of Software Projects
• Oct4 09:00 – 04:00 PM — WORKSHOP: Architecting Device-Driven Mobile Web Solutions

I just want to spend a few extra keystrokes here to call your attention on the workshop. It’s about ASP.NET MVC 4 and Bootstrap; you’ll get a complete solution that works beautifully on smartphones, tablets and PCs and IS NOT primarily based on responsive templates.

What??? Read the abstract:

Usually a solution is sought for a clear and well-defined problem. In mobile, instead, sometimes it seems that we’re looking for solutions without having first clarified what the problem is. “Mobile”, however, is a term that is quickly getting obsolete replaced by the term “device”. Any solution that involves mobile devices should be planned for a multitude of devices. This basic fact changes the approach to the design of the presentation layer (and to a good extent, also the application layer) putting the user experience on top of everything and, at least for new systems, taking precedence over domain and infrastructure. In this demo-laden workshop, we’ll first focus on multi-view client-side aspects such as Responsive Web Design and related frameworks such as Bootstrap and AngularJS. Next, we will identify possible pitfalls of Responsive Web Design and ways to work around them. In doing so, we’ll introduce server-side feature detection and device capabilities.

Key passages in the text:

• We’re looking for solutions without having first clarified what the problem is
• Changes the approach to the design of the presentation layer (and to a good extent, also the application layer

Being responsive is obvious and foregone. There will be no point in being responsive in a few months. You must be responsive.

I’d say you must work to provide a responsive experience much more than a responsive design. This is a sort of Copernican revolution in software architecture. And event-sourcing (no matter how implemented, DDD/CQRS/Transaction Script) is another REAL revolution–this one truly the biggest thing after object-orientation.

I suggest you also attend Stephen Bohlen sessions as well if this topic is catching you.