vanderwal.net

Final Cut Pro Site is Stunning

I am not sure when this started, but Apple has started showing its product stories for Final Cut Pro in stunning video. I have been watching and saving down the movies. They are so much better than text for getting me sucked into the story and the pitch. They are each so stunning. So very Apple. Finally!

Apple Pro tools are some of the best on the market and not only put others to shame, they are much less expensive. I have been playing with the movie capabilities in iMovie HD this past week. In 10 minutes I can shoot a movie of my son, edit, and publish to a web page that I can mail those I want to see the page. That to me was hands down incredible. I am not dealing with HD quality video, but the capability is fully there. I just wanted to share a clip with friends and family quickly and get back to work.

Yes, 10 minutes. I have had iMovie for a few years and never played with it much. When I moved to a faster PowerBook this last year I started realizing the potential that was in my hands.

I am continually in awe of Apple for its simplicity, power, beauty, and potential it puts in my hands.

For Many AJAX is Not Degrading, But it Must

A little over two months ago Chad Dickerson posted one of the most insightful things on his site, Web 0.1 head-to-head: 37Signals' Backpackit vs. Gmail in Lynx. You are saying Lynx? Yes! The point is what 37Signals turns out degrades wonderfully and it is still usable. It could work on your mobile device or on a six year old low end computer in Eritrea in a coffee house or internet cafe (I have known two people who have just done that in the last year and found Gmail did not work nor did MSN, but Yahoo did beautifully).

Degrading is a Good Thing

Part of my problem with much of the push towards AJAX (it is a good, no great thing that XMLHTTPRequest is finally catching on). But, it must degrade well. It must still be accessible. It must be usable. If not, it is a cool useless piece of rubbish for some or many people. I have been living through this with airline sites (Continental), commerce sites (Amazon - now slightly improved), actually you name it and they adopted some where in this past year. In most cases it did not work in all browsers (many times only in my browser of last resort, which by that time I am completely peeved).

When Amazon had its wish list break on my mobile device (I (and I have found a relatively large amount of others this past couple years doing the same thing) use it to remember what books I want when I am in brick bookstores and I will check book prices as well as often add books to my wish list directly) I went nuts. The page had a ghastly sized JavaScript, which did some nice things on desktops and laptops but made the page far too large to download on a mobile device (well over 250 kb). In the past few weeks things seemed to have reversed themselves as the page degrades much better.

Is There Hope?

Chad's write-up was a nice place to start pointing, as well as pointing out the millions of dollars lost over the course of time (Continental admitted they had a problem and had waived the additional phone booking fee as well as said their calls were up considerably since the web redesign that broke things for many). Besides Chad and 37Signals I have found Donna Mauer's Designing usable rich internet applications as a starting point. I also finally picked up DOM Scripting: Web Design with JavaScript and the Document Object Model by Jeremy Keith, which focusses on getting JavaScript (and that means AJAX too) to degrade. It is a great book for designers, developers, and those managing these people.

I have an awful lot of hope, but it pains me as most of us learned these lessons five to seven years ago. Things are much better now with web standards in browsers, but one last hurdle is DOM standardization and that deeply impacts JavaScript/DOMScripting.

My Book Highlights from 2005

I had been hoping to do a longer post on things I enjoyed in 2005, but the year end has been a little busier than planned (it is a good thing). There are lot of books that I picked up in 2005 (possibly in the 30 to 50 range). Two from earlier in the year I really enjoyed, John Thackara's In the Bubble: Designing in a Complex World was a huge favorite. It has brought to mind many changes that we need to address as people who design and build things. The second was Personal, Portable, Pedestrian : Mobile Phones in Japanese Life by Ito, Okabe, Matsuda (editors), which provided insight into the Japanese mobile culture. Some of the cultural aspects to dot translate to the United States, but it does a wonderful job of raising awareness for introspection into one's own culture. The book also does a fantastic job of providing history and technological change and differentiation in use based on product types.

