I know it shouldn't, but this is pissing me off
Why Apple?
Finder:
iTunes:
Safari:
This seems like such a basic thing. All they do is clear a text entry field. Is there some reason why Apple would make these slightly different shades? As far as I know they all function the same... but, ugh
I mean, wouldn't it be like having radio buttons look slightly different?
Finder:
iTunes:
Safari:
This seems like such a basic thing. All they do is clear a text entry field. Is there some reason why Apple would make these slightly different shades? As far as I know they all function the same... but, ugh
I mean, wouldn't it be like having radio buttons look slightly different?
Comments
I can live with it as I believe the pace to make OS X great is very furious. At some point, a lot of the little details will all come together.
Also, its more important to fix bugs than things that most people never notice.(Not to be a jerk)
I know. I would much rather have Apple fix bugs than this, but it just seems like such a little thing. One of those things you should get right on the first try (well maybe not Safari, being beta and all).
Ah well
Originally posted by Kecksy
Ever since Jobs returned to Apple, Apple's software has been less consistent interface why. I think this has something to do with Steve dissolving a group within Apple which made sure all programs strictly adhered to HIG. Now programers have a lot more freedom to experiment, which I think is good, but you can also see some of the negative consequences.
I think the idea that the HIG group has been dissolved at Apple is a myth... but it's definitely true that UI teams on various groups have been given a lot more room for experimentation over the past few years. This approach seems to have its pros (lots of interesting things going on) and cons (dozens of little niggling and not-so-niggling differences and inconsistencies).
Does anyone have any inside information exactly how an application is developed at Apple? I assume there's a central team in charge of UE of OS X; can this team veto a UI decision made by another group? How does it all work?
All very Apple Internal and hush-hush, I know, but even the slightest glimmer of how it works would be most interesting.
Now every programmer (or DB admin) knows (or should) that code duplication is bad, nay, evil! This is enshrined in the rule Once and Once Only and the DRY principle (Don't Repeat Yourself). Breaking these rules leads to UI inconsistency, bugs and difficult-to-maintain spaghetti code.
So you might think this is an even worse problem than you think, but the truth is you need to experiment to innovate and this means duplication of effort and the occasional dead end.
Apple developers have the additional headache of bringing code designed originally for OS 9 (then OS 9 and X at the same time) up to the point were it can interoperate with pure OS X code. Sometimes, for various reasons, this just can't happen.
Apple is moving towards some beautiful coding, it's use of Obj-C, XML, open standards and open-source software is a *very* good thing. Once it fully breaks it ties with the legacy of OS 9 things will be much better.
And I really hate the fact that there is 6 billion different brushed-metal implementations now.
There's the super fake brushed-metal that started it all, QuickTime, then there's the semi-fake brushed-metal in iTunes. The real brushed-metal in AddressBook, iCal and Safari. Then there's the 'let's-keep-10.2-compatibility-brushed-metal' in iMovie and iPhoto...
Screw it, I've kind lost count and comprehension of the whole thing. I'm not even sure what I'm talking about anymore.
The latest look in brushed-metal is the embedded/receded glass button look shown in iMovie 3, iDVD 3, Safari 3.
But apps such as Address Book and iPhoto still have the protruding glass button look. As for iCal and iPhoto and other older brushed-metal apps, they still have the metallic buttons.
Is there going to be a more uniform GUI from Apple eventually? These are minor details but...ya know...it bothers me.