Check out: "Palm: this is your survival guide" - www.engadget.com http://www.engadget.com/2010/03/19/palm-this-is-your-survival-guide/?icid=engadget-iphone-url http://digg.com/apple/Palm_this_is_your_survival_guide'; Oh Palm. Just a little over a year ago your future seemed so bright, so renewed. You walked away from CES 2009 reborn, held aloft by a completely innovative new mobile operating system, a striking piece of hardware, and a feeling amongst the press and investors that you were back in the game and playing to win. Now, less than a year and a half later, you've nearly returned to the dark and desperate place you'd found yourself in at the end of 2008; a rapidly declining mindshare, the bottom falling out of your stock, and bad dips in phone sales. All of it is leaving you backed into a corner where the common perception now is that you've got to sell to survive at all. So what went wrong? How did such a promising launch lead to such a disappointing reality? And how can you wrestle your way back from the brink yet again? Is that even an option?

In 2007 the editors of Engadget penned an impassioned open letter to the company, pleading for many of the changes we eventually saw at Palm. This isn't a follow-up, but it's very much in the spirit. We're going to take a look at the missteps that put the company in its current spot, and talk about what we think can pull it back out. Palm, it's time for a little tough love... again.

The mistake: Launching the Pre and webOS at CES 2009, but not delivering a product until just days before the assumed announcement of a new iPhone.

Palm, you had more heat than a company could reasonably expect after your announcement of the Pre and webOS at CES 2009. Certainly amongst journalists, the feeling was one of utter elation at the products you'd just announced; an innovative, slickly designed OS and phone which looked to be solid competition even to the likes of the iPhone. Post-CES, the buzz surrounding the eventual release of the Pre was high, even though you'd partnered with Sprint (more on that in a moment). Yet when push came to shove, you let the excitement drag on for far too long, and what started as a high pitch siren started to wind down to sub bass drone. It didn't help that once your launch date was finally announced (nearly six months after CES), it came just days before Apple was set to announce a new handset. In the end, you still had some heat, but the cooling off period had already begun.

The fix: You can't rewrite history, but take this as a lesson -- no one wants to eat melted ice cream, especially when they know they're about to get a brand new banana split in a few minutes.

The mistake: Partnering exclusively with Sprint on the Pre launch.

Sure, you didn't have a great bargaining position before the Pre was shown off, but choosing to enter into an exclusive agreement with the third-place, ailing carrier with no clear picture of when you'd move to other partners was about the worst thing you could have done. We're not saying Sprint is necessarily a bad carrier -- in fact, when testing the Pre for our review, we thought the combo was excellent. Still, pairing one down-on-its-luck company with another doesn't often make for fireworks. You should have begged, borrowed, and stole to launch this thing on Verizon or ATamp;T. At the end of the day, it comes down to audience. In some ways, it might have been better to launch with T-Mobile, which would have allowed you to at least quickly ramp up your GSM sales overseas. As it stands now, you've only got a scant amount of partners in Europe (ignoring a potentially huge market), and you've been slow to bring on new carriers (hello, SFR).

The fix: Again, this one is a done deal, but spreading the love to every carrier you can get your hands on should be (and clearly is) a primary goal right now. The more eyes on these devices, the better chance you have of staying in the game.

The mistake: No SDK -- and more importantly no PDK -- out of the gate.

You really needed to win developers over to your platform quickly, but it was difficult to do that when you launched the SDK with only a limited pool of partners, then expanded that slightly as the months wore on. Additionally, you should have given devs access to the Pre's full capabilities with something like your PDK right out of the gate. While you were espousing the joys of web standards (a great idea without question, but not enough to make your phone feel competitive), users were getting stripped experiences and sluggish interactions with software on your devices. It's good for some things, but not for everything -- this is evidenced by some of the embarrassingly bad attempts at gaming we saw before the PDK was available.

The fix: You've done it -- you've got the PDK into wide release, and you've got devs showing off what these phones are capable of. Based on what we've heard from developers, webOS is actually the easiest and most pleasant mobile OS to develop for -- and you need to start evangelizing that message! The other thing you have to do is make these devices attractive to devs and users because of potential you show through apps, which brings us to...

