This link has been bookmarked by 22 people . It was first bookmarked on 28 Oct 2008, by M Tschofen.
-
05 Feb 09
-
30 Jan 09
-
26 Dec 08
-
26 Nov 08
-
14 Nov 08
Johan LarssonA few weeks ago we released a version of the Flickr site tailored specifically for the iPhone. Developing this site was very different from any other project I’ve worked on; there seems to be a new set of frontend rules for developing high-end mobile site
-
10 Nov 08
Frederik Van ZandeA few weeks ago we released a version of the Flickr site tailored specifically for the iPhone. Developing this site was very different from any other project I’ve worked on; there seems to be a new set of frontend rules for developing high-end mobile sites. A lot of the current best practices get thrown out the window in the quest for minimum page weight and fastest load times over slow cellular connections.
-
08 Nov 08
Marcel WeissHere are a few of the lessons we learned (sometimes painfully) while developing this site.
-
1. Don’t Use a JavaScript Library or CSS Framework
-
2. Load Page Fragments Instead of Full Pages
- 3 more annotations...
-
-
3. Don’t Build for Just One Device
-
4. Optimize Everything
-
5. Tell the User What is Happening
-
-
-
05 Nov 08
Nicolas HoizeyThere seems to be a new set of frontend rules for developing high-end mobile sites. A lot of the current best practices get thrown out the window in the quest for minimum page weight and fastest load times over slow cellular connections.
-
29 Oct 08
-
28 Oct 08
-
1. Don’t Use a JavaScript Library or CSS Framework
This was one of the hardest things for me to come to terms with. I’m a huge fan of libraries, especially YUI, mostly because they allow me to spend my time creating new stuff instead of working around crazy browser quirks. But these libraries walk a fine line; by definition, they must work across a wide array of browsers and offer enough features to make them worth using. This means they potentially contain a lot of code that you don’t care about and won’t use. This code is dead weight to your site.
-
2. Load Page Fragments Instead of Full Pages
- 2 more annotations...
-
-
3. Don’t Build for Just One Device
It’s really tempting to build the site for just the iPhone: you can use modern CSS (including things CSS3 selectors and transformations), you don’t have to hack around annoying browser quirks, and testing is extremely easy. But any single device, even one as ubiquitous as the iPhone, has a limited share of the mobile market, especially internationally. Rarely can you justify the cost of creating a one-off site for a very small number of your users.
-
4. Optimize Everything
The browsers on mobile devices operate under much stricter constraints than their desktop cousins. Slower CPUs, smaller amounts of memory, and smaller hard drives mean that less data can be cached. On the iPhone, for instance, only files smaller than 25 KB are cached. This puts very specific limits of the size of your files. For a large site like Flickr, 25 KB worth of JavaScript and CSS barely scratches the surface. To put our files under the limit, we ran everything through the YUI Compressor using the most aggressive settings. We ran all images through compression tools as well (we like pngout and Smushit), reducing each image file by an average of 40%. We also made heavy use of sprites, where possible.
-
-
-
Brad BrooksInteresting...
webdesign iPhone CSS javascript webdevelopment flickr optimization mobileweb
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.