The couple months I have picked up some books that I will really have an impact on me. Shaping Things by Bruce Sterling my be my favorite book of the year (with the Thackera a close second). Shaping things gets to where we are going with design in an innovative way. The design of the book is playful and makes for a quick read (unless it gets your mind wondering in wonderful ways, as it did mine). It is a book I could not more highly recommend.

I finally picked up DOM Scripting: Web Design with JavaScript and the Document Object Model by Jeremy Keith and was pleasantly impressed with the coverage of pages that degrade properly. This book is required reading for anybody doing JavaScript or AJAX so to stop the madness with sites that do not work across browsers or mobile devices. There are far too many sites that have developers that did not learn anything from the mid to late 90s and using JavaScript that are making unusable sites, pages, and applications today. If you are a manager of interface developers this is written in a manner that it should be easy to read and make sure the developers working for you are following these guidelines.

My favorite fun book was recently released book in Britain, Against the Wall by and about Banksy. This is a collections of Banksy's street art and wonderful sense of play. I personally find it a great book to break through conventional thinking and get to the other side. This book is not currently available in America, which is an utter shame.

I may do a posting on music from 2005 I really enjoyed in the next day or so. But on this note, I wish you a wonderful new year and great things.

Design Engaged and Symposium on Social Architecture

I got back home late Tuesday night from Design Engaged in Berlin and Symposium on Social Architecture in Cambridge, Massachusetts at Harvard. I had a deadline to meet by midnight Tuesday. Much of Wednesday was spent unbolding e-mail and getting essential replies out (more of this to do today) and unbolding my feed aggregator (1500+ things). I also spent time posting photos of the trip to Berlin (currently at 216 photos, possibly a few untagged).

Design Engaged

Design Engaged was somewhat different from last year's event in Amsterdam. It was still interacting with many of my favorite people, but it was a little larger, in a new space, in a new city (one I was not familiar with), and had a larger representation of women. All of these turned out good, but I felt a little more disconnected. The disconnection I think was attributable to an unfamiliar city, staying at a hotel away from where the sessions were, and not having most of the people staying at the same hotel. I tended to stick with those staying at my hotel, which was good for those relationships. But, part of this was tied to my unfamiliarity with the city.

This unfamiliarity changed for the better and I have learned something about myself, and that is all good. The unfamiliarity shifted to familiarity. I got to know some incredible people and spend time with people I knew, but now know much better. I got to know Berlin. I have not been to a completely new city that I had time alone in quite a while (Brussels last month was new to me, but I was with a large group I had become familiar with, I all were staying in the same hotel, and I had very little interaction with the city itself). My first impression of Berlin was good, nothing more and nothing less. This was formed on an outing to Potsdamerplaz and walking back through Mitte.

Part of the Design Engaged experience is interacting with the city. A group of us headed out to Friedrichshain, which was part of East Berlin and is not being torn up and made western to the degree that Mitte or Alexanderplaz have been and are going through. This was the perfect outing for me as I really wanted to understand East Berlin or get a flavor of what pre-unified Berlin was like. I was interested in the Soviet style architecture and the working neighborhoods. Why? They are something I do not understand and had not experienced. I was utterly thrilled with our exploration of the area, both on our own and with a local who life is in that neighborhood.

I also learned a fair amount about myself on the Berlin part of the trip. I use various supports to explore that which is new. I use friends to guide in new surroundings and meet new people. Familiar surroundings to best embrace new people and expand my knowledge of the surroundings. I learned that having much new causes me to fall into an observation mode and a little less interactive. There are people I really wanted to get to know better and spend more time with. I tended to spend time with the people I already know well, in part to catch-up and get to know better. I also spent a lot of transit time trying to take in as much of my surroundings as possible. Understanding the lay of the land, the flavor of the neighborhood, trying to glimpse what the neighborhood was, what that neighborhood is becoming, and the expression of the people who live in and move through that area. The architecture, design layers (planned and emergent layers -- painted and overlayed), traffic patterns, lines of sight, etc. are all important components to understanding the people, their interests, and indicators of importance. Digging through the international layers (Starbucks (particularly behind the Brandenburg Gates is problematic), Duncan Doughnuts, American brand advertising, and global mass produced products), which in my opinion are disruptive to the local culture.

