From NeXTSTEP to Cupertino
Interface Builder first appeared in 1988 as part of the NeXTSTEP development environment, created at NeXT Computer — the company Steve Jobs founded after leaving Apple. It let developers drag AppKit controls onto a canvas and wire them directly to Objective-C objects through a mechanism called connections, establishing relationships between UI elements and code without writing layout boilerplate. No competing tool of the era handled this binding so directly; most form designers of the late 1980s generated code as a secondary artifact, whereas Interface Builder treated the serialised interface definition as the primary product.
That definition lived in the nib file — a binary archive that stored serialised object graphs representing an application's entire UI hierarchy, including all outlet and action connections. The format took its name from NeXT Interface Builder. When the application launched, the AppKit framework deserialised the nib at runtime, instantiating objects and restoring the connection topology. This runtime-loading approach separated interface structure from application logic in a way that proved durable enough to survive two platform migrations.
NeXT was acquired by Apple in December 1996, and NeXTSTEP's toolchain became the foundation of what Apple would ship as Mac OS X. Interface Builder carried over intact. When Xcode 1.0 shipped in October 2003 as the successor to Project Builder, Interface Builder accompanied it — not as a new tool integrated into the IDE, but as a companion application that ran alongside it. The two communicated through the nib file and through Xcode's project model; Interface Builder remained a separate process until Xcode 4 in 2011, which merged the canvas into a single-window environment.
The nib format itself evolved from binary to XML with the introduction of the XIB format in Xcode 3 (2007), making diffs readable and version control practical. Later, Swift UI (2019) offered a declarative alternative that required no canvas at all, but Storyboards — the XIB successor introduced in Xcode 4 — remained common in production codebases long after.
What kept the visual-design approach alive across a fifteen-year journey and two platform transitions was not the canvas itself but the object-graph model underneath it. Interface Builder survived because its serialisation concept — freeze the object graph, ship it, thaw it at launch — was a genuinely good idea, independent of the hardware it first ran on.