kellishaver: There’s no simpler way to put it. The way we use the Internet is changing, and it’s changing quickly. Let me start off by throwing some statistics at you (courtesy of @jonathanstark):

  • There’s no simpler way to put it. The way we use the Internet is changing, and it’s changing quickly. Let me start off by throwing some statistics at you (courtesy of @jonathanstark):

    • 25% of US mobile users almost never access the internet via desktop or laptop computers.
    • The growth rate of mobile traffic is expected to increase tenfold over the next five years.
    • There will be 5 billion mobile broadband subscribers by the year 2016.

    Here’s another staggering statistic for you: 76% of all internet traffic out of Africa comes from mobile phones. There is a very large percentage of the continent that doesn’t have electricity, or running water, but you can bet they’ve got Facebook. The technological revolution in Africa is going to skip the computer entirely.

    As designers and developers, it’s up to us to shape the web, but if we don’t get on board with the change, we’ll get left behind. Even worse, the Internet will become a less friendly, less accessible place.

    Changes in how we use the web require a change in thinking about how we construct the web.

    Here’s another point to consider: given the rapid growth rate of mobile devices, how long will it be before device APIs currently available only to native applications become part of the standards by which we design and build web sites? We’re already beginning to see this with geo-location services. How many more years will it be before we, as web developers, have access to the camera, the gyroscope, the light sensor, the accelerometer?

    If I were guessing, I’d say we’ll see at least some these by 2016, as well.

    So what do we do?

    Clearly the mobile web is growing fast, but where do you make the switch? What’s the breaking point, and how do you build an accessible, responsive Internet when device and platform fragmentation is greater than ever?

    There answer is to start now, stay lean, stay flexible, and adopt a new approach. In short:

    • Start with Content
    • Build for Mobile First
    • Develop your apps and sites around an API
    • Accessibility is Key

    Let’s take a look at these…

    1. Start with Content

    It doesn’t matter how your site looks or functions, if you don’t know what it’s saying. Clearly defining your content before beginning development allows you to more easily build cross-platform, cross-device ways to create, view, and interact with that content. It’s like having a road map. It’s the precursor to planning your user experience. Get your content organized, and the UX often defines itself.

    2. Build for Mobile First

    With mobile web usage on the rise, it’s only wise to start with the small screen and work your way to the larger ones. Media queries and meta tags largely ignored by desktop browsers make it easy to create responsive layouts that adapt to mobile devices, and it’s far easier to start small and go bigger than it is to try and build in reverse. Mobile first also often means better fall-backs for old browsers and old technology, and an overall cleaner layout in general.

    3. Develop your apps and sites around an API

    This is still a somewhat uncommon approach to web development (though it is certainly gaining in popularity among web app developers), but for the ultimate freedom and flexibility, start with an API and then build your web site or client on top of this.

    Think of it as one more step in separation beyond the MVC pattern. Your API doesn’t present anything, not even so much as a paragraph tag. It just accepts data and spits data out in return, but if you build a rock-solid REST API, your client can be anything.

    Forget just serving up HTML pages. Do you want to access your content from the command line, over instant messenger, via e-mail, SMS, or even voice? Yeah, API-centric development will let you do that without having to redefine the application at each step. Your client determines the terms and scope of interaction, while the API does all of the heavy lifting on the data.

    Your API encapsulates the core of your application and then multiple, lightweight clients, such as an HTML/JavaScript front-end, a command line client, or a text-to-speech translation service, sit atop that and provide access in any number of ways on any number of platforms.

    4. Accessibility is Key

    Point four is the reason we do one, two, and three. Accessibility no longer just means a screen reader, or building a site for someone with low vision. It also means agile language translation, low-tech devices, slow-speed connections, voice activation, and touch gestures.


    The changing web isn’t about the growth in mobile access. It’s about the growth in people. Mobile is a means to an end, and while the way we deliver the web may be changing, it also affords us an incredible opportunity to reshape and rethink the tools we use to deliver content. With mobile as the catalyst, we can now step back and look at how we can adapt, in this new landscape, to building applications and web sites that are friendlier, easier to use, and more available to all users.

