4 ms·
For long time I've been arguing that code / functionality should come before visual design. Never found anyone to agree with me.
by njharman 16y ago
For long time I've been arguing that code / functionality should come before visual design.
Never found anyone to agree with me.
- thetylerhayes 16y agoSeems you just hadn't found the right people yet :)
- synotic 16y agoDepends whether you're innovating in the frontend or the backend. The user interface for the iPhone was completely designed before any of the frontend was coded. There's a great comment by tlrobinson somewhere about how the iPhone was designed and developed but I can't seem to find it. Also consider New Twitter. I don't understand how you'd start coding the HTML and the JavaScript without understanding the visual design for how the dynamic, two-pane interface was expected to work. But if you're building a search engine, then you can probably put off the design until later. The analog is that you really wouldn't (or shouldn't) start writing code until you had an idea (a design or an architecture) of what you were trying to write. Same way you wouldn't start to code an interaction (HTML+JavaScript+CSS) if you had no idea what that interaction looked like.
- dools 16y agoThere's a fair bit of noise for content preceding design in web mockups, same principle.
- rudasn 16y ago- "Hey can you build me a house?" - "Sure, how big do you want it? How many rooms?" - "I'll tell you what. Build the house and we see how it goes".
- ryanelkins 16y agoThere's a difference between visual design and architectural design.
- njharman 16y ago1st off I belive this conversation was about building software not houses. 2nd how big, how many rooms, also is it made of bricks, does it have a fireplace, etc are all functional and not visual design.