Since the release of the Google Nexus One, I was essentially of a mind that the Nexus Experience is pretty much exactly what I wanted from my phone. When the Nexus S arrived, I happily abandoned my Micro SD card in exchange for the curvy shininess of Samsung collaboration with Google. Here I was, completely happy to enjoy the Nexus experience and allow the other UI’s to fade into obscurity when LTE arrived.Now, the HTC Thunderbolt was cool, but after using a Nexus S for a while the Thunderbolt was not unlike a brick in my hand and pocket. Still, the speed and performance of the LTE network beckoned me in my sleep until the Samsung Droid Charge arrived. Here was a phone that was not entirely dissimilar from the Nexus S when you held it in your hand, yet it had an even better screen and the LTE radio wasn’t nearly as big a battery goblin as it was on the Thunderbolt. I thought I had found a nice Verizon phone to settle into, until about a day and a half into using it.I couldn’t quite put my finger on what exactly was wrong, but I was not enjoying the phone. It felt great in the hand and pocket, got pretty good battery life, and I giggled like a school girl every time a page loaded in what seemed like record time. I realized that what was making me unhappy was the TouchWiz UI that was deployed on this phone by Samsung. After trying to put to words exactly what I was having trouble with, I decided to put together a video explaining my dilemma.Now, all in all these seem like pretty trivial things for Samsung to fix, and hopefully in the next revision of TouchWiz, they will. Until then, however, I am forced to use third party launchers and simply suck it up when it comes to the rest.