MEISA Presents: Coachella 2012

I’m apart of a student organization called the Music and Entertainment Industry Student Association (MEISA for short), and we just had an amazing Coachella viewing party this past weekend at Woody’s Tavern at the Ohio Union. Luckily for us, Ohio State’s student newspaper, The Lantern, decided to cover the event for the Arts and Entertainment section.

Here’s an excerpt from the article written by Kaitor Kposowa:

The OSU chapter of Music and Entertainment Industry Student Association hosted a viewing party of the first weekend of the 2012 Coachella Valley Music and Arts Festival. The music festival is held annually in Indio, Calif.

The first weekend of Coachella took place April 13-15. The viewing party was held Saturday at Woody’s Tavern at the Ohio Union.

“We knew that Coachella, in years past, had streamed the event on YouTube and we were just like, why not just bring the best of Coachella to OSU?” said Sean Doran, a fourth-year in new media and communication technology and director of public relations for MEISA.

Click to read more.


DC Comics Logo


When I first looked at the new logo design my first reaction was, oh it’s a peeled back fold over the letter C? But then when I read the thinking behind the actual process and how this identity may be used in website and mobile form it totally makes sense. It’s a fantastic example of the way…



Who doesn’t love a good UX design, and who doesn’t get totally frustrated with bad experience design. Hail to all the great UX designers of the world. ILUVUXDESIGN


Fluid Icon for "mite."

It’s simply not possible to create excellent, detailed icons which can be arbitrarily scaled to very small dimensions while preserving clarity. Small icons are caricatures: they exaggerate some features, drop others, and align shapes to a sharp grid. Even if all icons could be executed as vectors, the largest size would never scale down well.


Content Audit Template


Flickr: Royalty. by vasta
by vasta

Businesses live and die by the usability of their services, writes Continuum’s Rick McMullen. But how do they know when there’s a serious problem?

“The worst thing you can do to an adult is make them feel stupid.”

WANTED: Work Experience

MEISA @ OSU: Internship Super Fun

So you’ve wanted to get into the music business? Getting some work experience isn’t a must, but it’s extremely recommended so you can put it on your résumé, network like a boss, and also just to see if it’s what you’d want to do for a career. This week we’re going to have a couple of our members share their internship experiences.

This Wednesday: Awesome (And Free) OSU Event


Also, there happens to be an awesome event being held at the Ohio Union: OUAB & OSU Hillel Present Funny Men: An Inside Look into What Makes America Laugh this Wednesday. The doors open at 6pm, and the show starts at 7pm — and it features Doug Ellin – the head writer of Entourage, Kenny Schwartz – executive producer and writer for American Dad!, & David Javerbaum – the former head writer and executive producer of The Daily Show with Jon Stewart.

So, see you guys Tuesday and Wednesday this week, and let’s try to be awesome. Hell yeah.

Completely Unrelated to UX - MEISA

In addition to going to school and working, I’m also the PR Chair for the student organization MEISA (Music & Entertainment Industry Student Association) here at OSU. I figure I might as well get the word out on here as well. Check out below for the post I just wrote about this upcoming quarter.

MEISA - Music and Entertainment Industry Student Association: O-H-I-O Winter Quarter

It’s the last winter quarter here at The Ohio State University before semesters kick in, and we better make it one to remember. Our first meeting of the quarter is happening tomorrow (Tuesday, January 10th), and we’ve been shifted to Lazenby Hall 034. For more info about this week, returning members, and new prospect members, read more and be amazed!

Read More

My First Website Evaluation

My First Website Evaluation

I’m free! My 2011 fall quarter is over and done with, and I have a glorious winter break ahead of me, but that doesn’t mean I’ll be slacking off. I’ve been recently getting more involved with some LinkedIn groups that deal with Usability, Graphical User Interfaces (GUI), and the User Experience (UX) just to learn more from professionals, and give my two cents.

So, I figured I’d post one of my assignments I did for school, and see how it’s received – and don’t be afraid to comment on other ways to improve the evaluation.

Read More