Andre Malan
Aug 21, 2013 · 1 min read

Last month I gave a lightning talk at the Ember.js NYC meetup. The talk was about designing your API based on what it was going to be used for by the users instead of designing it based on what is in the database. I think that this tactic can be really effective as it reduces the complexity of the front end code, which is where your users are and where you really want everything to revolve around their experience, not the intricacies of your data layer. With more and more complexity living in the front end through frameworks like Ember.js our design decisions need to be giving more weight to the front end than they used to.

Video and slides below:

Video:

Slides:

http://slid.es/andremalan/your-front-end-is-not-your-back-end/

http://slid.es/andremalan/your-front-end-is-not-your-back-end/embed

andre-malan

Hacking, Learning and Technology

Andre Malan

Written by

Hacking, learning and technology. Spend a lot of time building @simplereach

andre-malan

Hacking, Learning and Technology

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade