Having literally bruised my fingers trying to appease a visual designer who wanted browser rendering to look exactly like Photoshop (for instance, the CSS-drawn gradients didn't meet her approval, so we had to lard the interface with background graphics), I'm now in the "Put designers in straitjackets until they learn the fundamentals of modern Web application design" camp.
It's the year 2013, and your competition is using frameworks like Bootstrap or Foundation to release something while your dev team is fussing over bespoke line-heights specified in points. Maybe your app looks better, but how many users are waiting for that placed-just-so button image to download?
We take design very seriously, and thats because better designs have been quantifiably proven to have a meaningful impact on our bottom line. That means sometimes we try and polish something for the first release, but we always set a limit to that - if it's not in production, it's not shipped, and we will forget about it amongst the 23524 other things going on in a given week. Therefore, we usually set at least some internal goal of "good enough" and then ship. It just so happens one of our founders really likes digging into design.
Also note, this is an iPhone app, not a web application. Very different rules apply here, so you can't just slap Bootstrap on your UI and hope for the best :)
It's the year 2013, and your competition is using frameworks like Bootstrap or Foundation to release something while your dev team is fussing over bespoke line-heights specified in points. Maybe your app looks better, but how many users are waiting for that placed-just-so button image to download?