Filed under

design

 

Coding Update #3: MicDroid

Launcher-icon

Pronounced McDroid (i.e. McLovin'), it's a wildly successful Android app created by a friend. I feel privileged to be entrusted with creating the ui, from concept to code.

The latest release as of this writing features the first release of the new ui. There's much more in store for the app. Development has been very organic and fun thanks to Github. There, you'll see the inner workings of the app: like my first 100 or so lines of xml to write layout, the file structure of the resources directory that map the support for various phone types, and the nine-patch images that save tons of space. I only wish this was the base model for making websites. The xml format certainly feels very powerful, I may even prefer it over html+css. Also, a big thanks to the Android designers at MtV for the base materials psd files that really sped up my photoshop work. Overall I've had a pleasure learning tip of the Android api. In terms of what's baked in for the ui, it still doesn't feel completely baked, but already I prefer it over other, ahem iOS ahem, platforms.

I know I've been gone for at least a few "blogosphere epochs," there's more posts in store. Image below is actually a comp and not 100% the final product.

Draft

Filed under  //   Google   design   development   mobile web   web  

Essay: Navigating The New Housing Boom

blogpost header: a city of markup, a house in focus with #fff hex on its roof

Websites are like houses. The creator of Django confirms this idea I've had in my head for a while. While I lack his experience working with the internet, and I have not worked in construction or studied architecture, I see the similarities in the processes. I also believe these similarities will can help us correctly defined the future of websites.

Definitions

Most websites are, or should be, functional, so they're rarely foremost works of visual spectacle. I am excluding the genre of the Flash-based brochure sites, as they are closer to commercialized movies. I am referring to sites that foremost deal with data: its storage, distribution, presentation, aggregation, and management. Since the internet is about interacting with information, it doesn't do much good if the information is static, like in a brochure site. Therefore I'm referring to sites where the data is very dynamic. Of course, it doesn't matter what the site does; sites do a lot of things, from tracking your life to being a game.

If making websites was about visual spectacle, it would be more like making a painting or a movie, all about the visual feel with little concern about supporting functional, non-linear interactivity. Rather, making websites is different and harder in two ways. First, websites, like other software that support user-interaction are non-linear. This changes a lot of the underlying creative thought process. Instead of just imagining the natural, cumulative, visual progression of strokes on the canvas or frames in the clip, you have to think of use cases, the variety of paths that branch and fork depending on what the user is looking for. The user is given too much interactive power for linearity to work.

And that's how, for a while now, I've realized like many, many others, the website of our time is actually software.

Analogies

And making software is like making houses. Both tasks take a very long time. There are numerous stages, and I'm sure, variations of processes for projects of various scale. There are many components and with them, are constraints. And these standards must be met, or the result is unusable. Just like poisonous Chinese drywall doesn't meet standards, make people sick, and devalue the houses they're in; a website where there are ads anchored to malware or flash banners that interfere with the layout and content upon mouse-over will drive away readers and actually lower revenue, thanks to ad-block features on browsers and userscripts. Or something as careless as forgetting user-friendly color contrast.

Read the rest of this post »

Filed under  //   WordPress   design   development   frameworks   usability   web   writing  

Photoshopped

Poster_preview

First time using Photoshop for something it was originally designed to do. Can't say I am too pleased with the result, but it is a rushed NFP job. Perhaps next time I'll check PsdTuts before starting.

The image will be printed on black clothing. 

Filed under  //   design  

Visual refinements

This Posterous thing is pretty neat. Although the interface is a bit clunky, with the new theme feature, I'm really sold on this as a decent, low-overhead blogging platform. I'll admit the default html/css doesn't exactly follow best practices at parts, but it sure beats what I've seen in some themes in other blog platforms; ahem WP. 

Filed under  //   Posterous   WordPress   blogging   design   usability   web  

A real post on design

Though I subscribe to them, I've had it with the so-called 'design' blogs and their unending streams of linked lists. Let's forget for now how much of a hassle it is to be able to keep references to all of these individual posts, since designers who blog probably can't be bothered with using a wiki, since they're so gawd-awfully hideous. No, let's just talk about quality of content. It bothers me that gradients and starbursts are presented as exemplary design. From the content on these blogs, you'd think to design a better frontend web interface, all it takes are some grunge textures, drop shadows, and large social networking and syndication icons. Though I'd have to conclude from the standpoint of sensible, human-friendly design, that concoction just makes it a gawdy, user experience nightmare. There's a reason the websites of most agencies and professionals stay clean of such fads. WordPress theme designers take heed.

Bottom line. The web designer in me is more interested in real innovations in user-friendly interface design. And the print designer in me is more interested ways for layout to highlight and enhance content. Neither side really cares about textures and gradients. Under most circumstances they're benefits are not worth their weight. Expect a link to a list of resources and articles, on a wiki page.

Filed under  //   WordPress   blogging   design   web