Client Side Architecture Part Three: Your Turn!

In our two previous posts, we talked about the benefits of client side web architecture. To talk the talk is one thing. To walk the walk is something else entirely. Moving to client side architecture implies mastering a new set of skills. For one thing, you'll have to learn JavaScript. Taking this step can be pretty daunting, even to the most skilled developer. Here are some tips to help you out.

Client Side Architecture Part Two: A Practical Example

In a previous post we talked about client side and server side web architecture. We showed the difference between the two approaches and concluded that client side web architecture offers a lot of benefits. Now it's time to get our hands dirty and put theory into practice. In this post we’ll compare both approaches using a real application.

Client side architecture part one: The web is Lego.

Let's admit it: when it comes to interacting with the web, we’re all a little spoiled. We’re used to websites like Facebook, Pinterest and Evernote. We all own a smartphone with fancy-looking apps. Yet when we create web applications, we often forget our users are no different. They expect a rich interaction and a fast, dynamic user interface. Providing this kind of interaction can be crucial to your business. This is where you win or lose the hearts of your customers.