You edited your reply to make a stupid comparison. Fine, one more.
Definitely effort went into creating the GUI. By the guy hired to do that. Not the guys in charge of deciding core features.
"The guy." Can you tell me how big the eShop develoment staff was? Who was on it? What their defined roles were? I've been looking, and I can't locate that information. Maybe I suspect that if they had been given a simpler GUI design to develop and program, that their time could've added to other aspects of the 3DS, perhaps ultimately leading to some improvement down the line over what we received. It's my suspicion they wouldn't have said "Whoops, done early!" and jammed their thumbs up their butts while the rest of the staff toiled away.
Guy 1: "That's a nice looking interface you made."
Guy 2: "Thanks, I put a lot of effort into it."
Guy 1: "It's a shame we have to take out all of the color and make it grayscale."
Guy 2: "Wtf? Why?"
Guy 1: "3DS doesn't have demos as a standard."
Guy 2: "And what does that have to do with what I was paid to do?"
Guy 1: "I dont' know, but maybe if spent less time doing your job and more time adding features to the eShop which isn't your job, nor do you have the authority to do, we wouldn't have this problem."
*head desk* This is just STUPID. This is not what I'm saying, and if this is what you see it as, you've been misreading.
I'm saying the staff MIGHT be more multi-function than you seem to assume. The person who spent all that time making the box that fills up with color as charms swing from the lines and drop in, including the little 3DS shop mascot running around and sometimes getting caught on the line, and being able to tilt that camera limitedly around that box, that's actual programming work that was not effectively spent. It polished a turd, sure, but it's one example of many where they were focused so much on the little details and gimmicky touches, almost to an excess. And presuming they had a limited time and budget for developing these aspects, including the eShop which was already
late for months, this was not the best use of their focus.
My point was that something had to go there, and some of the little touches are nice, but they got carried away polishing minor details and things they'd have to go back and replace or modify later. I feel like as a whole, some of those people who did that development work would've better spent their time working on more basic features. I'm not just saying them screwing around with pegs on the back of icons was solely to blame, or the eShop's overproduced download screen, or any one of a dozen other aspects. I'm saying as a whole, for a portable that was rushed, so hard to market, staff time seemed mismanaged.
I am not saying the guy who modeled pegs on the back of icons is the reason we didn't have messaging. But who knows what other tasks he could've been doing while he was trying to figure out what size to make the pegs, what shape, what depth, which icons have them, and so forth. The other work he could've been doing instead may have made someone else's job easier, freeing up their time to work on something more important. The polishing comes when the project is done, and I'd hardly call what the 3DS launched with "finished."
That's as clearly as I can explain it, and if you don't understand my point by now, I don't care. If you don't agree with my point, I don't care. If you just want to quote some tiny segment and make some lame "you're an idiot/I'm superior to you" statement, you're sad and I still don't care. We're way off-topic in one of my favorite topics, and the only reason I've been replying this long is that some people are treating me like an idiot because they think I don't grasp the concept of job roles, and others are just being plain assholes about it. And if you still think that? Yeah, you can guess the rest.
Now please, someone post another cloudbush or something. I want to move on just as much as the rest of you.