![thumb](https://www.webdesignerdepot.com/cdn-origin/uploads/2012/02/thumb5.jpg)
Not accounting for device width
This might sound obvious, but an awful lot of websites look like this on a mobile device (in this case, the iPhone):![](https://netdna.webdesignerdepot.com/uploads4/mobile-mistakes/img01.jpg)
body
element was set to a narrower width (320 pixels, for example), it would just get pushed to the far left of the screen and still be small and unreadable.
This can be fixed with a simple HTML line in the <head>
of each document:
<meta id="meta" name="viewport" content="width=device-width; initial-scale=1.0" />This small detail, along with formatted elements, will make for a good mobile experience.
![](https://netdna.webdesignerdepot.com/uploads4/mobile-mistakes/img02.jpg)
Making users fill out long forms
Filling out forms is annoying even on desktop computers, and it’s even more tedious on a mobile screen. Designing a web form for mobile devices is a complex task; focus on building simple forms that don’t ask much from users. Set the type of input being requested from the user, so that the keyboard has the elements that the user needs when they focus on the field. For example, setting a field’s input type asnumber
will set the keyboard to display numbers by default, instead of letters.
Not reconsidering content
Transferring content from big-screen web environments has come to involve its own strategy, like when content had to be transferred from print to web. Space and focus constraints on mobile devices are far more significant than those on computers. Luke Wroblewski’s “design for mobile first” methodology defines a strong approach we can take. It discourages us from generating one set of content for the desktop web and another set for the mobile web. A mobile design team should consider whether content that will not appear in the mobile version is even necessary? Perhaps it doesn’t even need to appear in the desktop version. Using content for decorative purposes or just to fill space almost guarantees that it will be removed later, so why not consider just essential content from the beginning? Going through this process can uncover other common mistakes and problems.Eliminating content and functionality for no reason
Revising content can be tricky, and tight schedules can force it to happen faster than it should. This often results in removing content and functionality erroneously—in fact, almost at random. The process involves in-depth analysis before the editing and curating begin. Existing content needs to be reviewed in order to separate content that adds value and meets users’ expectations from content that just distracts or fills up space. To better understand the strategy of generating and editing content, check out the book Content Strategy for the Web by Kristina Halvorson. It covers every detail, from basic content strategy to auditing and editing substantial material.Forgetting the size and limitations of a finger
When using a computer, we use precise mouse clicks for every task. We’re able to easily click on a 16 × 16 icon; the process involves no hardships. A mobile user, on the other hand, has the precision of a finger—a finger that’s almost never thin. Apple has decided on 44 pixels as the minimum acceptable size for mobile controls (44 × 30, to be precise) and has implemented this standard across its products. In addition to the size of elements, the space between those elements is often ignored. Think of a list of options, each accompanied by a radio button, with a line height of0
between them. Users are bound to make mistakes, even if they take their time. Why would we complicate things in this way?
Luke Wroblewski has perhaps gone further than anyone in identifying standard sizes for mobile design, by compiling recommendations from several platforms. According to the Windows Phone UI and Interaction Guide, the standard size between elements should be 8 pixels, minimum.
Long page-load times: Heavy image files
Heavy image files have been a problem from the beginning in web design. And the mobile web presents even greater challenges, because loading times tend to increase when you combine the limited capabilities of some devices with variable data-transfer signals (which depend on the type of Internet connection). Image optimization also continues to be an important consideration in mobile design.Long page-load times: Too many images
Many small images pose the same handicap as a single heavyweight image. This is especially a problem when designers try to emulate the look of native smartphone applications, including the gradients and rounded corners of iOS headers and buttons.![](https://netdna.webdesignerdepot.com/uploads4/mobile-mistakes/img03.jpg)
Not taking advantage of CSS3 and HTML5 capabilities
Many kinds of images can be avoided altogether now that HTML5 and CSS3 are around. Plus, mobile browsers give us a lot more freedom than desktop browsers because almost all of them were built on the Webkit engine, which supports both HTML5 and CSS3. Why not take advantage of this? The<canvas>
element in HTML5 can reduce the need for images, as can the new CSS3 properties that provide basic styles like gradients and rounded corners. It’s a major way to save on page-loading times.
Enough with the graphics now. Using too many images isn’t the only way to damage a mobile design, and images aren’t the only things that slow it down, either.
Long page-load times: Too many imports
We see this mainly with frameworks (and plug-ins for those frameworks). Let’s face it: it happens a lot now, and it has been happening since the arrival of the oh-so-necessary-and-helpful AJAX frameworks such as jQuery and MooTools. jQuery developers even went so far as to create a mobile enhancement called jQuery Mobile. These make the job so much simpler that many designers don’t worry about the consequences of depending heavily on them. You’ve probably seen something like this in a<head>
tag:
![](https://netdna.webdesignerdepot.com/uploads4/mobile-mistakes/img06.jpg)
![](https://netdna.webdesignerdepot.com/uploads4/mobile-mistakes/img05.jpg)
Long page load times: Not communicating actions clearly
Let’s say that certain actions on your mobile website take longer to load than others. That’s fine; it’s not something to go crazy over if you’ve made a real effort to speed things up. The important thing to consider now is how to make the wait more bearable for the user? The solution is to make the design as transparent as possible. What’s happening? The user should be able to answer this question at all times. For every loading action in the design, there should be a clear statement telling the user about it. Never underestimate the power of the simple “Loading…” string.Not setting a home screen icon
![](https://netdna.webdesignerdepot.com/uploads4/mobile-mistakes/img04.jpg)
<head>
of your HTML document:
<link rel="apple-touch-icon" href="images/icon.png"/>Simple and helpful. This line of code works on Android phones, too. You don’t even need to add the gloss or rounded corners; the iPhone adds that automatically.
Not being responsive
Responsive web design is one answer to all of these issues. It’s tricky to implement, but effective when done well. Ethan Marcotte recently wrote a whole book on the subject. I highly recommend it if you want to get into this in a lot more detail. Responsive design is about creating a design that adjusts nicely, regardless of the size of the container. It involves considerations such as fluid grids (where elements reorganize as the browser changes in size) and images that adapt as the page expands and contracts. Marcotte also wrote a detailed introduction to responsive design, which might help you better understand the subject. Do you have personal experience with mobile design challenges? What problems have you encountered? As a mobile user, have you encountered difficulties other than the ones mentioned here?Pamela Rodríguez
Written exclusively for Webdesigner Depot by Pamela Rodríguez, a mobile interface designer and front-end developer at Naranya AppHouse. She maintains a personal blog on desktop and mobile design and development topics.
Read Next
15 Best New Fonts, July 2024
Welcome to our monthly roundup of the best fonts we’ve found online in the last four weeks. This month, there are fewer…
By Ben Moss
20 Best New Websites, July 2024
Welcome to July’s round up of websites to inspire you. This month’s collection ranges from the most stripped-back…
Top 7 WordPress Plugins for 2024: Enhance Your Site's Performance
WordPress is a hands-down favorite of website designers and developers. Renowned for its flexibility and ease of use,…
By WDD Staff
Exciting New Tools for Designers, July 2024
Welcome to this July’s collection of tools, gathered from around the web over the past month. We hope you’ll find…
3 Essential Design Trends, July 2024
Add some summer sizzle to your design projects with trendy website elements. Learn what's trending and how to use these…
15 Best New Fonts, June 2024
Welcome to our roundup of the best new fonts we’ve found online in the last month. This month, there are notably fewer…
By Ben Moss
20 Best New Websites, June 2024
Arranging content in an easily accessible way is the backbone of any user-friendly website. A good website will present…
Exciting New Tools for Designers, June 2024
In this month’s roundup of the best tools for web designers and developers, we’ll explore a range of new and noteworthy…
3 Essential Design Trends, June 2024
Summer is off to a fun start with some highly dramatic website design trends showing up in projects. Let's dive in!
15 Best New Fonts, May 2024
In this month’s edition, there are lots of historically-inspired typefaces, more of the growing trend for French…
By Ben Moss
How to Reduce The Carbon Footprint of Your Website
On average, a web page produces 4.61 grams of CO2 for every page view; for whole sites, that amounts to hundreds of KG…
By Simon Sterne
20 Best New Websites, May 2024
Welcome to May’s compilation of the best sites on the web. This month we’re focused on color for younger humans,…