The number of obvious bugs [1] included lends a lot of weight to the impression of it being more about sniping than criticism.

[1] z-index, text overlap, mixed states, etc. These are not questionable design choices. They're bugs. And lumping them in only detracts from the site and the many legit design gripes (problems of focus, alignment, contrast, usability, etc.)

Are bugs in the UI not themselves part of the UI? If their goal is point out "sloppiness" in the UI, why should obvious or slightly less-obvious bugs be excluded?

Because it's very likely that anything that would be seen as a "bug" will be fixed in updates; whereas things that are the result of intentional (bad) design, like lack of information hierarchy, probably won't be fixed, because they won't be seen as incorrect. (Which is, nominally, what this tumblr would be for pointing out.)

I don't think I agree with your last sentence, which seems to be the issue. The site isn't called "The Terrible Design Decisions of iOS7", it called "Sloppy UI" which I think covers both bugs and UI. Further, sometimes it can be hard to differentiate between a bug and a design decision, so I think it's hard to ask them to just stick to one or the other. May as well point out everything you see that isn't up to standards, be those design or implementation.

To me, the Tumblr is pointing out an overall lack of attention to detail. Some of these obvious bugs should have never made it past QA/testing, but somehow they did - and that's sloppy UI, regardless of whether it was an intentional "do that" directive.

I understand what you're saying, and perhaps the name of the Tumblr should change to "Issues with iOS7", but that sounds pretty boring to me. Instead, we can all agree that sloppy/bad decision-making, sloppy QA practices, etcetera can be learned from, and that there is value in identifying (and avoiding) these mistakes both in the works of others and in our own work.

> "Some of these obvious bugs should have never made it past QA/testing, but somehow they did"

Perhaps they made it past QA/testing because what is an obvious bug in a screenshot isn't necessarily obvious to generate or replicate.

I haven't seen any of those bugs in the time I've spent in iOS7.

I'm with 'roc' on this one. Including a bunch of obvious bugs tells me that you either a) can't distinguish between design and implementation or b) are more interested in shitting on other people's work than saying anything useful.

This is fail culture masquerading as design critique, and it isn't even doing that well.

> This certainly isn't "hipster" culture - this is design critique.

Critique that doesn't actually tell what's wrong ... isn't.

Let's talk about the z-index issue with the AppStore icon. How is this reproduced? I have never seen that. How do I know it's not shopped?

All it says is "z-index". Not useful. Not really a critique to me, it's just too terse.

Critique doesn't always explain reproduction. That's more like a bug report I think. Actually saying what's wrong is describing that the UI has a clear problem with z-index. I would understand if someone was trolling the Apple bug submission process, but they aren't; they are pointing out flaws with clear visual examples.

I disagree that critique must inherently describe the problem. Sometimes, the problem is fairly self descriptive, especially with what this blog provides, which is obvious issues that most of the blog's audience will immediately understand as "sloppy" - that is, I shouldn't have to explain why the z-index issue is sloppy to justify my criticism, but if you want a bug report, I can explain how I got there.