Sure, there are a whole slew of "applications" that will suffice with a basic form-driven UI accessing a rails or servlet back-end. And indeed there are applications like twitter where the entire complexity is in the complexity of the back-end. But then there are all the apps that simply aren't web-apps yet, because nobody has figured out how to do complex, rich, and above all Interactive, applications using fucking javascript. We're getting there, but people are writing the code to do it as I type (jquery, backbone, etc).
So this is why UI is hard: its art and its engineering. And nobody thinks about the engineering part. And when they do, they have to find an engineer who can talk to the designer without scaring him/her (very often "her").
> Backend is hard in the way that building a skyscraper is hard ... Managing complexity is really the problem there.
UI is hard exactly for this same reason: managing complexity.
There are a lot of great great tools and abstractions for back-end work, but UI has too long suffered with same old OO-oriented approaches that GUI frameworks dictate. They are quite bad for managing the complexity.
Backend is hard in the way that building a skyscraper is hard. You need a solid design and framework, but you also have to make sure every wire runs in the right place. Managing complexity is really the problem there.
Which is harder? I don't think they're very comparable, in the way that I don't know if creating beautiful art or building a skyscraper is harder.