Add this Infographic to Your Website:
Simply copy the code below and paste it into the HTML of your blog, website, or Static FBML box on Facebook
This infographic was submitted to us by the folks at AYTM. They gave us this description, too:
“The iPhone debuted in 2007 and Apple has sold well over 100 million devices to date. With Piper Jaffray analyst Gene Munster predicting that 18.8 million iPhone 3GS users will upgrade to the iPhone 4S within the next year (which will account for 18% of sales), AYTM put together an infographic from our research for some insight into the apparently never-ending iPhone phenomenon.”
This is a wonderful example of a really informative and thorough infographic. Yeah, there’s a decent amount of text here, but the balance is what’s important. The text serves important functions, like listing features or providing context for/summarizing visualized statistics. There are way more visuals than there is text, so to use some internet speak: “ur doin it rite.” (You’re doing it right.) The colors and design fall right in line with Apple aesthetics, but the unique illustrations don’t make it look branded or gaudy.
There are just a few technical problems throughout this infographic. The most common is inconsistency in capitalization (the features of the various models of iPhone under “The DNA of US iPhone Users,” for example, or apps/Apps). Attention should be paid to the accuracy of copy just as in the accuracy of data.
My favorite examples of data viz here are (can you guess?) “Time distribution of device use” and “Features and benefits the next iPhone must have.” These are really unique graphs. While it takes the uninitiated viewer a few moments to work out how to read them, it’s worth the investigation. Pie charts and bar graphs will always have a place in data viz, but it’s always more exciting to see people play around with new formats.
Overall I’d give this infographic an A-. It does a really great job of telling its story in an accurate, attractive and unique way. I tend to have a hawk-like eye for typos on the work of others (and appreciate others correcting me, even if I do take it personally… haha), so for me the capitalization issues are the only thing holding this back.0