Steve Souders's talk was about how design and performance go hand-in-hand, like yin and yang.
- It’s not one gains and the other loses, design and performance should be complementary
- “I used to be a reckless designer” said by one of the designer he knows, but it turns out, the pretty pages she designed took 2 minutes to load.
- Sometime it’s hard to correlate business goal with technical performance. Solution is to come up with metrics earlier
- On mobile in particular, the page load needs to be faster to be considered as good design. Google came out new ranking on mobile search where the mobile-friendlyness will affect the ranking
- Possible solution: don’t separate design and developers, and maybe have them sit together from the very beginning
- Define guiding principles: figure out what users are after, what’s important to this product, what’s the most important element on the page. One example of a news mobile site “Speed is more important than design embellishment"
- Prototype earlier and measure performance in prototype
- show the data loading time while implementing
- window.onload is NOT the best metric for measuring website speed (page load time isn’t providing the proximation of user experience). Page load time could be too optimistic/critical
- We need to get metrics to have closer proximation of user experience
- User experience and business goal could be inline with each other
- what’s the most critical design element on the page and focus on those performance
- Designing for UX performance