The mistake: Awful marketing at launch. Sustained awful marketing.

Palm, have you ever watched one of your ads? They are unspeakably bad. In particular, your launch spots featuring what seemed like an extra from the The Cell (and hell, directed by Tarsem, who made 'The Cell') not only failed to show what your beautiful and sophisticated phones were capable of, but alienated viewers almost universally. The fact that these ads weren't pulled off the air immediately was troubling, but more disturbing was the fact that they seemed to confirm that you didn't understand how to market your product, or what your demographic was. Adding insult to injury, you mostly allowed Sprint to steer the ship with showing off your product, which was fine, but it wasn't like the Pre was being perfectly framed by their ads either.

We expected round two would be much better, considering the variety of very vocal objections to your first set, and especially considering that you had a new, wealthier partner: Verizon. Somehow, these ads turned out worse than the first round, not only once again failing to show off your phones (now with other amazing capabilities like 3D gaming), but genderizing the Pre and Pixi in offensive, pointless, and downright stupid spots that insulted those you hoped to be selling to, and simply turned off everyone else. In fact, throughout your career in selling these phones, the only ad which effectively did anything to show how powerful webOS was was the underused Pixi ad we covered in November.

The fix: This is so simple it's stupid. Show your phone doing what it does best -- show it running 3D games, Facebook, and Twitter apps. Show how it notifies users without pop-ups, show how you can switch between all those apps quickly, show how fast web browsing is and how nice pages look (and show pinch-to-zoom!). Show your App Catalog and all the software that's available, show off how your gestures work, show off how easy it is to search for things... but most importantly, don't be afraid to compare it to the competition. You're beating Android's pants off with your game offerings -- and hey, guess what most people are buying in Apple's App Store? You're the only other phonemaker playing in their space, and you've done nothing to sell it. Your newest ad is a step in the right direction, but only about a quarter step. You're still making things gender specific, and you're still not really showing how the phone works. If you do anything with whatever money you have left, you should pour it into an advertising onslaught that simply doesn't pull punches. You have a good product, it's just that no one knows about it or thinks it's for them.

And we can't stress this bit enough: stop acting like your phone is just for girls. Seriously, it's like you've taken Roger McNamee's stupid comments from the All Things D conference about the Pre having a mirror on the back and used that as the basis for your marketing campaign. We're not sure what bunk piece of demographic research you're utilizing to make these decisions, but we're pretty sure reality doesn't bear that research out. You're simply making a huge mistake by trying to "sell" these phones to women -- again, you insult your target demo, and you turn off other potential buyers big time.

The mistake: The iTunes sideshow.

We may never fully understand this one. It seemed like a cool idea at the time, to be sure, but you'd think someone at Palm would have known better than to get into such a silly battle with Apple when your position wasn't so hot. For some reason, you guys thought it was important to offer native iTunes syncing -- important enough to invest time, energy, and resources into -- but we couldn't say why at the end of the day. We're not going to spend much time on this one, because we've already let you know what we think the reasonable, rational thing to do would be... but it bares repeating.

The fix: Another no-brainer. You should have partnered with DoubleTwist out of the gate, or just written your own desktop app that would allow syncing for your devices. Honestly, people don't care that much as long as you give them a sensible, simple way to get music and media onto the phone. You never had to waste a single second on this -- in fact, you could have come out looking like heroes by teaming up with another open source, underground champion like DVD Jon. Instead, you had a protracted battle with Apple which you essentially lost, and now you're telling users not to upgrade their copies of iTunes. Frankly, it looks silly.

The mistake: The Pixi.

