Switched On: Kin's seven deadly sins
Each week Ross Rubin contributes Switched On, a column about consumer technology.
There may have been a lot of behind-the-scenes machinations at Microsoft and Verizon that resulted in the discontinuation of the Kin One and the Kin Two, but there were also many marketplace miscues that resulted in the demise of the handsets. Here, then, were Kin's seven deadly sins:
Lust. With the Kin handsets, Microsoft was too eager to get its hands into the pockets of young social networkers for whom the smartphone market had proven elusive. The key paradox of this was that the Kin data plan was the same for that of other smartphones at Verizon, and that continued to shut out those who aspired to mobile digital sharing nirvana.
Gluttony. If Microsoft was angling to get Verizon to offer a sweetheart deal for Kin data, it certainly didn't help its cause with the automatic backup of rich media to the Kin Studio website. If there was one aspect to the Kin handsets operation that may pave the way toward future success, it was the Silverlight-based web interface to all the media that was captured with the device. This also allowed Microsoft and Sharp to minimize the amount of on-device storage. However, constantly backing up high-resolution photos and even standard-definition videos to the cloud required a lot of bandwidth, making it difficult for Verizon to justify a "light" data usage plan for Kin users.
Greed: Cutting back on on-board storage was just one of the ways Microsoft and Sharp cut corners with the otherwise respectably-designed Kin hardware. The Kin One in particular had a small 2.5-inch screen that required a fair amount of scrolling even for Kin's native user interface. Browsing websites on the device required endless scrolling. Greed was also evident in Microsoft entering the hardware market itself while trying to push Windows Phone 7 to licensees. And if there's a short-term silver lining to the Kin story (apart from Kin Studio), it's that Microsoft will no longer be in competition with its hardware partners.
Sloth. The giants of the social networking space include Facebook and Twitter, for which Kin offered at least fair support. But rather than support Flickr for images and (Google-owned) YouTube for video, Microsoft plugged in its Windows Live services for these media. Kin also lacked established functionality such as a calendar and instant messaging as well as support for fast-growing services embraced by social networkers such as Foursquare.
Wrath. It's certainly no secret that the Windows Phone 7 reboot has been driven in large part by Windows Mobile falling far behind the licensing revenue-killing success of Android from Microsoft's foremost rival Google. Windows Phone 7, though, still isn't here, and so Kin represented a fork from the main group that came to market without all the support of an app marketplace. Kin could not compete with more capable smartphones available at Verizon (and elsewhere) that offered nearly all of its functionality to its target market, plus a much broader range of features.
Envy. The heart of both Microsoft's and Google's mobile operating system strategy is to have diverse handsets running its software. Still, both companies look at the level of integration Apple can achieve with the iPhone and are drawn to have a heavier hand in the design of handsets. This sort of licensor regret is part of what drove Google to create the Nexus One and likely also contributed to Microsoft's decision to create the Kin handsets.
Pride. Perhaps the most ominous sign of Kin's failure was that its user interface was in some ways a more tricked-out version of the one for Windows Phone 7's top-layer tiles. Microsoft gussied up the terms used to describe the user interface with lingo like "the Loop" and "the Spot," the latter referring to a tiny green target for dragging interface items. Microsoft confidently cited extensive research with young social networkers as evidence that the generalist approach of smartphones wasn't as good a solution for managing the three kinds of "friends" by Generation Upload. Ultimately, though, Kin made far too few friends of any kind at the cash register.
Ross Rubin is executive director of industry analysis for consumer technology at market research and analysis firm The NPD Group. Views expressed in Switched On are his own.
There may have been a lot of behind-the-scenes machinations at Microsoft and Verizon that resulted in the discontinuation of the Kin One and the Kin Two, but there were also many marketplace miscues that resulted in the demise of the handsets. Here, then, were Kin's seven deadly sins:
Lust. With the Kin handsets, Microsoft was too eager to get its hands into the pockets of young social networkers for whom the smartphone market had proven elusive. The key paradox of this was that the Kin data plan was the same for that of other smartphones at Verizon, and that continued to shut out those who aspired to mobile digital sharing nirvana.
Gluttony. If Microsoft was angling to get Verizon to offer a sweetheart deal for Kin data, it certainly didn't help its cause with the automatic backup of rich media to the Kin Studio website. If there was one aspect to the Kin handsets operation that may pave the way toward future success, it was the Silverlight-based web interface to all the media that was captured with the device. This also allowed Microsoft and Sharp to minimize the amount of on-device storage. However, constantly backing up high-resolution photos and even standard-definition videos to the cloud required a lot of bandwidth, making it difficult for Verizon to justify a "light" data usage plan for Kin users.
Greed: Cutting back on on-board storage was just one of the ways Microsoft and Sharp cut corners with the otherwise respectably-designed Kin hardware. The Kin One in particular had a small 2.5-inch screen that required a fair amount of scrolling even for Kin's native user interface. Browsing websites on the device required endless scrolling. Greed was also evident in Microsoft entering the hardware market itself while trying to push Windows Phone 7 to licensees. And if there's a short-term silver lining to the Kin story (apart from Kin Studio), it's that Microsoft will no longer be in competition with its hardware partners.
Greed was also evident in Microsoft entering the hardware market itself while trying to push Windows Phone 7 to licensees. |
Sloth. The giants of the social networking space include Facebook and Twitter, for which Kin offered at least fair support. But rather than support Flickr for images and (Google-owned) YouTube for video, Microsoft plugged in its Windows Live services for these media. Kin also lacked established functionality such as a calendar and instant messaging as well as support for fast-growing services embraced by social networkers such as Foursquare.
Wrath. It's certainly no secret that the Windows Phone 7 reboot has been driven in large part by Windows Mobile falling far behind the licensing revenue-killing success of Android from Microsoft's foremost rival Google. Windows Phone 7, though, still isn't here, and so Kin represented a fork from the main group that came to market without all the support of an app marketplace. Kin could not compete with more capable smartphones available at Verizon (and elsewhere) that offered nearly all of its functionality to its target market, plus a much broader range of features.
Envy. The heart of both Microsoft's and Google's mobile operating system strategy is to have diverse handsets running its software. Still, both companies look at the level of integration Apple can achieve with the iPhone and are drawn to have a heavier hand in the design of handsets. This sort of licensor regret is part of what drove Google to create the Nexus One and likely also contributed to Microsoft's decision to create the Kin handsets.
Pride. Perhaps the most ominous sign of Kin's failure was that its user interface was in some ways a more tricked-out version of the one for Windows Phone 7's top-layer tiles. Microsoft gussied up the terms used to describe the user interface with lingo like "the Loop" and "the Spot," the latter referring to a tiny green target for dragging interface items. Microsoft confidently cited extensive research with young social networkers as evidence that the generalist approach of smartphones wasn't as good a solution for managing the three kinds of "friends" by Generation Upload. Ultimately, though, Kin made far too few friends of any kind at the cash register.
Ross Rubin is executive director of industry analysis for consumer technology at market research and analysis firm The NPD Group. Views expressed in Switched On are his own.
























