In this series of four posts, I’ll provide an introduction to the world of mobile web development by giving a birds-eye view of three different technical strategies. We’ll kick things off this week by examining what exactly it means to be “mobile friendly.” In the following posts, I’ll give a rundown of the different options for accomplishing this.
What is Mobile Friendliness?
Mobile friendliness can mean a multitude of things, depending on who you’re talking to. In my experience, I’ve found it helpful to think of it in terms of three goals for improving your site’s user experience: Presentation, Content, and Performance.
Goal #1 (Presentation)
“Make websites that work well on a variety of screen sizes.”
“Adjust your content for mobile users.”
Think about what your users want to do at your site if they are on a phone. A great example of this is Alaska Air’s website. Their desktop site focuses on getting visitors to book trips. Mobile users, however, are probably more interested in checking-in for a flight or seeing if their flight is delayed. They’ve adjusted their site’s content to reflect this, and it meets the needs of mobile users.
Goal #3 (Performance)
“Give your users a smooth experience, even on a slow connection.”
Though things have been getting better in recent years, browsing the Internet over a wireless data connection can still be pretty painful. This makes it more essential than ever to practice good performance practices, only sending the user the bits they will actually need.
Note: Know Your Audience
While not strictly a part of my definition of being mobile friendly, defining who your target audience is makes these goals much more concrete. For example, it is absolutely critical to keep in mind which browsers and devices you will target when picking a mobile strategy. At Mozilla, we’re keeping our eyes on the future and focusing on tablets and smartphones with standards-friendly browsers as our target audience. On the other hand, if many of your site’s users are on devices with less capable browsers, that may eliminate certain strategies as viable options.
As you’ll see in the following posts, different approaches aim to achieve each of these goals by different means. Join me next week to learn about the Separate Sites approach to mobile development.
malexis wrote on :
Montana Harkin wrote on :