Some browsers (Safari, Opera mini) are almost as good as their desktop counterparts, but others are very bad, so it's best to plan for the worse, and use progressive enhancement for more capable browsers.
I'd recommend keeping only the parts that you need from blueprint, for the following reasons. 1. IE for mobile only has a very small percentage of the mobile browser market, and probably other bugs too. 2. The reset and layout style sheets are probably wasted bandwidth compared to the number of browsers that will indeed use them. I haven't built any mobile website (the French market is painfully slow in gaining mobile awareness) but here's how I'd build a mobile webpage. 1. Branding (short text or small image, no fancy image replacement technique) 2. Content (can be navigation on the homepage and redirecting pages) 3. Navigation 4. Link to a basic stylesheet customising html tags: text, links, body, lists, etc. 5. Use media queries to add layout and CSS decoration, place the navigation in a sidebar, etc. You'll find great resources at http://www.quirksmode.org/m/ and http://www.w3.org/Mobile/Dev Hope that helps! On Tue, Aug 4, 2009 at 7:11 AM, WootWoot1234 <[email protected]> wrote: > > I'm developing a website/webapp and am looking for a css grid system > that I can use for the mobile version. I can't find anything on the > blueprint site. Anyone know of a grid system for mobile devices? Can > I just use blueprint? What have other people done? > -- Goulven Champenois --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Blueprint CSS" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/blueprintcss?hl=en -~----------~----~----~----~------~----~------~--~---