It's the SideKick (a once great device still with the best keyboard ever) after MS idiots wrung the life out of it.
I think with a firmwear update it could have worked with on pre paid plans in Europe. Where most people are pre-paid or "pay as you go" As most networks offer an "unlimited" (i.e. 250MB) Internet plan. I would have recomended it to friends of mine that aren't in need of a full smartphone. I was excited to see it and would thought about moving from a iPhone 3GS to a KIN Two
Not sorry that the Kin is dead, but I'm hoping that the Kin studio or at least the idea of it survives. Had the opportunity to play with it and I liked the idea of having everything on my phone available on the web.
True, you can already do this, but this implementation was pretty much seamless which is good for the average user.
I don't really get the point of this article. We've read the full story behind the kin that you guys posted, and none of that lines up with Ross Rubin's "7 deadly sins". It's pretty clear he didn't read that article actually otherwise he'd know things like why MS decided to make the Kin in the first place, and why it turned out to be such an awful product.
The only reason I've been reading these Kin articles is to see they pay homage to the Courier.
Oh, Courier... My first and only love.
MS is pathetic!
They fucked their investors out of millions in r&d money for that Kin and the subsequent PR cost just to see it erode into nothing!
Ballmer should be shafted for his incompetence.
This is what you get when you have a bunch of nerdy, middle aged corner ofice schmucks trying to make stuff for folks 1/10 their age.
IMHO, if they had gotten the Xbox team to do this it probably would have been a winner.
@pspitts
Settle down dude. Win Phone 7 is just around the corner.
Sin #8 its not Apple product. Right engadget?
@eka
Quick! Name me the Apple product that was killed just 6 weeks after release (billions wasted). I'll be waiting....................
If a Kin fell in the forest, would its owner care to try to find it?
@whitesoxing
its owner won't be able to find it anyway without (GPS) location tracking.
yo engadget.
http://i47.photobucket.com/albums/f159/RaulMonkey/Animated/beating-a-dead-horse.gif
@aemengo isn't that a llama? if it's a llama i'm fucking killing you ¬¬
you also forget that when Microsoft announced the Kin, even Engadget's response was "why bother?"
It was doomed from the start.
Cheap Ugly Stupid Crippled Stupid Ugly Cheap
Oh enough already engadget
MS did it to themselves. My daughter considered the Kin, but the data plan was ridiculous. People can get cars for a smaller monthly these days.
What could have saved the Kin:
1) $30/month for unlimited SMS, MMS, IM and data
2) Removal of Kin Studio
3) microSD card reader
4) Kill the Kin One
Leave the hardware and software specs the same. It's a mid-range device for a reason. If you could have given me the Kin Two, with a cheap plan, removable storage, and no cloud storage bullshit for $50 without a stupid rebate I would have seriously considered that at the least. The current Kin One and Kin Two never even crossed my mind as purchase worthy.
@kenny goo
I agree with you on everything except for kill the kin one. Almost every review of the two phone's cites the one as the more attractive and fun to use choice. The key board feels way better and the size is a nice change from the bigger and bigger flat screens we've been shoving in our pockets. Killing the 2, which was closer to just more of the same (going against what MS was trying to achieve here) would've made more sense.
@AWINRARISYOU
Hey, if you love square phones, smaller, lower res screens, less storage space, and less capable cameras, by all means, you're welcome to love the Kin One over the Kin Two, but you're very, very much in the minority on that one. Not a single person I've heard from or spoken to about the Kin actually liked the Kin One. Whether it fit the norm or not, the Kin Two was the much better phone and probably sold a lot better.
I don't mind another Kin story but framing it with the Seven Sins feels kind of forced.
Tell me how a mess of a product like Kin makes it to market but an ingenious UI concept like Courier doesn't. Please MS, hire someone who knows what the fuck they are doing. Ballmer needs to go!
@GAM3R Have you ever actually used a zune? Because as an mp3 player it is a much better device than the iPod. But it has the Microsoft name attached to it so tweeners and hipsters won't even give it a chance. It's all marketing.
@GAM3R
Zune was meant to be a MP3 player as opposed to an iPod Touch wanna be. It succeeds quite well at that. Microsoft provides a small amount of very well made apps for the Zune HD. I don't use any of them though. That's one of the main reasons why I bought it over an iTouch. I wasn't really interested in the apps. I just listen to music and podcasts and liked the smaller form factor.
Just because Microsoft didn't split their dev community by allowing 3rd party apps on the original Zune HD doesn't mean that there aren't going to be any for WinPho7. We already know there are going to be plenty. No one makes software development easier than Microsoft. Period.
WACK ... SMACK ... THUMP ... THUD ...
Um, Engadget? That horse isn't moving anymore.
The Kin died. So what. At least the iPhone didn't die.
I still believe Kin was an experiment for MS. They knew the risks and they just wanted to try something.
@Ravenwoods Actually I believe the Engadget-reported inside information that it was all ego-fused internal conflicts at MS that ruined KIN. I actually feel worse for Danger. MS bought them out just to ruin them completely.
@aubreyq
I would love to hear the ex CEO of Danger, Andy Rubin's reaction on this. Before this, MS bought WebTV from him and also took it nowhere.
This horse is dead, put down the stick!
@HighestRanked2 Man you are such a pathetic joke, if you were a cellphone you'd be a kin.
Hey guys!... I just bought my Kin today!... I love it... it's a really great phone and it has a... oh wait... DOH!
What if you're someone who purchased a Kin on a two-year contract?... I feel sorry for those suckers -- I mean people...
You just have to wonder how many thousands of handsets sit in warehouses, never to be opened. Wouldn't it be a cool geek-venture if you could get android running on it and then re-sell all those unused handsets? Even Engadget had to admit the hardware wasn't too bad (esp. the K2). It would involve too much pride-swallowing, but MS could recoup at least some of their losses by selling Kindroids.
@fanchettes lol even with android these things would be dead they seemed like only an experiment to begin with even if somebody did shoehorn 2.0 or later on it. They may as well suck up the studio and make it an app for WP7 and then disassemble these and sell the parts or something.
And people down-ranked my comment when I said that Engadget was dwelling on this thing after it died....... -_-
@HighestRanked2 +1