After returning home I know I have a much better understanding of Berlin and it is a city I would love to return to so to spend more time and explore. Now that I have a foundation of understanding I am ready to drink in more. I also realized that observation limited my getting to know others better than I would have liked. Ever single person at Design Engaged this year was utterly fantastic. It is a very special group of people. There are no egos. There are no agendas. There are people who love sharing, learning, embracing, and exploring. This is something very special and something very different from most any other gathering. Part of it is the event is not about certainty, but exploration, asking questions, listening, and growing all in a shared experience. Unfortunately I am more ready to engage others and interact now that I am home, but hopefully there will be more time.

Symposium on Social Architecture

Counter to the Design Engaged the Symposium on Social Architecture was in a somewhat familiar place, but I only knew a few people prior. I knew many from digital interaction, but personal "in place" interactions were limited. There were more people who knew of me, than I knew of prior. I was continually having to put people in context of digital and idea spaces (some of this is now connecting). I had somewhat slept much of the journey from Berlin to Boston (transferring in Washington, DC) so I was not really dealing with jet lag. On the first night there was a reception at the Harvard Faculty Club and I met many fantastic people. I noticed there was a fair amount of clustering by gender, which was bothersome as there were a few women I wanted to chat with, but I found some very good discussions in the men's clusters and did not break free. There are many women whose work I find insanely helpful and wanted to say thanks and engage in some longer conversations.

The symposium was utterly fantastic. Every session had something I really enjoyed and there was a lot of reassurance of my own understandings and directions. I am not as fully engaged in the social software realm as I would like as it is an insanely important component of how we do things on the internet and it is growing ever more important. Much of my work discusses the Local InfoCloud as an intersection with the Personal Infocloud.

I have a lot of notes from the day (but more complete notes will be expressed in a later posting). I heard a lot of mention of local (closeness drawn through interconnection in social contexts), which was a reinforcement of my understanding as well as the language (or problems with the language) I have been dealing with at times. I heard a lot of discussion of all current social software is simple software, as it is easy to understand what the value is and the barrier to entry is a relatively painless in comparison to the reward received in the perceived value. Many also discussed building tools that got out of the way, they just let people interact. This was explicitly stated by Tina Sharkey of AOL, which made me very happy as it was a large social portal that expressed they understood what to do and have done it. It is not the tool that is important, so much as it is the social interactions that are the key. The tools should be a platform for connecting and communicating not for controlling.

I also met one of the people responsible for Steve, The Art Museum Community Cataloging Project, which could be the most important folksonomy and tagging endeavor that is ongoing. The importance is in part their work, but the research into tagging and folksonomy is insanely helpful and seems to be the best work out there at the moment. The work proves the strong positive significance that tagging and folksonomy plays in connecting people to objects and information. Having the world framed in a language or vocabulary is incredibly helpful and that is not often a result of formal taxonomies as they tend to optimize toward the norms and not embrace the edges. I will be writing about Steve more in the future, but I was so excited to meet somebody tied to the project so I could have more conversations and learn what they have found to be helpful and not so helpful.

The panel on politics and social software, particularly in relation to Katrina, was great. It highlighted the problems with politicians and their lack of understanding technology that could better connect them to their constituents, but also technology that could better enable solutions and resolution for their constituencies. I was completely moved by this panel.

The piece I had disappointment in was the closing. Er, the closing was Stowe Boyd interviewing me about what I found of interest from the day and what I would take home. Stowe asked the perfect questions, but I learned something about myself, I framed my responses literally and too personally. I let myself down in the responses as they were too general and did not capture the whole of what I got from the day nor the strong themes I noted. I was still taking in the politics panel and re-digesting the day based on that context. When I get a new perspective or new information I run the world I perceive through that lens and adjust accordingly and then emerge with a slightly reshaped or more inclusive framework. I think my closing remarks were poor, because I was integrating the last panel into my understandings. The rest of the day went largely as I expected, but the wonderful politics panel disrupted me in a positive manner. I apologize for the poor closing observations. For me it was the poorest part of a great event.

BBC Knocks Audio Annotating Out of the Park

