[HTC EVO 3D] agrabren:
Off-topic:

What's next for me after the HTC EVO 3D?

I tried my best to work on the HTC One X+, but unfortunately, I've been denied. That was the last HTC phone of interest to me, so after the HTC EVO 3D, I'll likely develop for a Samsung phone. In the meantime, I'm getting the LG Nexus 4, because I do want to upgrade finally, and with my time being as restricted as it is, trying to support both the EVO 3D and another phone at the same time would be too much. In the last 3 weeks, I haven't really had much time to do anything on any phones, but I'm expecting work to slow down a little in December. It's sad for me to see HTC doing as poorly in the market as they are, as I have enjoyed all my HTC devices. I got started with the HTC EVO 4G more than 2 years ago, and it was my first experience with Android. I jumped on the EVO 3D the day it came out, and even had Sprint ship it to me at my hotel while I was on vacation, I was so eager to get my hands on it. And the HTC One X+ really does look like a nice phone, but I can't lose my day job over my hobby. Providing for my family and myself comes first. My wife has the Galaxy Nexus, and I'm not entirely impressed with it. The Galaxy S3 is sexy, but it just doesn't "grab" me and get me to switch. More and more, Nexus phones are becoming the right choice, both for price and capabilities. Think, for a bit, about what the development community could do with these devices if we weren't busy just trying to make them work with AOSP? Imagine how much better we could make AOSP and these devices? Stability, security, features... Google does an amazing job, but carriers and OEMs are determined to hamper it. This is why Apple is able to do so well against them, in my opinion. Google has to focus on all the different OEMs and businesses, while Apple focuses on iOS and it's next generation device.

What is Google missing?

Backup and Restore - The iPhone was upgradable from the first version. I still can't move my save games from one Android device to another

Google Voice Integration - A Google Device running a Google OS using Google Voice is still a mess. Explain this to me. Why doesn't this "just work"? I should be able to use any SMS program, MMS app, etc... And it should *just work*. When I dial out, it should *just work*. I understand Google Voice having issues on an iOS device, but on a Google Device?

E-mail Integration - Apple got this one right, why do I need multiple email apps? Why isn't e-mail handled through providers and observers? One app to rule them all? Take a lesson from Microsoft, control the platform and the APIs, and you will own the devices.

Hardware/API Compatibility Lab - Phones should have to be qualified with hardware to pass. Headsets, serial port protocol, NFC, camera... All should be tested running Google software which talks to the framework. And if that software doesn't pass, the phone isn't Android. Stop letting the OEMs mess up things that prevent developers from making functional software. You made the APIs, enforce them. That way, developers spend more time making better apps, and less time debugging crappy OEM modifications that break things. And yes, charge them for this. While AOSP is free, officially declaring your device to be Android should not be. It should mean a certain expected level of functionality and usability.

User Interface - You're on the right path. You finally made the camera look decent. Now, go find yourself a small UX design company, acquire them, and *use* them. Google's ability to make an amazing OS has only been hampered by its inability to make amazing user interfaces. If every single OEM has replaced the same piece of your OS before shipping it, it means yours isn't very good. (Ahem - Pre-MR1 Camera)

That's all I can think of to list right now, but I wanted to get some of it off my chest to the handful of people who still read my posts and actually own an HTC EVO 3D (yes, all 15 of you) ;)