Let’s talk about mobile web development some more! The principle of progressive enhancement is a general principle of front-end web development with wide applicability. Because you have a wide range of capabilities in mobile browsers, the principle is very important in this space as well.
Category: Javascript
Prolegomena to Mobile Web Development
Comments: (0)
The mobile web is on my brain constantly these days. This is partly because I work as a development lead for Match.com in their mobile group, and I happen to be working on a big mobile web project for them (yet-to-be-launched). This is partly because I have...um...other projects around mobile web going on. This is also because Match gave me an iPhone. My first smartphone was a Windows Phone 7 device. Given that I have in the past much indulged myself in the Microsoft Kool-Aid, I bought that thing the day it came out. In general the phone was very good but the browsing experience was very bad (it got better with “Mango”, but it remains less than thrilling). So owning that deviced did not at all excite me about mobile web development. But then I switched to the mobile group at Match and they gave me an iPhone. Suddenly, I had a device that had a great browser. Perhaps you are surprised, but that makes a huge difference. And I’m a web developer by trade anyway, so the world of mobile web development offers an interesting new avenue.
Last month I read a great book. It is one of those “must reads” about JavaScript as far as I’m concerned. I’m talking about Alex MacCaw’s book “Javascript Web Applications.”
This month I have two technical talks, and in this case they are back-to-back tomorrow and Thursday. I didn't need to relax anyway...
I have always been a "full stack" kind of guy. When I started teaching myself to program back in 2003, I had an app in mind that required a some knowledge of css, databases, and everything in between. At the time I didn't even really know what those were but eventually I figured it out. I'm doing Full Stack Day to help others get started with all the technologies you need to build websites.
Creating an Ajax Content Switcher with jQuery and ASP.NET MVC
Comments: (0)
The last few days I have been digging into the Javascript history api and in the process built a jQuery plugin that I figured others might find useful. It is actually very simple. I will be blogging about the Javascript history api next week and this will be used in those, so you can consider this a teaser as well if you are interested in the topic.
Read More on "Creating an Ajax Content Switcher with jQuery and ASP.NET MVC" >>
In the last post I showed you how to get started with Node.js on Windows. Easy, wasn’t it? Remarkably so since there was no install requirement. This time we are going to tweak the system a bit then learn how to return static files like plain ol’ Html, Css and Javascript files.
The intarwebz has been abuzz for a while about Node.js and being the intrepid explorer of things I don’t know, I figured I would take a look at it. I’ve been working like a rabid code monkey for weeks now and haven’t had hardly any time for fun coding so I needed something to stretch my brain anyway. So far Node.js is fun, it feels kinda raw…kinda low level and it is very different from what I’m used to. And even though the documentation is a bit sparse, it is very approachable to the Windows user. So I’m going to help get you started.