dotMobimobiThinkingmobiForgemobiReadyDeviceAtlasgoMobi

Posted by camper2020 1 year 40 weeks ago

pic
 camper2020
mobiForge Newbie
Posts: 1
Joined: 1 year ago
[offline]

Hey Everyone,

I am new to mobiforge, but already, I'm seeing the good a site like this does. I am a post-graduate Multimedia Student but also work for a web development company. This year I began developing sites for mobile and I came across those familiar design issues, particularly when it comes to browser compatibility. However, with mobile, the problem is a million times worse.

As I'm studying, one of my subjects requires me to write a mini dissertation and do some research. What I've decided to do is compile an archive of the different ways mobile browsers render and support CSS (1, 2, and 3) I do realise that this is only one issue, as successful mobile rendering relies on much more than CSS and there are the efficiency concerns of having too much CSS to begin with.

However, I think it will help to give developers less of a headache when developing for mobile, where they can go to one central place and see what code works with which browsers.

I want to create a Wiki with all the CSS rules set out by the W3C and create areas where anyone can add their experiences with a particular device and the CSS it renders.

This is what I want to know: Would you reckon something like that would be helpful?

Would you use such a Wiki?

Would you contribute to such a Wiki?

Does a Wiki or similar area like this exist already? (I don't wanna do something that's already been done)

Regards,
Camper2020

Posted by mattan 1 year ago

pic
 mattan
mobiForge Enthusiast
Posts: 17
Joined: 4 years ago
[offline]

Hi Camper2020,

That's quite a project you got right there. First of all I would like to point out that there some efforts done already, although not complete, such as WURFL and DeviceAtlas. WURFL for instance, does not report if a device has full CSS1/2/3 support but rather support for a few common css functions; css_gradient is one.

It's quite a complex task to test if a device has full functionality of a CSS version. And is that even desireable? Most PC browsers don't even fully comply with the CSS standards, take the acid3 test as an example. There are also quite a few mobile browsers/versions out there.

When I develop a mobile website I usually make it very simple to begin with, and then i might to a version specially for iPhone/Android which has a big market share and can render quite advanced stuff.

I don't think I personally would use a wiki when I develop, I rather make calls to WURFL or similar if there is something special I would like to render.

But hey, that's jsut my two cents. Others might have a completely different view on this.

Good luck!