Comments on Andrzej on Software: Frontend first

Anton, Sounds great! I think I sometimes worried...

2013-02-18T10:07:55.972+01:00

Anton,

Sounds great!

I think I sometimes worried, if this approach isn't too waterfallish. What's your opinion on that?

I totally agree. We follow a similar approach wit...

2013-02-18T01:28:13.459+01:00

I totally agree.

We follow a similar approach with most of the applications we build for our clients, even when they aren't single-page apps.

After wireframing the key screens, we build a clickable prototype using Twitter Bootstrap that allows all stakeholders to play around and use the application at a level that's very close to what the user will see in the actual app.

This eliminates a lot of guess work out of the development process, and allows us to find issues with the user interface much sooner, before writing a single line of back-end code or opening Photoshop.

Yes, that's exactly this. From the perspectiv...

2013-02-15T15:55:43.213+01:00

Yes, that's exactly this.

From the perspective of an SPA, the backend is actually mostly some kind of a smart persistence (depending on the application).

We were delaying the backend work for a while and it seems that maybe we don't need to do a proper backend, but can rely on firebase, or a similar tool. Which is very convenient :)

This reminds me of Uncle Bob talking about a Hexag...

2013-02-15T15:51:46.443+01:00

This reminds me of Uncle Bob talking about a Hexagonal/Onion/Ports'n'Adaptors application, in which they recurringly postponed creating a persistence layer. They originally thought it would need a database, but to begin with just mocked out persistence. Then someone created a test implementation of the persistence API, using flat files, just for testing. Then they started demoing the app, and then shipping the app, and eventually realised they didn't need a database at all.

Is what you're talking about similar to this at all?