We get what you were thinking here: give consumers an updated version of the Centro (your last successful device), a cheap, entry level smartphone to get them into your ecosystem. You figured people at shops would say, "Hey, instead of buying this $99 featurephone, I can get this totally grown up smartphone!" And that is a good strategy... for a world where there's no $99 iPhone or Droid Eris. Unfortunately, we don't live in that world (or, we live in that world, but it's two years later). Your Centro strategy doesn't work anymore, because now the most exciting and feature-packed smartphone (in the eyes of many consumers) can be had for the same price. What's worse, you designed the Pixi (admittedly a nice handset) with slower, less capable hardware than the Pre, meaning that even if you like the form factor, you're still cheated out of the best software (at least for now, Palm says that will change soon) -- and it means you have to devote more resources to OS development because you've got parallel paths. Not a great situation for a company that's already hamstrung by a small staff.

The fix: Kill the Pixi. Seriously -- kill it, or give it the same specs as the Pre. You're going to alienate some users, but it's worth it in the long run, because whatever resources you're pumping into this device are ultimately going to be wasted. There's no way you can sustain this kind of fragmentation at your size (even Google can't do that... and they're Google), and once your next gen device rolls around (if it ever does), something tells us the gap between products will grow even wider.

The mistake: Hardware issues which plagued the Pre, with no outward acknowledgment or rush to correct.

Let's just be honest, guys -- you've had some manufacturing and design issues with the Pre. We've seen countless reports, read too many blog posts to recall, and heard all sorts of horror stories about broken sliders, power buttons that stop functioning, the "Oreo cookie" effect, and more. Hell, even our first review unit broke!

Let me switch to first person here and tell you a story. When the Pre came out, I emphatically recommended the phone to a good friend of mine who was a Sprint subscriber -- I sold it to him so well I should have gotten a commission. I was truly excited about webOS and all its possibilities (I still am to a large extent). My friend went ahead and bought the phone, only to be wracked with build quality and battery life issues. He regularly complained that his slider mechanism had begun to slip, his power button required a "special" hard push to function, his MicroUSB door snapped off (big surprise)... and that was to say nothing of his battery life problems. In addition, the software issues which started around the first or second update (the sluggish behavior and random "too many cards" messages) drove him to not just be unhappy with the phone -- but to really hate it. By allowing these hardware and software issues to go unchecked or unacknowledged, Palm isn't just creating issues for its customers... it's making enemies.

The fix: Make better hardware, and own up to issues as soon as you see them. Maybe this is easier said than done, but if you want to continue to be transparent and available to your customers, then you have to be able to speak up when something goes wrong. Of course, instead of just issuing an "improved" version of the Pre when it came time to release on Verizon you could have just...

The mistake: The Pre is looking pretty dated. You need new hardware.

Look, we get it. We know your party line: the Pre has been out for less than a year. Ah, but remember, you showed us the Pre back in January of 2009 -- which means it's been in front of us for nearly a year and a half. In that time we've seen a new iPhone, the Droid, the Nexus One (and Desire), the HD2 and TG01, Sony Ericsson's X10, and plenty more. Now, sure, you share similar screen and CPU specs with the iPhone 3GS, but you've still got worse build quality and a smaller display -- and people notice. The trend of WVGA displays and faster, more efficient CPUs (hello, Snapdragon) is clear, and you can't afford to sit on the sidelines with a device which is over a year old by many people's standards. We know that you still have a few partnerships to sort out, but if you keep bringing these same devices to more carriers (or don't give us an indication that something new is on the horizon), you're practically hammering nails in your own coffin. You need to innovate on every side now.

The fix: Release a piece of hardware that bests what is currently out there, and put it in an extremely hot looking package... that's also built like a tank. We think you've done a beautiful job on industrial design, now take what you've been working with, apply it to something with the build quality of the Droid, maybe toss in a landscape keyboard, high res camera, and a nice, large screen -- we promise people will take notice. Oh, and don't release it on Sprint... even if it's got WiMAX. And for heaven's sake: advertise the hell out of it. For everyone.

Now we'll be the first to admit -- we have no idea if what we think actually makes any sense for Palm. We're not marketing experts or a design committee -- we're just a group of gadget enthusiasts that want to see companies making smart, innovative products succeed. Palm, you've done some amazing work in the past year or so, and we really do applaud the effort and artistry you've brought to the smartphone world, but you're not taking this thing into the endzone... you're not even half way there. You've got to compete harder, and you've got to start to focusing on what works and start killing what doesn't. You've got a lot of the latter and not enough of the former -- and it's time to flip that equation.

On a personal note, Palm, if you're looking for a Robin to Jon's Batman: you know how to get a hold of me.

-------------------------------

This article came from the Engadget iPhone App, which features everything from the latest smartphone news, to reviews and hands-on looks at laptops, HDTVs, gaming, and more. To learn more about the app or download it go here: http://www.engadget.com/downloads/iphone

Check out: "HTC Legend review" - www.engadget.com http://www.engadget.com/2010/03/10/htc-legend-review/?icid=engadget-iphone-url http://digg.com/gadgets/HTC_Legend_review_Engadget'; After four three flavors of the HTC Hero, the Taiwanese mobile giant has finally brought back the chin with an additional lick of aluminum and a similarly quirky name -- the Legend. If this alone isn't of much interest to you yet, just bear in mind that this is HTC's first Android 2.1 device with Sense UI. It didn't take much for us to fall in love with this Android phone at MWC -- HTC convinced us of its unibody toughness by banging it against the wall, and needless to say, the vibrant AMOLED screen caught our eyes, too. However, there are still some questions to be answered before we can decide whether the Legend lives up to its name, especially on battery life, wireless reception, camera quality and software performance. Unless there have been major tweaks, we'll try not to bore you with features already seen on the Hero -- so please, won't you join us?
%Gallery-87570%

Features and build quality

Those who've used the Hero for some time will spot many similarities on the slimmer Legend. The phone's general anatomy on the front and sides remains unchanged, except for the keys below the screen -- the Search and Back buttons have pushed the entire row to the left, thus killing the pick-up-call key and flicking the power button to the top of the phone (near the 3.5mm headphone jack). Naturally, some may miss the ability to jump straight to the dialer, and the keys' occasional stickiness on our unit don't help, either, although this might be an isolated issue. The volume buttons -- now in the form of a thin silver bar that sticks out slightly -- have been moved up from the slope underneath to the straight side, making them more reachable and less prone to accidental presses. On the contrary, we found the new earpiece to be a tad higher than where we'd like it to be, so we often had to deliberately hold the phone lower on our ear to hear the call. The speaker on the back was amazingly loud, so good thing that we can quickly mute the ringer by placing the Legend face down (courtesy of the G-sensor, of course).

Now, we can't speak on behalf of everyone here regarding the trackball being replaced by an optical trackpad -- in the long run, yes, the latter should in theory last much longer than the trackball, but there's no doubt that some prefer stroking the little ball to the trackpad that provides no tactile feedback. We lived happily with both, anyway, although the flat trackpad button was easier to push. Like the Nexus One, the connector below is now a micro-USB port instead of ExtUSB as found on the Hero -- welcome to the party, HTC!

Moving on to the backside: due to the aluminum unibody construction, we no longer have a big battery cover that required some skillful hands and long nails to pry open on the Hero; instead, we access the battery, SIM card and microSDHC card (spring-loaded slot) under a smaller rubber cover at bottom, while the camera, LED flash and speaker near the top are padded with some rubber. Here's an advanced warning, though: the battery cover is actually part of the cellular radio antenna, so removing it while your phone's still on means you'll be temporarily out of reach. Obviously, letting the kids or the dogs get near your rubber cover may render your Legend useless. Flipping open the inner cover underneath will also loosen the battery thus killing the power. Naturally, this slide-in design for the battery bay means third-party manufacturers will struggle to produce batteries of larger capacity. As for the general feel of the Legend's metallic body, it wasn't as slippery as we had initially expected, but understandably the Hero's back has better grip and provides a warmer touch.

Software

As we've seen at MWC, HTC's made some pretty neat changes to the Sense UI for Android 2.1, and we're not just talking about those fancy colors and icons. First is the handy Leap feature that lets you view all seven homescreens in one go (similar idea to the XPERIA X1's panel interface), and this can be triggered by pinch-zooming any of the homescreens or by pressing the Home button when you're on the main screen. Leap's been responding pretty well all this time with both input methods, but we've noticed that the panels are actually just stills of each homescreen as last viewed -- it would be nice if HTC can make them all live, or at least auto-update the panels every now and then. Next up is Friend Stream -- an aggregator app (with widget) essentially for stalking people by the means of Facebook statuses, Flickr and Twitter (which launches Peep when you click on a tweet). While this isn't exactly a breakthrough feature -- Motoblur already does this with its Happenings app -- it's no doubt a welcomed addition to HTC fans.

A more useful update is the text highlighting tool -- on the Hero we've had to guess where we were highlighting due to the lack of a magnifying glass and start-end pointers, but thankfully HTC's figured that one out and stuck both features onto the Legend, and garnishing them with a small shortcut bar for copying, searching and sharing. On a similar subject, the keyboard is still as usable as the one found on the Hero -- we didn't notice any changes. Another tweak that deserves massive props is the menu for widgets and shortcuts, where you can now dive straight into the Program list instead of having to go into Shortcut first, and additionally, "HTC Widget" and "Android Widget" are now united under "Widget." Someone in HTC's office deserves a big hug and some chocolate for these fixes, but there are bonus candies if they can also fix Adobe Flash on the Legend -- the videos that we managed to play came out with pretty low frame rates (and needless to say games were not playable at all, if anyone cares), so we'll have to make do with YouTube and our own videos (3GP, 3G2, MP4 and WMV supported) for now.

General performance

Even though the Legend (Qualcomm MSM7227 at 600MHz) is clocked at just 72MHz more than the Hero (MSM7200A at 528MHz), we thought it'd be interesting to compare boot-up times, and behold: the Legend only needed about 20 seconds, whereas the Hero took almost twice as long. Praise be the Android 2.1! We then decided to test the Legend's battery and camera by treating it to a rare sunny trip around London. As fun as it sounds, the reflective nature of the AMOLED screen meant we had to keep web surfing to the minimal while out in the open -- perhaps some Super AMOLED could fix this.

For most of the day we listened to music and a bit of FM radio, took the occasional photos and videos, and stayed connected to the web via 3G (with Google Mail notifications and a Twitter app's automatic update enabled). After all that, the 1,300mAh battery lasted us for around six hours only -- definitely not enough for those on a constant move or even the average gadget consumer these days, and other reviewers have reported similar battery issues. This is pretty much the major drawback on the Legend, and we hope HTC will have a solution for this -- a software fix or even bundling a spare battery will keep us happy. Other than that, we were pretty happy with how the Legend had managed to stay snappy most of the time, and more importantly, call quality was good on both ends even when used on the busy London roads.

We've also spent a few nights with the Legend in bed. First thing we noticed was that with the brightness turned down to minimal level, the AMOLED screen was suddenly given a brown tint and some noise pixels. Again, this could be just the general disadvantage of AMOLED that could be fixed by coping with one or two brightness levels up. A more pressing matter that we discovered on the Legend was the weaker WiFi (802.11 b/g) reception compared to the Hero and many other phones -- in the same spot, the Hero managed two bars while the Legend struggled with one or none at all, which ruined our bedtime web surfing routine. That said, there's always the good old 3G if you're on an unlimited data plan.

Camera

It isn't a nice thing to say, but we do have just a bit more hate than love for the Legend's camera. The 5 megapixel pictures taken during the day turned out pretty good, but night shots were hard to focus and some were terribly noisy -- it's what you get with small sensors anyway so we'll leave it there. However, the 640 x 480 videos were just choppy in general, and they became much worse when filmed in the dark. We've seen better filming performance on other smartphones so there's clearly some work to be done. To cheer things up a bit, the LED flash may be small but it did its job well with objects within two meters. You can see all the camera's good and bad below.

Video filmed during the day:

Video filmed at night:

%Gallery-87636%

Wrap-up

It's safe to say that HTC's broken yet another mold with the Legend, stunning the world with both its hardware and software design. There's no question about the unibody's toughness, and many other features we've seen here are of significant improvements over the Hero, namely the AMOLED screen (in general), FM radio, optical trackpad (debatable), still camera and the new goodies plus performance boost in Sense UI. Sure, there are major flaws in the battery life and video recording performance, but the positive mind in us are hoping that these can be fixed via a software upgrade, if they weren't of hardware glitches. Some may have hoped for some 720p video capture capability, but hey, isn't that what the Desire's for? We hope so. Anyway, we'll know which one's of the best value when both phones are available in European shops.

-------------------------------

This article came from the Engadget iPhone App, which features everything from the latest smartphone news, to reviews and hands-on looks at laptops, HDTVs, gaming, and more. To learn more about the app or download it go here: http://www.engadget.com/downloads/iphone