[Shield General] agrabren:
I'm sure for many people, the last 24 hours has sucked in regards to SHIELD. I know for me it has. And even more frustrating is the lack of communication and transparency that should be expected from a large corporation who cares about its customers. Obviously, I feel the anger and frustration that is being vented both in the geforce forums and, to a lesser extent, over here on XDA. And I have no other outlet than XDA. First, and foremost, realize that the decision to delay the product, the reasons behind it, and the execution of the delay are unrelated. I, along with many, feel they really messed up on the execution of the announcement. Am I disappointed? Of course I am. There are hundreds of engineers around the world who have been putting in long hours for months (some of us, even over a year) to make this product. This is a passion for us. I, personally, involved myself into community aspects of the device. For example, I was one of the voices asking for the device to be unlockable. And NVIDIA didn't put up a fight for it, they agreed. Deep down, the heart of the company wants the best for everyone.

I'd like to answer a few questions that I ask myself, as a developer and a member of the XDA community:

1. Do you plan to run CM on the device, and why?

This is always a very important question for me while at work. This question is important because it represents all the shortcomings I feel exist in the product. But I'm not the average user, I'm an XDA member. That means that additional settings do not scare me. Ease of use can be reduced in the name of more advanced functionality. And Google Certification is a requirement that CM doesn't have. But I think deeply about every feature I want from a custom ROM, and what the product should do. Ultimately, yes, I plan to install CM. And it is because of the advanced tweaks available in CM that don't belong in a standard user device.

2. Do you think the device is worth it?

Do I think the device is worth the long hours, the stress, the loss of my personal development time (which is why I had to mostly drop the EVO 3D), and the time away from my kids? Obviously, that question also has the benefits I've gotten, like attending CES and Google I/O. But ultimately, I still work on it, and I still want it to be the best it can be. So the answer has to be yes.

3. This whole debacle is ridiculous, shouldn't I just cancel my pre-order? NVIDIA obviously doesn't know how to launch a product...

This comes back to the earlier message. Engineers build a product, marketing sells a product, and the company as a whole is represented by the product. The mistakes made in the messaging and delays don't represent the engineering and product, they represent a company which still has some lessons in releasing a customer product. It's easy to get emotionally wrapped up in it, because the disappointment so close to the release. And I'm not immune. If anything, I've also got the disappointment in the world finally getting to see what we've done and use it. That's why I'm writing this thread, because it helps me express my feelings in a constructive way.

4. What would you change?

I'm slowly becoming disenchanted with Google's AOSP design. While I love the product being so close to AOSP, it reminds me how ugly AOSP really is. I don't want something like Sense or Touchwiz. What I want is AOSP, but sharper looking and using the graphical power of modern devices. Does everything really need a flat gray look? TWRP looks ugly to me, compared to the install phase of 4EXT. Halo is outdated and sad-looking. I want glass effects, I want sharp text and lines. I want to feel like the display is sharp and crisp while in the launcher and settings. I want my settings to have tabs (like MIUI used to have, maybe still does?) for the different areas. But again, the goal is to line up with AOSP, which I can respect.

Ok, so I'm out of questions and I'm feeling a bit better. If you have questions for me, be my guest... I'll do my best to answer, and when I can't, I'll do my best to get an official answer...