Case Study Audi：奥迪的案例研究.ppt

Case Study: Audi 1. Schematics (wireframes) 2. ?Jumping Boxes“ 3. Right vs. Left Navigation Schematics Documents separate independent 1. Schematics (wireframes) 2. ?Jumping Boxes“ 3. Right vs. Left Navigation 1. Schematics (wireframes) 2. ?Jumping Boxes“ 3. Right vs. Left Navigation Thank Youjim@razorfish.de There are many ways to achieve flexible page layouts, but we went for what can be called an automated layout. Essentially we build ?smart“ pages that are able to detect the size of the browser window and serve up the right layout size automatically. We essentially had three sizes – small, medium and large. This solution fulfilled CI constraints. The page designs have a grid that aligns all page elements horizontally and vertically. With an automated layout solution we were better able to control the alignment of page elements. The solution is highly technical and speaks to the Audi slogan ?Vorsprung durch Technik“ or Advancement Through Technology. So, we were branding with layout and with this technical solution. Three sizes: 640x480 800x600 1024x768 Show: /de/de/erlebniswelt/unterhaltung/audi_bildschirmschoner/audi_bildschirmschoner.jsp and other pages... 1. This proved to be more challenging to implement than initially thought. 2. It is unknown if there are any usability implications. We don‘t believe so, but have no proof. 3. The automated layout solution is not needed for all pages and page types. With an increase of alternative browsing devises on the horizon, the continuum of viewable browsing sizes will only expand. Never before has the demand for flexibility been greater. This was a valiant attempt to address this issue and we learned a great deal from it. However, it was very complex to implement and I would caution anyone considering such a technique. We wanted to set Audi apart from its competitors, who general have conservative page layouts with the navigation on the left of top. The idea was to place the navigation the