As a fresher straight out of college, I've never really grasp the differentiation between frontend and backend development. I've barely digested th...
For further actions, you may consider blocking this person and/or reporting abuse
In my experience, even the front end profits from Backend-First doctrine. That allows us to pre-define the data structures we need processed and displayed. That way we can keep the front end as simple and dumb as possible. Also, it encourages a "form follows function" design principle.
Of course, it also always depends on what you're working on. I don't think there's a definitive answer.
I used to be backend first, frontend later. I changed my mind. The UI will end up influencing your app (backend included) because the UI is the app for most of its users.
In reality I think you'll do both at the same time.
Design the first feature, implement it fully, iterate. Both frontend and backend will evolve with the app.
My conviction about interface first comes from the book Getting Real by 37Signals/Basecamp and with experience. Most of the times app built with a non iterative approach will end up doing the wrong thing.
Use an "agile" approach if you can, decide what's the smallest thing of value you can deliver and implement it from top to bottom. Repeat.
LOL