The mobile web and billso.com

by billso on Tuesday, 5 February 2008

This site is now avail­able in a mobile web for­mat at http://m.billso.com/ – please give it a try with your mobile phone or PDA.

Apple iPhone users can view this site in its reg­u­lar desk­top mode at billso.com, or try the mobile version.

As I men­tioned on 27 Novem­ber 2007, the mobile web is not quite ready for the masses yet. There is no stan­dard URL for mobile web sites, for exam­ple. Some sites like Face­book use “m.” as a sub­do­main that serves up a mobile site. Other mobile sites are using the .mobi top level domain. I have a short list of mobile web sites at http://billso.com/mobile/

I own http://billso.mobi and I’ve set that name to redi­rect to http://m.billso.com

It’s dif­fi­cult to design web sites that resolve well on small screens, espe­cially given the num­ber of dif­fer­ent devices, plat­forms and car­ri­ers that exist in the mobile Inter­net market.

Dif­fi­cult does not mean impossible

I’ve tweaked my web site with some Word­Press plug-ins. Plug-ins are prepack­aged files of PHP pro­gram­ming code that third-parties have writ­ten to extend the Word­Press blog soft­ware. I’ve made m.billso.com work on sev­eral hun­dred pages of con­tent with 3 hours of effort.

The mobile ver­sion does load quickly on PDAs and phones, while pre­serv­ing most of the site con­tent. Those were my pri­mary goals. I’m pleased with what I’ve accom­plished using free soft­ware and web services.

Feel free to log on with a real com­puter and leave a com­ment about the mobile site. I’d like to know if the mobile ver­sion of this site is usable and use­ful for my readers.

A few of the site’s fea­tures do not work well on the mobile ver­sion. I’m look­ing for workarounds to address some of these problems.

  1. The menu on the top of each page becomes a long set of entries.
  2. The event cal­en­dar in the right side­bar turns into a sin­gle col­umn of text, for exam­ple. This hap­pens with the stan­dard Word­Press cal­en­dar wid­get, too.
  3. Tables do not resolve well in mobile browsers, either. That’s one rea­son that the cal­en­dars on the Spring 2008 course pages are writ­ten in a bor­ing text format.
  4. The scenic image at the top of each page shrinks a bit.
  5. Mobile users can­not enter com­ments. The reCAPTCHA plu­gin that I use to stop com­ment spam does not sup­port mobile web browsers. The com­ment fields will appear on the mobile site, but com­ments will not be posted. i’ve seen very few mobile blogs that sup­port com­ment entry, so I am not very wor­ried about fix­ing this issue.
Share
  • http://www.atypicalliving.com atyp­i­cal­liv­ing

    Hey Bill, check­ing the mobile site on the iPhone… com­ment­ing from the laptop.

    The site is a lit­tle on the plain side, as you men­tioned, but still very usable. Loads very quickly on the iPhone, even on EDGE, so that’s always a plus for those times I’m check­ing the site in class…

    … I mean, when I’m at work…

    … I mean, when there’s no wi-fi con­nec­tion to speak of. Yes. That’s it.

    Also, the site defaults to the mobile site on the iPhone, I can’t get to the desk­top ver­sion, even if I explic­itly type in billso.com

    Oth­er­wise, works like a charm.

  • http://www.atypicalliving.com atyp­i­cal­liv­ing

    OH, one more thing…

    Adding billso.com to the iPhone home­page also leaves a very nice home screen button.

    You know, for those inter­ested in that type of thing.

  • http://billso.com billso

    Ah, the iPhone home screen but­ton worked! I added that last week, but I have not had a chance to test it on an iPhone or an iPod Touch – I do not own either device. Mahalo!

  • http://billso.com billso

    I could develop a land­ing page for iPhone users. If they surf to http://billso.com/ the iPhone user will be redi­rected to http://billso.com/iphone/

    Then they can choose the reg­u­lar site or the mobile version.

    I can add a cookie to this land­ing page to remem­ber the choice for future sessions.

    Would that help? Let me know!

Previous post:

Next post: