Bill Humphries


Bill writes software, worries about identity and privacy, and is still trying to balance simplicity vs. shipping a product.

Proposals for this user

* Rethinking the Single Page Web Application

We were promised a glorious future with RESTful APIs, clients with lighting fast JavaScript engines, and an end to sending UI from the server. Now your project is late, the technical debt is piling up, and you're thinking that hey, Rails wasn't awful. Let's talk about when it's a good idea to build a single page, client side app, and when it's not. I'll be drawing from my experience building a single-app to manage an enterprise software as a service product. Before you jumped into Backbone, Ember, or Angular, you needed to think through the APIs you have, and still had to build. You need to look at the interactions in your UI. You need to figure out where and how your users will access the application.
Cooking 2014-04-11 08:57:43 +0000
Bill Humphries