graphics
Truchet Tiles
The basic course
The Basic Course was a general introduction to composition, color, materials, and three-dimensional form that familiarized students with techniques, concepts, and formal relationships considered fundamental to all visual expression, whether it be sculpture, metal work, painting, or lettering. The Basic Course developed an abstract and abstracting visual language that would provide a theoretical and practical basis for any artistic endeavor.
A universal correspondence
In 1923 Kandinsky proposed a universal correspondence between the three elementary shapes and the three primary colors: the dynamic triangle is inherently yellow, the static square is intrinsically red, and the serene circle is naturally blue.
The series ▲■● represents Kandinsky’s attempt to prove a universal correlation between color and geometry; it has become one of the most famous icons of the Bauhaus. Kandinsky conceived of these colors and shapes as a series of oppositions: yellow and blue represent the extremes of hot/cold, light/dark, and active/passive, while red is the intermediary between them. The triangle, square, and circle are graphic equivalents of the same polarities.
BeOS Icons
The Art of Looking Sideways
A Book by Alan FletcherCover art for Alan Fletcher's wonderfully expansive commonplace book.
Interaction of Color
A Book by Josef AlbersWhat shape is the internet?
A Gallery by Noah VeltmanAccording to patent drawings, it's a cloud, or a bean, or a web, or an explosion, or a highway, or maybe a weird lump.
narrowdesign.com
A Website by Nick JonesDesign
Prototype
CodeAPL386 Unicode
A Font by Adám BrudzewskyAPL font based on Adrian Smith's APL385 font with a fun, whimsical look, inspired by Comic Sans Serif.
APL (named after the book A Programming Language) is a programming language developed in the 1960s by Kenneth E. Iverson. Its central datatype is the multidimensional array. It uses a large range of special graphic symbols to represent most functions and operators, leading to very concise code. It has been an important influence on the development of concept modeling, spreadsheets, functional programming, and computer math packages. It has also inspired several other programming languages.
butdoesitfloat
A BlogThe Tiling Patterns of Sebastien Truchet and the Topology of Structural Hierarchy
A Research Paper by Cyril Stanley SmithA pattern of tiles illustrated by Douat in 1722.
A translation is given of Truchet's 1704 paper showing that an infinity of patterns can be generated by the assembly of a single half—colored tile in various orientations.
Reading Design
A WebsiteReading Design is an online archive of critical writing about design. The idea is to embrace the whole of design, from architecture and urbanism to product, fashion, graphics and beyond. The texts featured here date from the nineteenth century right up to the present moment but each one contains something which remains relevant, surprising or interesting to us today.
The Fidelity Curve
How do we choose which level of fidelity is appropriate for a project?
I think about it like this: The purpose of making sketches and mockups before coding is to gain confidence in what we plan to do. I’m trying to remove risk from the decision to build something by somehow “previewing” it in a cheaper form. There’s a trade-off here. The higher the fidelity of the mockup, the more confidence it gives me. But the longer it takes to create that mockup, the more time I’ve wasted on an intermediate step before building the real thing.
I like to look at that trade-off economically. Each method reduces risk by letting me preview the outcome at lower fidelity, at the cost of time spent on it. The cost/benefit of each type of mockup is going to vary depending on the fidelity of the simulation and the work involved in building the real thing.
Four levels of fidelity
Suppose we have four levels of fidelity…
- Rough sketch (on paper or an iPad)
- Static mock-up (eg. Photoshop or Sketch)
- Interactive mock-up (eg. Framer, InVision)
- Working code prototype (HTML/CSS, iOS views)
Depending on the feature you’re working on, these levels of fidelity take different amounts of time to create. If you plot them in terms of time to build versus confidence gained, you could imagine something like a per-feature fidelity curve.
Time to build versus confidence gained
Take a simple CRUD web UI, where you’re just navigating between screens. It doesn’t take much more time to build the real version than it does to mock it when the design is simple. If you were to build out an interactive mock first, you would end up spending twice as much time in total without gaining much out of it.
Contrast that with a complicated Javascript interaction. Or a native iOS feature that requires programmer time to build out. If it takes substantially more time to build the real code version, then it may be smart to do an interactive mockup first.