wabi-sabi
The most incidental detail
Bells
Most Japanese bells when hung still have on them one or more rough lines obviously arising in horizontal mold joints. These lines are not removed in fettling the bell, and they seem to be regarded not as defects but rather as a reminder of the reality of the founder’s interaction with his materials. One is reminded of the ceramics that are most treasured in Japan which usually have some unexpected tool marks or irregularity resulting from a kiln mishap.
Roughness
Roughness is the odd shape, the quick brush stroke, the irregular column size or spacing, the change in pattern at the corner – it is adjusting to conditions as they present themselves with meaning, but without ego or contrived deliberation.
Though it may look superficially flawed, especially with human perception accustomed to mass-produced regularity and perfection as a goal, an object with roughness is often more precise because it comes about from paying attention to what matters most, and letting go of what matters less.
Wabi-sabi
Sabi is an aesthetic term, rooted in a given concern. It is concerned with chronology, with time and its effects, with product.
Wabi is a more philosophical concept, a quality not attached merely to a given object. It is concerned with manner, with process, with direction.
Optical Glass House
A Building by Hiroshi NakamuraA façade of some 6,000 pure-glass blocks (50mm x 235mm x 50mm) was employed. The pure-glass blocks, with their large mass-per-unit area, effectively shut out sound and enable the creation of an open, clearly articulated garden that admits the city scenery. To realize such a façade, glass casting was employed to produce glass of extremely high transparency from borosilicate, the raw material for optical glass. The casting process was exceedingly difficult, for it required both slow cooling to remove residual stress from within the glass, and high dimensional accuracy. Even then, however, the glass retained micro-level surface asperities, but we actively welcomed this effect, for it would produce unexpected optical illusions in the interior space.
How the light gets in
A Quote by Leonard CohenThere is a crack in everything.
That's how the light gets in.Is perfection boring?
An Article by Ralph AmmerWe love to see the process, not just the result. The imperfections in your work can be beautiful if they show your struggle for perfection, not a lack of care.
Beyond Artboards
The Pursuit of Lossless Design-Development Handoffs.
Can't developers just see?
We designers love artboards. From rough UI sketches to high fidelity mockups, we see ourselves as visual artists expressing ideas on artboards that have a pre-defined width and height. To start a new project, we declare the size of the artboard in the first step.
What about responsive design? Not a problem! We diligently design on three artboards — one for mobile, one for tablet, and one for desktop — with content elegantly adapting, scaling, reflowing, reordering, and reprioritizing. We proudly hand off the artboards to developers while patting ourselves on the back: this is how responsive design should be done.
After weeks of arduous engineering, the product finally comes out. We find, to our great dismay, that some copy is hanging off the grid, the focal point of the hero image has been cropped out, the font sizes don’t even come close to the type ramp. What went wrong? Can’t the developers just see everything on all those artboards?
Nope.
We are the ones who paved the path
No matter how many screen sizes our artboards account for, some user’s browser will break loose from our prescription. With users resizing, rotating, and zooming the screen, new devices stretching, squashing, curving, and cutting (e.g. the speaker area in iPhone X) the screen, the sizes become infinite. Good luck making an artboard for each one of them.
Artboards are a lossy format. Using artboards in a handoff is a lossy process. When we pitch a finite number of plans against an infinite number of situations. We inevitably get in-betweens. Once there are in-betweens, there are unknowns. Once there are unknowns there is guesswork. Once there is guesswork, there are surprises. Engineers take the path of least resistance. We are ones who paved the path.
Until we get there
- As a designer, learn writing HTML, or better still, semantic HTML. If coding up the entire design is too hard, try coding up one component at a time, and not worrying about CSS. The HTML alone will prove invaluable for developers to understand the content structure. In addition, you are forced to optimize the information architecture as you work out the code from content.
- If coding by yourself is out of the question, pair up with the engineer who will receive the design. Work closely with him or her to prototype the design, validate responsive behaviors, and obtain feedback on the feasibility. Don’t call it an iteration until the design has seen played with in code.
- As a manager for large enterprise, co-locate your designers and developers, encourage interdisciplinary learning, understand that each minute spent on coding before the handoff translates to ten minutes saved from changing and fixing issues after the handoff.
- As a stakeholder in the handoff meeting, give the designer a thumbs-up when he or she demos live code running in browsers in place of mockups on artboards. That’s a design champion you are looking at.