Should Samsung go back to the software drawing board?Evan Selleck - Contributing Editor
When it comes to this Apple versus Samsung situation, there is a lot to write about. A lot of different angles. A lot of different ways to point fingers. Both companies are showing that off right now. Debating on who is right, and who is wrong. We could sit here and talk about both of those points all day long, as I know that all of you have your own opinions on the proceedings. But instead, I want to talk about the future. What comes next. Or, what should come next, anyway.
Yesterday, just in case you missed it, it was revealed through an internal Samsung document, that the company did indeed develop TouchWiz with Apple’s iOS in mind. At this point, there’s just no way around that. It is what it is, and I’m not surprised that Samsung would want to develop their own future software based around the already successful iPhone’s software. If you can’t beat them, join them, right?
That’s a bit much, but you get the idea.
The problem here isn’t that Samsung wanted to use some iOS-based inspiration with the development of TouchWiz. The problem should be that Samsung chose that route, instead of using iOS as a building block and developing forward. Creating something new, unique, and, in their eyes, better. Because Samsung chose not to do that, and they decided to go a decidedly different way, we have the proceedings we have now.
Well, Apple has a part to play in all of this, too, and I’m certainly not saying that their hands are clean here, either. But, for the sake of this particular article, yesterday’s revelations are our focus. And honestly, this isn’t going to be about how Samsung deserves this, or anything like that. No, instead, as I mentioned above, I want to talk about what comes next.
I’ve seen people on the social networks suggesting that Samsung should drop TouchWiz completely, and just focus on releasing handsets that are based on stock Android. For all intents and purposes, this is probably the only definitive plan that Samsung has. Or, that they may have, if the court does indeed make Samsung change things around in the software department. But, I think that this shouldn’t be Samsung’s permanent forward momentum.
Devices like the Galaxy Nexus are great, especially for those who like the vanilla Android experience. But, as we’ve seen with the launch of the Verizon and Sprint branded versions of the device, just because it’s a Nexus device doesn’t mean all those great things we thought it used to. Like quick updates. I believe this is one reason why most people prefer stock Android over the other options. So, take those quick updates away, for whatever reason, and you may find that most people would prefer to stick with proprietary software.
So, what should Samsung do next? That’s a good question. I believe, truly, that this is the best time that Samsung could use to go back to the drawing board. Let’s face it, TouchWiz is either loved or hated, and these whole legal proceedings could be used to give Samsung a chance at making the best proprietary software on the market. To go right up against HTC’s Sense UI, or even LG’s custom software. To build it from the ground up to accentuate Android’s features, and not just beat them down. To focus on not just Samsung-branded hardware, but to capitalize on the multi-manufacturer greatness that Android is.
I would say that a Galaxy Note 2 running stock Android would be an interesting sight to behold, but that’s not going to happen. It will be another Samsung device with TouchWiz on it. That should be the last one. After the Note 2 launches, Samsung should go back to the drawing board, and build a new, unique and attractive proprietary software that they can unveil on their next flagship device at the start of next year (or sooner, if they can make that work).
What do you think, Dear Reader? Should Samsung drop TouchWiz and go with stock Android from here on out? Or should the company go back to the drawing board and create something new and worthwhile? Let me know what you think Samsung should do next.