HTML5 Zone is brought to you in partnership with:

Andrzej is a DZone MVB and is not an employee of DZone and has posted 24 posts at DZone. View Full User Profile

Frontend First

02.15.2013
| 2583 views |
  • submit to reddit

 
Some time ago, I blogged about the different phases of mental transition when working with JavaScript frontends. Here's the shortened version:


1. No-JavaScript phase

2. JQuery explosion

3. Page and Widget objects

4. Single Page Application

Once you're in phase 4 and you create apps this way, you realize that you don't need the backend in order to create the Single Page App. Even more, you shouldn't start with a backend.

Frontend first

This is the additional phase. Frontend first. In most of the typical situations, it's much better to start with a Single Page Application and use LocalStorage or some kind of a InMemoryServerSideAdapter for the first phases of the development.
Only after you know how the frontend works and what kind of server interaction it requires, it actually makes sense to start working on the backend.

We've tried this approach in several Single Page Apps and it worked great for us. It now seems like the most natural way of working.

Published at DZone with permission of Andrzej Krzywda, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

Comments

Ian Mayo replied on Fri, 2013/02/15 - 12:05pm

Agreed, it totally removes the reliance on having a server at all in the early stages - plus you get to mature the frontend-backend API without having to maintain  codebases in two separate languages, potentially across two separate developers/teams.


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.