I think this is worth mentioning: I spent the better part of today trying to fix a layout bug in Internet Explorer 7, where a negative margin was applied to a floated image container. The image was cut off at the edge of the containing element.
This is actually a well known-bug - in theory - and a reliable fix is to add a “position: relative” CSS rule to the floated container. But it didn’t work.
After a lot of research and tearing out of hair, followed by careful debugging (aka “wildly flailing about”), I discovered the reason. The containing element had a Internet Explorer proprietary filter applied to it, to give a semi-transparent fill:
/* For IE 8*/
-ms-filter: “progid:DXImageTransform.Microsoft.gradient(startColorstr=#59000000, endColorstr=#59000000)”;
On removing this, everything worked perfectly. So I just used a semi-transparent PNG as a fill image instead. Probably more efficient anyway.
I joined the team working on the Wazzamba virtual world back in April 2009. And now we’ve launched in the real world.
Wazzamba is a virtual world with a twist: it includes built in games which allow you to build up a score to compete for real world travel prizes. Every week, we award 4 prizes. So far we’ve given away quality, all expenses paid trips to China, New York, Las Vegas and San Diego. Forthcoming destinations include Spain, Rome and Australia. And actually winners can select an alternative if they don’t like the headline.
The virtual world itself so far has 6 “cities”, each sub-divided into areas, for example Sunset Strip in LA (you can see me there on the left with my friend Marilyn). And we’re growing.
So how do we make any money out of this ? Well the idea is you pay a subscription to take part, at “silver” or “gold” level. The higher the level, the higher the number and value of prizes you qualify for. But you can play - and win - for absolutely nothing. Zero, free, peanuts. Although we’d be terribly grateful if you didn’t.
My part in all this in theory involves building up a mobile channel, from a mobile-enabled web site up to an iPhone application. But I’ve also ended quite heavily involved in building our Facebook applications and presence, as well as a blog built on Wordpress.
It’s early days yet and Wazzamba is not fully mature. But it’s certainly worth a few minutes of your time. My avatar there is called Ostakokur and has great dress sense. Don’t forget to say “hi” if we meet!
I’ll say it right away, this is a 5-star, thoroughly excellent book. The biggest puzzle is why it has taken so long for somebody to write the definitive text in this space, but anyway, Brian Fling has nailed it.
Written in a deft and engaging style, with a touch of weary cynicism about the old operator-dominated order of the mobile space, and the legions of executives who neither get it, nor accept that anybody else does, this is an absolute must read for anybody getting into mobile development of any kind on any device. I really get the impression that every page has been obsessed over, that the author really, really cared about getting it as good as he could - which I’m afraid to say is not too common in the field of technical books, and especially some about the mobile web.
The author covers pretty much all aspects of building mobile applications, from a discussion of the ecosystem (which should be a real eye-opener to newcomers), to the all-important topic of context, to mobile-specific information architecture, usability, interaction and visual design. Despite the big changes heralded by the iPhone and it’s competitors, the book is right up to date, including discussion of WebOS and Android.
What I really like is the way he avoids sitting on the fence. Rather than surrender to the calls for lowest common denominator design, he encourages designers to be creative and take risks. In my opinion, there’s a strong argument for going out on a limb aiming to build an application people will upgrade their phone to be able to use, rather than be dragged down to level of 120 by 160 pixel monochrome devices - who’s owners are unlikely to be big data services users anyway.
Some parts could be a bit clearer. For example, when the author discusses the concept of teasing the content to improve user experience, I’m pretty sure I know what he’s talking about, but the illustration given (figure 7.6) is so unclear that I’m half sure it’s an editorial error. Or it could be a case of over-channeling the lauded, but in my opinion, unnecessarily opaque, Jesse James Garrett. Surely an actual example with page screenshots would be a better way of getting the point across ?
I’ve been working in this field for over 7 years, and I’ve experienced most of the frustrations described in these pages. There isn’t actually much in this book which is really new to me, but seeing things spelled out so clearly is refreshing and encouraging, and provides some very timely reminders.
If you’re developing for any mobile platform, iPhone included, you will be well rewarded for the you invest in reading this book. Brian Fling has suffered so that you don’t have to ... well, not too much anyway.