Tom Coates shows off the BBC's Annotatable Audio Project. Tom gave me a preview early on Saturday and I was ecstatic. You see, what the tool does is provide an interface to annotate and segment audio on the web. Yes, podcasts can be easily segmented and annotated. This has been my biggest complaint with podcasts over the past year, okay since they started getting big (that is big for an early early adopter). I complained to people I knew at Odeo about the problem and they said they were working on it. I mentioned this to podcast enthusiasts at Yahoo! about nine months to a year ago and they said if they did podcasting that would be one of the first things in it as it was a big complaint. Did they? No, they made a product not too indistinguishable from every other product out there? Where is the innovation?.

Why is this Huge

The reason I am so excited about this is voice/audio is not easily scannable, like type. I can not easily skip ahead in a 30 or 45 minute podcasts to find that which I am interested in. Many friends will forward me links to a podcasts stating I have to hear what somebody says. Finding that segment usually means listening to much of the whole podcast.

The other downside is if I hear something stellar in a podcast my mind will mull over that item for a little bit. This means the minute to five minutes that follow in the podcast are lost on me. This is not a problem with written materials as I can skim back through the content and pick-up where my mind drifted (it is usually in these moments of drifting that I find the best solutions to things that have bugging me - the Model of Attraction came out of one of these).

