✳flâneur — a map of the web's best reading

Interface First | Getting Real

basecamp.com · 577 words · saved by 1 readers

Heads up! This page uses features your browser doesn’t support. Try a modern browser like Firefox or Chrome for the best experience. CHAPTER 46: Next: Epicenter Design Too many apps start with a program-first mentality. That’s a bad idea. Programming is the heaviest component of building an app, meaning it’s the most expensive and hardest to change. Instead, start by designing first. Design is relatively light. A paper sketch is cheap and easy to change. html designs are still relatively simple to modify (or throw out). That’s not true of programming. Designing first keeps you flexible. Programming first fences you in and sets you up for additional costs. Another reason to design first is that the interface is your product. What people see is what you’re selling. If you just slap an interface on at the end, the gaps will show. We start with the interface so we can see how the app looks and feels from the beginning. It’s constantly being revised throughout the process. Does it make sens

Interface First | Getting Real sidebar#closeWithKey"> Heads up! This page uses features your browser doesn’t support. Try a modern browser like Firefox or Chrome for the best experience. sidebar#open" aria-label="Getting Real Table Of Contents"> Getting Real Chapter 46: Interface First Next: Epicenter Design sidebar#close mouseup->tweet#update input->tweet#update keydown->tweet#update scroll@window->tweet#update" data-bookmark-id="/gettingreal"> Design the interface before you start programming Too many apps start with a program-first mentality. That’s a bad idea. Programming is the heaviest c

Explore this link on the map →

related reading