In a mass of large bubbles The froth, therefore, though lacking long-range symmetry, nevertheless has very definite rules as to its composition. It is pleasing in appearance because the eye senses this interplay between regularity and irregularity. Structure, Substructure, and Superstructure symmetry
We wonder which is real, he of the picture or he who talks? In the tea room the fear of repetition is a constant presence. The various objects for the decoration of a room should be so selected that no color or design shall be repeated. If you have a living flower, a painting of flowers is not allowable. If you are using a round kettle, the water pitcher should be angular. A cup with a black glaze should not be associated with a tea-caddy of black lacquer. In placing a vase or an incense burner on the tokonoma, care should be taken not to put it in the exact center, lest it divide the space into equal halves. The pillar of the tokonoma should be of a different kind of wood from the other pillars, in order to break any suggestion of monotony in the room. Here again the Japanese method of interior decoration differs from that of the Occident, where we see objects arrayed symmetrically on mantelpieces and elsewhere. In Western houses we are often confronted with what appears to us useless reiteration. We find it trying to talk to a man while his full-length portrait stares at us from behind his back. We wonder which is real, he of the picture or he who talks, and feel a curious conviction that one of them must be fraud. Okakura Kakuzō, The Book of Tea repetitionsymmetry
Beyond Artboards An Essay by Chuánqí Sun medium.com The Pursuit of Lossless Design-Development Handoffs. Can't developers just see?We are the ones who paved the pathUntil we get there processinterfacesdesign
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. Start drawing, then put the box around it
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. gridless.designChanging Our Development Mindset
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. html