A couple other items of note about this product. It is great interface design as it is interactive helps the person using the product know exactly what they are doing. The second is the segmentation is a great asset. With segmentation I can easily see writing a script to grab items of interest (27 seconds for here and 36 seconds from there, etc.) and having an automated audio stream built for me. Not only do I have a personalized audio stream, but since the originals are annotated and I can keep track of where the information is extracted from I can easily point others to the spot so they (or I) at some later point can go back and listen to more so to get better context (personally I don't think people are against attribution, it is just that we have made it so hard to do so in the past).

Voice and Audio is a Common Problem

The last couple time I have travelled in the USA I have run across people quite similar to me. None of us like voice. We are not particularly fond of the phone, for much the same reasons as I have problems with podcasts. Too much information gets lost. In phone conversations I am often saying, "I am sorry can you repeat that", in part because I did not hear, but the something that was stated just triggered a good though process for me and I missed what came after that moment. (What would be a great application is Tivo for the phone.) I continually am running new ideas and thoughts through what I believe and see how they may change it. It is the examined life - I enjoy living.

So what Tom and his cohorts did was make podcasts and audio more usable. It makes it searchable. One thing that would be a very nice addition is to have those annotating the information each have their own distinct layer. Just like with folksonomies, the broad folksonomy where each individual and each annotation on a distinct element provides a richer understanding and richer layer. (Such things would be really nice in Wikipedia so that I could remove the people who I do not think add any value to entries (in not polite terms - those who I know are wrong and are polluting the value of Wikipedia, which is far too much noise for me on the entries I would love to point to), or conversely to use a "white hat" approach and subscribe to the annotations of people and the distinct tags or terms they use in annotations. I have many people whose opinions and view I value, but on rare occasions it is everything a person has to say.

Filtering information in a world of too much information to keep track of is a necessity. Filtering is a must. It is about time we got here.

Thank you Tom. I hope your new team can innovate as much as you were allowed at the BBC, which has been the most innovative large enterprise going.

Europe Presentations

I am late in posting the links to my two presentations given in Europe. I presented the Personal Digital Convergence as the opening keynote to the SIGCHI.NL - HCI Close to You conference. I have also posted the final presentation, IA for the Personal InfoCloud, at the Euro IA Summit 2005.

Closing of the First Phase of the Fall European Tour 2005

I am back in Amsterdam tonight after a wonderful trip to Brussels for the Euro IA Summit. It was quite refreshing to talk to people that have a different perspective from Americans on IA, mobile, technology, privacy, and the possibilities for social interaction with digital devices. Last year after Design Engaged in Amsterdam I believed Europe to be farther ahead on internet and mobile (including mobile internet) than America. I now firmly believe Americans have a lot to learn from the Europeans.

I wanted to come and present the InfoCloud information in Europe because I thought they would be more ready for it. They would be able to provide criticism and questions that I do not get in America, mostly because the Europeans have been implementing mobile and trying to work through a means to access information in the environment and context where the information makes sense. Boy, was I right. The InfoClouds are more than mobile, as they are a means to think about information access, personally managing that information (or providing people the ability to manage, use, and reuse the information intelligently) and reusing it as that information is needed and framing the information in ways that make sense (web 2.0 fit this bill). I ran into smart thinking about web 2.0 here, not the just go do it, just open your information up, but working to think about if it made sense to do the cool and how they would do it intelligently.

The Europeans also really get cross-cultural sensitivity and are smart about how to approach working with other cultures. I was delighted to find what American's call internationalization is referred to as localization. How brilliant. How understanding. How unalienating. There is a distinct understanding that people are different and we need to understand that and embrace that. Hmm, there is a very strong reason why it is called the Personal InfoCloud and not the User InfoCloud. If you are not thinking in a local sense you will not get to the personal sense. You can get from localization to personalization, or from the Local InfoCloud to the Personal InfoCloud and also back. We all deal with more than one Local InfoCloud and I received some of the best questions about the interaction between the various Local InfoClouds and the Personal InfoClouds. Interaction be between the social part of personal it of immediate interest here. People are very tied to their communities here, it is a strong part of their identity.

I found myself surrounded this weekend by insanely smart people, who love what they do, and are doing things to help others. Everybody was incredibly friendly and genuinely interested in learning everything they could and sharing what they knew. I could not have asked for a better way to have spent any of this time. I would do all of this again in a heartbeat.

Thank you to all of those that I had the pleasure of sharing time with. Who were incredible hosts in their countries. Who asked and listened and from whom I learned to do the same, as when you listen you can learn. I learned an incredible amount. Thank you again. I am ever so much looking forward to my next two trips.

Peace!

Great Travel Bag

One very good thing I found out on this trip to the Bay Area. I love my new travel bag it is a Victornox carry on that is the same size as my (er my wife's) bag I had been using. This bag not only has more room in it (I fit three days of clothes (did not know what I wanted to wear), an extra pair of shoes, too damn many beauty products (but not toothpaste), and a bottle of Vitamin Water), it wheels around wonderfully (it did not tip over or tip on one wheel), and it is the first towing handle that I love. The handle curves so the bag is not only easy to pull, but it never hit my foot. This is a huge pet peeve with luggage with wheels (not that I want to go back to the days with only carrying luggage) they always clip the back of my foot when towing it behind, well until now. The wheels on this are very well placed and large, which mitigates many bag problems I have normally had.

When I get a product that is well designed, particularly one in a class of products that are abysmal or never design quite right, it is a great moment. The difference between this wonderful bag and others are rather small, but details are what separates commodities from great products (this is why I love Apple products and German cars).

Looking around the airport and plane yesterday I saw people battling their bags and I just wanted to tap them on the shoulder and say "just get one of these".

Personal InfoCloud at WebVisions 2005

The last few years I have kicked myself for not going to WebVisions, well I finally am attending, actually I am presenting my Personal InfoCloud at 1pm. This is the latest refinement of the Personal InfoCloud that I have been working on for four years and sharing with those that are finding it quite useful.

The essential information you need is that you should be at WebVisions 2005 in Portland, Oregon. It is being held July 15th at the Oregon Convention Center.

What do you say? "Join the giants of the Web world to explore the future of design, content creation, technology and business strategy. From podcasting to universal usability, you'll discover how the Web is interacting with digital devices to change the way we communicate, access information and do business."

Design Issue for Non-Designers

After reading more than 4 paragraphs of the June 2005 Fast Comany issue I have found I like the whole issue. I have not really learned much new, but it is one issue that I could just hand to so many folks to help bring their understanding of design and design process up to functional use. The issue discusses subjects like iterating and "T-shaped" people and offers up many lists, which are scattered through out the magazine.

Designing with a Solution is the Problem

I finally put my finger on it. There has been growing frustration within me with where I work and as well with some of the leaders in the web design community of late. The problem and the solution has been known to me, but scattered in pieces and I did not pull all the pieces together until today. Why today? Well, it took a little doing, but I finally got my hands on this month's issue of Fast Company - June 2005, which I had been subscribed to until the May issue. It took a little bit of time to track down the issue as it was to the point in the month when the next months issues are getting put out. But, having that issue in hand (having read some on-line) I stumbled across my tipping point in the Be Cooler by Design column. I did not make it past the fouth paragraph when it hit.

It Begins with a Canyon

The paragraph has a header, "Show Them the Canyon" and discusses a designer at Ford, Giuseppe Delena, who would say, "Don't tell me you need a bridge, show me the canyon!" This was aimed at marketing people who would ask for specific design solutions, but not explain the problem.

That is my tipping point. Having to start with somebody's solution to design problems (most often solutions to the wrong problem). Not having the problems put forward, but an answer. An answer without anybody showing their work to how their arrived at the solution. For nearly four years I have been working, for the most part, with the end results of the work of others who started with a solution and worked that as a starting point, while never considering the problem (or in nearly all cases the multitude of problems they needed to solve). They did not understand the problems nor do they understand or know the standards and requirements that their end result must meet. Lastly they do not understand the medium in which they are working. In short it is a string of considerable messes that our team deals with continually. The sad complication is this is taxpayer money being spent (often quite nice sums) for end products that require incredible fixing to meet minimum standards and be usable on the web.

It is not my direct customer, who is in the same boat I am in as we support him (and he is one of the very few that really get what they are doing), but the "customer service" management and the management signing off on these projects that have become the problem. With the web, the business customer is not always right, the user is, as without the user their is no business customer. In our situation, by-and-large, the web being built is using what works for print and for multi-media, neither of which are solutions for text on the web. The business customer requires solutions for the wrong medium, which (as those who have sat through usability test find out) the tan text on brown background and all of the animated bits make using the information as is it is intended, nearly impossible.

Designers Must Explain Design Better

In part the design world is to blame as we have done a very poor job of educating the rest of the world as to what we do. We solve problems. We have spent an inordinate amount of time on learning everything we can about our medium, how people think, how people interact with our medium, how people interact with their devices (desktop, laptop, PDA, mobile, etc.) as they are all different, how to organize and structure for people interacting with what we design, how to build for people to give them freedom to choose the solution that is best for them, how to build for ease of use by people, and how to build for people to easily reuse what we provide (the list goes on). Yes, it is not a short list and I do not know a good designer who will truly claim they are done learning all of these aspects. We know what works best with everything we do know for the problems before us and we test everything we do and we iterate through our designs while always striving to make things better. Every designer I know loves to show how they got to their solution and document it for others to do, as their joy in designing is not repeating, but problem solving and innovating to better solutions. As designers we are always trying to learn what others do, so the good designers share in as much detail so others may learn what to follow and what to modify for even better solutions down the road.

In my current situation the lack of time to document and show our work is a major problem. The lack of documentation (or deliverables) is part of where the problem lies with the problems up the food chain (not that there are skilled designers or people that would understand up the food chain). If we had the time to show our work we could hand it to those at the beginning of the process so we could get better products with fewer problems when we receive them (although it is a very rare occasion that any of what we have produced for these purposes is ever followed). Many of the places up the food chain have sold a bridge with out ever seeing the canyon it is just a cookie cutter. It is rare when we get to solve the problems, either at the beginning or the end, we just get to fix it so it will just pass the minimum requirements, which are horribly low.

Understand and Explain the Problem First

This frustration has also flowed over to the web design community of late as there is excitement in the web community again. The excitement is not bad, actually it is great. But some of the new solutions are being framed as new wonder solutions without framing the problem they are solving. In the world of design (as it is with many other things) it is a realm where the answer to most every question is, "it depends". What is the solution? It all depends on many factors in the problem. Teaching how to understand problems and to walk through the decision process to get to the solution (or more correctly, one of many possible right solutions) is what raises the profession.

What has been happening of late in the web design/development community is looking at solutions that may be terrific implementations for a certain problem in a set environment, but proclaiming what is new is "the new way". For those that are not good designers or even designers at all, this approach reaches a problem point very quickly. It was not long after XMLHTTPRequest was coined AJAX that customers, and those I advise from farther away, started asking for their solutions to be AJAX. There are right places for AJAX, as it is just one of many solutions for problems where it may be one of the solutions. It is quite similar to aura around Flash as a solution, but AJAX has its benefits and detractors when compared to Flash.

Where the problem around the AJAX solution got tough was when AJAX was tied to a whole new exitement around the web. It was at this point the AJAX solution was being demanded from customers. I was hearing if from many corners, this great solution touted, was for customers the only way they would accept their final products. AJAX had quickly become the cure-all in customer's eyes, much like Flash had years before.

Our Responsibility

What we have to realize as designers, is people do listen and people want to believe there is one simple solution for all of their web problems, all of the information problems, etc. We know there is not a simple solution as of yet. In fact the digital information world is far more complex than it ever was, as Europe and Asia will attest, with the influx of mobile handheld use. (Europe and Asia have things a little better than the U.S. right now, as they have much less of a population that believes build for desktop (including laptop) solutions is the one way all design is heading.) Europe and Asia understand the world is far more complex and information far more useful when it can be used in context on a mobile device. The expanding of the devices and the realm of possibile solutions with their benefits and detractors across the many variables we monitor componded the problems we are solving. Simplicity is many designer's goal, but getting there is ever harder today and we must embrace the complexity (thank you Mike for turning that light on for me) and work through it. We also need to communicate the complexity to our customers so everybody understands it is not as simple as it seems.

It is this complexity of convergence around devices is also compounded by the flood of information people are experiencing, which is what has me loving the work I get to do around the Personal InfoCloud (and the Model of Attraction and folksonomy that are intertwined with it). This work is satisfying as it is not only defining the problems and working through possible solutions, but more importantly laying out frameworks to design and build solutions that others can use. There are increasingly people (who may become customers) that are coming and asking the right questions from the right perspective around the Personal InfoCloud, which may be another reason I really like working on it (we all love people asking smart questions). People are asking how to cross their canyon while describing the canyon and many times showing me the canyon they would like a solution designed for.

I think we all know what the next step is. It will not be happening tomorrow, but every day that passes makes the frustration that much worse. Knowing there is one point around which much of my frustration revolves may help me deal with it better.

Response to Usability of Feeds

Jeffrey Veen has a wonderful post about the usability of RSS/Atom/feeds on his site. I posted a response that I really want to keep track of here, so it follows...

I think Tom's pointer to the BBC is a fairly good transition to where we are heading. It will take the desktop OS or browser to make it easier. Neither of these are very innovative or quickly adaptive on the Windows side of the world.

Firefox was the first browser (at least that I know of) to handle RSS outside the browser window, but it was still done handled in a side-window of the browser. Safari has taken this to the next step, which is to use a mime-type to connect the RSS feed to the desktop device of preference. But, we are still not where we should be, which is to click on the RSS button on a web page and dump that link into ones preferred reader, which may be an application on the desktop or a web/internet based solution such as Bloglines.

All of this depends on who we test as users. Many times as developers we test in the communities that surround us, which is a skewed sample of the population. If one is in the Bay Area it may be best to go out to Stockton, Modesto, Fresno, or up to the foothills to get a sample of the population that is representative of those less technically adept, who will have very different usage patterns from those we normally test.

When we test with these lesser adept populations it is the one-click solutions that make the most sense. Reading a pop-up takes them beyond their comfort zone or capability. Many have really borked things on their devices/machines by trying to follow directions (be they well or poorly written). Most only trust easy solutions. Many do not update their OS as it is beyond their trust or understanding.

When trends start happening out in the suburbs, exurbs, and beyond the centers of technical adeptness (often major cities) that is when they have tipped. Most often they tip because the solutions are easy and integrated to their technical environment. Take the Apple iPod, it tipped because it is so easy to set up and use. Granted the lack of reading is, at least, an American problem (Japanese are known to sit down with their manuals and read them cover to cover before using their device).

We will get to the point of ease of use for RSS and other feeds in America, but it will take more than just a text pop-up to get us there.

One Less Wonderful Merchant

Ismail Merchant has died. He and James Ivory's creations on films were magic. I clearly remember seeing A Room With A View at the Elmwood Theater in Berkeley, California when it came out. I later saw the film in Oxford, England at the Penultimate Picture Palace as well as on video tape there. The experience watching the film in two different cultures drew me to the film even more. In the U.S. the film was a period piece, but in Britain it was more of a romantic comedy. The film holds up to many watchings revealing details that may have been missed prior (opposed to the book, which has one good reading in it at best). It was this film that not only made me a fan of the Merchant Ivory productions, but made me a better fan or critic of the medium itself.

I have always enjoyed the interviews with Ismail as he adds depth and care to his creations. I believe that it is this care that should be poured into all of our creations and craft of our hands, mind, and soul.

Peace

Opening Old Zips and Finding Missing Passion

Tonight I finally got my old USB Zip drive to work with my laptop (I have not tried in a couple years) and it worked like a charm. I decided to pull most of the contents of my old Zips into my hard drive, as it is backed-up.

I started opening old documents from a project from four and five years ago and the documentation is so much better and detailed that what I have these days. The difference? Focus and resources. On that project I was researching, defining, iterating, and testing one project full-time. I was working with some fantastic developers that were building their parts and a designer that could pulled everything together visually. We each had our areas of expertise and were allowed to do what we enjoyed and excelled at to the fullest. Our passions could just flow. The project was torn apart by budgets and politics with the real meat of it never going live. A small piece of it went live, but nothing like we had up and running. But, this is the story of so many killer projects and such is life.

What is different between now and then? Today there is no focus and no resources to develop and design. I am in an environment overseeing 2,000 projects a year across 15 funding areas (most of the work done centrally is done on 5 funding areas), it is project traffic management, not design, not research design, not iterating, just balancing high priority projects (mostly it is 9 of us cleaning up others poor work). The team I work with is fantastic, but we have few resources (mostly time is missing) to do incredible work.

The looking back at the volumes of documents I wrote laying out steps, outlines of design elements, content assessments, schematics, data flows, wireframes, and Flash animations demonstrating how the finished tools would function I realize I miss that, deeply. I miss the passion and drive to make something great. I miss being permitted to dream big and solve problems that were untouchable, and best of all, go execute on those dreams. When I see members that made up that old team we reminisce, much like guys do about high school sports champion teams they were on. We had a great team with each of us doing what we loved and changing our part of the world, the digital world.

It was in that project that the seeds were planted for everything I love working on now. Looking at old diagrams I see hints of the Model of Attraction. I was using scenarios around people using and reusing information, which became the Personal InfoCloud. These elements were used to let others in on our dreams for that project and it was not until my time on the project was winding down (or there was no desire to move more of the whole product live and therefore no need for my skills) that I could pull out what worked well on project that made it special. Now others are getting to understand the Personal InfoCloud and other frameworks and models I have been sharing.

Adobe Buys Macromedia

Adobe buys Macromedia was not the news I wanted to wake up to this morning. My sole issue is competition, as with out these two competing there is little push to advance. This is not a huge surprise, as many rumors the last few years that Macromedia was on the block (most were expecting Microsoft to buy it and then spin out ColdFusion and the application tools to an outside buyer).

If this goes through, we have Dreamweaver/HomeSite as the dominant web development tool (it is making great strides towards standards compliant development and GoLive needs much more work), desktop publishing is Adobe only, market share of image editing and creation (Photoshop and Illustrator) go to Adobe, application development goes to Macromedia with ColdFusion, then we have the tough call with Flash and SVG. Flash is dominant, but SVG is open and Flash lite (for mobile) has really upset many developers as the player is up to the carrier and phone maker to deploy, not the content creator. This last step has really pushed many Flash developers away from Macromedia as they work to focus on mobile. Rumors that Adobe was working on a SVG mobile tool with open deployment had many developers for mobile really excited.

My hope would be for Macromedia customer service and pricing and Adobe Premium Suite with Dreamweaver and Flash thrown in for a well rounded package.