Do you design for handhelds?

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
laura s's picture
Yes, always
16% (10 votes)
Sometimes
21% (13 votes)
I know I should, but I don't bother
25% (15 votes)
No. Should I?
30% (18 votes)
No. Why the heck should I?
8% (5 votes)
Total votes: 61

Comments

I post this poll as a member of

Laura Scott
PINGV | Strategy • Design • Drupal Development

I look forward to this

sime's picture

I look forward to this discussion. The most I do is check that my content is accessible text-only, I have no idea what these handhelds do visually. Do they interpret my style-sheets in such a way that my content is mangle? I don't know.

So I've answered "always", I wanted "mostly" because sometimes customers make me do evil, but generally I have good intentions. :-)

duplicate post

rickvug's picture

sorry about this.

I have yet to run into a project that needed it...

rickvug's picture

I know that I should be doing this but frankly, I haven't had a client who asked or required any sort of testing on mobile devices. This obviously has to do with the kind of sites that I produce: they are for small business and focus on the design first and foremost. This functionality just isn't warranted or budget. However, if you are making a site that is focused on continually updated content (say a newspaper) I think that developing for mobile devices is essential. All sites that I build use CSS for all layout, so I might only need a few tweaks to get things in tip-top shape for most mobiles. Laura, in your article you mention a number of helpful tips but don't mention skiplinks. Skip links ("skip to content") are perfect for mobile devices and general accessibility.

On a related note, I have in the past added print stylesheets to ensure that articles print clearly despite the intricate design. For a great example of print stylesheets go and print off something from alistapart.com ... notice the unique look.

So...

Boris Mann's picture

There are some things to keep in mind. BUT...my new Nokia E61 phone, for instance, does a great job of rendering standards compliant websites. The browser is based on Apple's WebKit code, and I can even use the full, non-mobile version of Gmail.

That's great!

laura s's picture

My 700p runs old Palm software, so options are limited. Even Opera chokes at times. I bought it for the screen and keys, I confess. At least we signed a short service contract. In this world, last month is practically outmoded.


Laura
pingVision, LLC

Laura Scott
PINGV | Strategy • Design • Drupal Development

I say always, but...

msmiffy's picture

I have always coded to be user agent neutral, but only recently have I stared using the emulator on the Opera Mini site to check how my content looks.

What amazes me is that I have visited some, supposedly, mobile sites with my phone (Motorola V3i/Opera Mini), and have found them quite awful on the small screen.

Not explicitly, but...

Cliff's picture

Simply making a site I inherited compliant with XHTML 1.0 also made it work on the small screen.

Writing compliant code and following accessibility guidelines goes a long way towards making things work on handhelds. (You might say they go hand in hand.)