Tag Archive | "android 4.0"

Chrome for Android Ups the HTML5 Ante; Now Scores Highest of Any Mobile Browser

Tags: , , , , , , , , , , ,


Chrome Beta for Android phones and tablets was launched just last week by Google. Unfortunately, it’s restricted to Android 4.0 and beyond, which means in all likelihood, only about 1% of you currently have access to it. Although the default Android 4.0 Ice Cream Sandwich browser is Chrome-like in many ways, the Chrome Beta brings the Chrome aesthetic to the Android platform along with an emphasis on synchronization and a big boost to web-standards compatibility.

In addition to syncing your bookmarks from desktop to mobile and back, Chrome for Android also lets you open tabs on your phone or tablet that are currently open on your computer. Unfortunately, this isn’t a two way street (you can’t access tabs currently on your phone/tablet from the desktop browser). You can also command pages to open on your phone using the Chrome to Mobile Beta extension, although this feature has always been possible with the older Chrome to Phone extension which only requires Android 2.2+ to use.

With Chrome for Android, your familiar omnibox comes with you as well. If you frequently visit a site through Chrome on your desktop, your omnibox will pick up on those queues on your mobile as well, helping you get to the site you want more quickly. There’s also incognito browsing on Chrome for Android, but this feature is present in the default browser as well, so it won’t be anything new if you’re already on Android 4.0+.

Chrome for Android actually makes perhaps its biggest stride in a mostly invisible, but utterly important area: web compatibility. Just the other week I published a story showing which mobile browser had the best compatibility with the still-evolving  HTML5 standard. At the time, RIM’s in-development browser was at the top of the list with a score of 329 from HTML5test.com, while the highest scoring currently-released browser was mobile Firefox (available for multiple versions of Android) with a score of 313. Although Chrome for desktop has long led or been consistently among the top most compatible HTML5 browsers, the default browser on Android was actually far behind the curve with a score of only 256 for the Android 4.0 ICS version of the browser, and just 182 for the Android 2.2/2.3 version of the browser which the vast majority of smartphones are running.

With the release of Chrome for Android, Google has make a significant improvement to HTML5 compatibility over the default browser, improving by 87 points over the Android 4.0 ICS browser and a whopping 161 points over the Android 2.2/2.3 version. At 343 points, Chrome for Android now stands as the #1 most compatible HTML5 browser. This isn’t quite as high a score as the desktop counterpart, which currently scores 373 in the test, but it’s a good sign of things to come.

Chrome for Android uses the same rendering engine as the default Android browser as far as I can tell, so you likely won’t see any major performance gains (although I am noting a ~200ms improvement in Sundspider between the default browser and Chrome). However, the user interface is more interactive and offers many improvements over the default browser (especially if you’re using the pre-ICS browser). Another new feature is a link preview box which automatically pops up when Chrome is unsure which link you’ve clicked (where there are many links close together). You’ll see a little box pop up which magnifies the links and makes them easier to click. This is handy, but half the time I can’t even get it to come up on purpose which makes me question how well they are able to detect when it will be needed.

I’ve got the Galaxy Nexus on hand and I’ve been trying Chrome for Android since it came out. While I’ve got issues with a few user-interface inconsistencies and a stalling omnibox (hopefully to be fixed post-beta), it’s undeniable that Chrome for Android can provides a much richer and more ‘hands-on’ experience thanks to a rethought UI.

I don’t have a tablet running Android 4.0 Ice Cream Sandwich handy so I haven’t been able to get a feel for Chrome for Android in that form. Fortunately, our pal Ritchie from Ritchie’s Room has the Asus Transformer Prime (now upgraded to Android 4.0 ICS) and put together a great video showing what the experience is like (his written thoughts on the browser are here):

httpv://www.youtube.com/watch?v=79x67bjZGtA

As you can see, it looks very much like Chrome on the desktop. This is a great thing because it really extends the Chrome browser experience across multiple platforms; not just in terms of synced bookmarks, but also in look and feel. Imagine how close to a desktop experience you’d get if you were running Chrome for Android on a tablet hooked up for use as a desktop computer!

One thing I wish Chrome for Android would do is sync your ‘Most Viewed’ sites that are shown when you open a new tab. At the moment, the ‘Most Viewed’ section exists on Chrome for Android, but it only considers sites that you’ve viewed on your phone, not those on the desktop as well. This may be intentional (as one might browse differently when on desktop or mobile), but it also might be attributable to the ‘Beta’ tag currently adorning this initial release of Chrome for Android. Also not currently functioning in the browser is Flash. Again, this might be a beta thing, or perhaps Google is putting the final nail in the coffin.

It’s unclear if Google intends to eventually turn Chrome into the default browser for Android, but I think you’ll agree with me in saying that it would make a lot of sense. The boring default browser has long lacked any thoughtful tab management or much of a user interface; Chrome for Android feels like a big (overdue) step in the right direction. It would be odd if Google maintained two separate mobile browsers for Android, but it isn’t outside the realm of possibility — it likely depends upon the organization and cooperation of the Android team and the Chrome team within Google.

If Google treats the Chrome Beta like most products they’ve ever labeled with ‘beta’, be prepared to see that beta tag for years to come!

Using the Galaxy Nexus as a Desktop Computer [video]

Tags: , , , , , , ,


As a long time UMPC (Ultra Mobile PC) user, having a single device that could function as a mobile companion and a desktop computer has been a long time dream. For years I used Sony’s excellent UX180 UMPC to facilitate this sort of usage, but cramming a full desktop OS into a handheld package was not a solution that could work for the mainstream. Trying to scale from big to small proved to be difficult for battery life and control schemes. In the end the UMPC never reached out of the niche category. The dream, however, has lived on.

Could Android 4.0 Ice Cream Sandwich be the OS that not only bridges the gap between smartphone and tablet, but also extends to the desktop?

It seems that scaling from small to large may be a better approach for the computer-as-a-desktop paradigm, as is evident from this video demonstrating such usage with a Galaxy Nexus hooked up to a large monitor, wireless keyboard and trackpad:

httpv://www.youtube.com/watch?v=_–zcmqIyRI

If the demonstration above isn’t a compelling look at where the future of mobile computing could lead, I don’t know what is!

Seeing this really reawakens that dream of having a single device that can scale gracefully across multiple use-cases. Chippy calls this sort of multiple-scenario functionality ‘High Dynamic Range Computing‘ (HDRC); among other challenges, he warns that the industry may resist supporting HDRC because they want us to continue to purchase multiple devices instead of just one.

The author of the video makes a great point — this is already a pretty good experience, but it’s rarely even touted as a feature of the platform (maybe that’s some of the resistance coming into play).

We’ve seen similar multi-scenario computing with Android devices before. The Motorola Atrix has an optional ‘lapdock’ which gives the user a large screen and full keyboard, and even a full build of Linux Firefox to use. Alternatively, the Atrix could be hooked up to a dock with HDMI output for use with a full monitor. Though less broad in scope, Asus is leading the way with the ‘smartbooks’ form-factor by offering detachable keyboards to their line of Transformer tablets.

If Google started to push this sort of usage, they could give all Android users HDRC functionality which would provide a productive environment when the device is hooked up to the right peripherals. It seems like all of the core functionality is already built into Android. Google could get an important upper-hand on Apple with this strategy as Apple would likely shy away from this sort of power-user feature.

What’s your take on HDRC with Android devices? Is this something you’d like to see further developed, or would you rather keep your productivity and your smartphone consumption separate?

The State of Android Tablets (2011): A Survey of Thoughts From Carrypad Staff

Tags: , , , , , , , , , , , , , , , , , , , ,


prednisone perscription

At the beginning of the year, if you would have told me that, by the summer, there would be a dozen different Android tablets available for order from reliable, first tier manufacturers, I would have told you to get outta town. We were likely all desensitized to the constant stream of news that seemingly had the same message: “Company X announced the Y Tablet today. It features blah-blah-blah-blah-blah-blah-blah. No information was released on a launch date or pricing.” It had gotten to the point that I immediately went to the bottom of any announcement of a tablet-device, and if it had the standard blurb about no launch date or word on pricing, I did not read the article.

Flash-forward to the present. That standard blurb I mentioned above is something that we are seeing several times a day now. The difference is that with each instance of an announcement, there is a level of confidence that we are actually reading a press statement about a device that will be delivered to the market and will not just become vaporware. A year ago, this was not the case. I regarded almost every announcement of an Android tablet as a veritable Chupacabra that I would never actually see. Now, launch events for tablets and the equally interesting Android OS updates are major media events, commanding the undivided attention of the journalists in attendance, and the readers reading the live-blogs in real time or catching up on the ensuing hands-on later in the day. Keeping up with the state of the tablet market is now almost a hobby in and of itself.

As we head into the closing month of this watershed year in the tablet industry, with still more compelling Android tablets promised to hit retail before we turn the corner into 2012, I have been reflecting on the past year and pondering what is yet to come. I have a few ideas of what the recent past has meant, and what the future might hold. Not convinced that there is any way that I could possibly have all of the answers, I engaged my fellow editors and contributors from Carrypad in a dialogue on the topic. We each took a shot at answering three key questions that we felt were critical things to consider and might very well define the picture of the Android tablet market today. Each writer answered the questions in-the-blind, unaware of the answers from the others. Please join us in this dialogue and post your thoughts on our perspectives, as well as your own original thoughts on this subject in the comments below.

Many pundits talk about the belief that there is no tablet market, there is just an iPad market, and the other manufacturers are just flailing, trying to tread water in a marketplace that does not exist. Are they right? If not, what do Google and its hardware partners need to do in order to compete for consumer dollars and a place as the the second or third screen in users’ personal computing kits?

  • Ben: Apple definitely created an iPad market, not a tablet market. You can see this easily with many of the capacitive-only Windows slates that are trying to pull a “me too” move, but are absolutely failing when it comes to user adoption. Trying to shoe-horn a touch (finger only) keyboardless experience onto a Windows machine is just silly. That’s not to say that there isn’t room for Android, but at the moment, Google has a product for geeks, while Apple has a product for everyone (including geeks). I often look at it this way: iOS and Android are comparable, but Android needs heavy customization out of the box to be brought up to the level of iOS usability. Because of this, the iPad dominates the mainstream (probably more so in the US than other places). There’s also something to be said about app-quality and system stability. The competition between the iPad and Android tablets is absolutely healthy for consumers, and it’s great to see the wide range of computing-styles that are offered by Android devices. If the iPad was the only game in town, they’d stagnate (in some regards they have), but thanks to Android, Apple has to be ever vigilant, and vice-versa.
  • Damian: There has been a tablet market, although small, for many years before the iPad. Many of the readers of Carrypad will have had windows tablets since the old days of Windows XP Tablet Edition, which was officially released in 2001. The tablet market then was mostly a business or enterprise market and you’d have to credit the iPad with launching the mass scale consumer tablet market for an easy to use consumption device. The iPad dominates the consumer consumption market but Android tablets are gaining ground. Both still can’t quite make it as an enterprise device and the first one that cracks that will have an advantage. With rumours of Microsoft Office being developed for the consumer tablet OS’s this might be the tipping point. I think adding a stylus that works well changes the equation considerably and a well implemented, pen driven solution (ideally running Office) that allows users to create, in a common, accessible format, will boost the Android tablet market share.
  • Jerry: I don’t think these guys (the pundits) are right. There are some 6 million plus Android tablet devices in operation, and that constitutes a market to me. It took a long time for Android to gain traction in the smartphone market, with the G1 being just interesting, but things really started taking off with the arrival of the original Droid on Verizon. For Google and its partners to push more adoption, I am not sure if the saturation tactic that was has worked in the smartphone market is going to work for tablets. I think general consumers will be compelled by more content. Android has a great hook with its one-source approach to aggregating access to all content mediums via your single Google account. But they need a better library in Google books, a music source for procuring music (Blast it! I drafted this before the Google Music launch), and further integration with Google TV. It would be a huge plus if I could be watching an episode of a show on my tablet, and then have my stopping place synced with a GoogleTV device to continue watching the content from the same place… and for there to be worthwhile, current TV content.
  • Chippy: In terms of tablets there really is only an iPad market at the moment. Android tablets remain a niche, rather geeky option. The reason has nothing to do with hardware design or OS, it’s to do with the apps. There simply aren’t enough devices out there to justify any serious large-screen/fragments-enabled quality developement work. By my estimate there are between 10 and 15 million Android tablet devices out there. Some 5″, some 7″ and some 10″ devices, some running Android 2.x and some 3.x. The effort required to make a quality app across this fragmented product base is too big for the potential returns. For this to change, the number of fragments-enabled devices out there needs to grow considerably. ICS will help slowly during 2012 but for Android to stimulate major development work, soon, it needs a breakthrough product. The Kindle Fire could have been that product but with its 2.x OS it won’t stimulate the important use of fragments. 2012 looks like another difficult year for Android tablet apps.

The pundits also say that fragmentation of the Android OS is a key detractor from the product category gaining ground, not only in the tablet market but across smartphones as well. How do you define fragmentation, or do you feel it does not really exist? There is also a discussion of ecosystems and its criticality in the mobile market. How do you define a mobile ecosystem, or do you think this factor does not exist, or is not as relevant as some suggest.

  • Ben: “Fragmentation” is not an issue inherent to Adroid, but rather a desire of Android device manufacturers. Apple only markets one line of phones and one line of tablets, and at any given time, there is only one model that is considered the flagship device. For Android, any number of phone/tablet makers may have comparable devices, so how can they ‘differenatiate’ (aka fragment) their devices to appeal to customers over their competitor’s devices? The answer often comes in adding custom skins, pre-baking in selected applications and services (some of which may be unique to a given device). This means that the specific experience between tablets is somewhat different. Depending upon the hardware, you might not be able to see the same applications in the Android Market because not all applications are supported on all Android tablet hardware. If a non-techie user buys an Android tablet and enjoys using a specific application that comes with it, they may be surprised to find that when they get a new tablet, that application is not available for it. The only way to avoid this issue is for the user to understand the way this ecosystem works, but that can’t be expected of non-techie users. When it comes to the iPad, you can expect the latest iPad to be capable of running every iPad app (and iPhone app for that matter) that’s ever been made. Furthermore, because all apps are made with the top-end hardware in mind, you can expect any app available to run well if you have the current generation of iPad or iPhone.
  • Damian: I think fragmentation, which I define as multiple hardware manufacturers making different spec’d devices and different implementations of the same OS, is a major factor in consumer uptake of Android tablets, not smartphones. The Android phones need to act as a phone first, then web consumption device, then app using, game playing devices. They usually don’t tend to be used as a consumer of complex media or producer of enterprise content. The phones have different hardware for sure but the manufacturers seem  to be doing a good job of making sure their hardware works in most scenarios, i.e. plays all the media formats it needs to, opens pdf’s and documents when attached to email, renders different websites, etc. The tablet space is more complex and the fragmentation hurts it more. Some devices have full sized USB, some devices have SD card slots, some devices have docks, some devices play all of the video formats and some don’t. This is where the split of the manufacturers seems to hurt most. It’s frustrating when one video plays well on your android phone but not on your tablet. Aren’t they both Android? A website looks great on your Android tablet but when you send the link to anther Android tablet it breaks. Sure you can download a new browser which is one of Android’s strengths but it’s also a hassle. If you see something on one iPad it will work on another iPad – that’s the advantage of controlling the whole ecosystem, both hardware and software.
  • Jerry: I do not think fragmentation exists in the way that I hear a lot of other journalists discuss it. I do not agree that that skinning Android is a form of fragmentation, and the discussion about any difference from the baseline version of Android being fragmentation seems to be a very conservative view. I do not think these perspectives are so close to the reality, and I do not classify mods like HTC Sense or skins like TouchWiz as examples of fragmentation. Where we were as recent as a year ago, there were many new phones being sold that were already whole baselines behind. In other words, tablets and phones were being released with Android 1.6 when Froyo was already out:  that’s an example of fragmentation. More so when those devices were immediately abandoned and never saw updates to a 2.x version of Android, that was also an example of fragmentation. It is the analog to Windows XP laptops being sold when Windows 7 was already out, and then those laptops not supporting  a path forward to Windows 7.  Android is open source, and variety in deployments should be expected, just the same as we expect it with LINUX. Yes, ecosystems are important.  I define ecosystems as a collection of hardware, connectivity, and services, without which, the hardware as a standalone device would offer very little value.  They are obviously important for smartphones, and they are perhaps even more important for tablets. The tablet by itself represents very little functionality. It is only in combination with its network connection, app store or market, and back-end cloud services (email, contacts management, plug-ins to social networks, content availability, and online profiles) that a tablet becomes useful. Amazon’s Kindle Fire has a better fighting chance of being a viable competitor than the Nook Tablet because it brings a kitchen sink of content availability via  its ecosystem and consolidation of that content in one repository channel. The Nook Tablet will have to be configured with several accounts to have access to the same volume of content, and then the content will be available via a spread across multiple channels.
  • Chippy: Fragmentation is a real issue when it comes to developing apps which, in turn, affect the value of the whole Android product range. ICS is the right step, almost a first step, in removing some of the fragmentation but we must not forget that screen sizes, processing capabilities, and sensors all cost development and testing time and are part of the fragmentation problem. ICS development will remain focused on handsets first until the numbers rise significantly. The screen-size/platform fragmentation will remain in the Android ecosystem so Google has to make it as easy as possible to develop. That means fast, quality dev tools and emulators.

What are your current Android devices of choice (tablets and smartphones)? What is your projected next Android acquisition and why? What are your thoughts on Android Tablets as media consumption devices versus their utility for productivity?

  • Ben: I haven’t yet found an Android smartphone or tablet that has quite cut it for me, but I also feel like I have no need for a tablet at the moment, it is too redundant between my smartphone and laptop. It’s quite possible to get done work on tablets, regardless of the platform, but it really comes down to the applications and how well they run on the hardware.
  • Damian: The Asus Eee Pad Transformer with keyboard dock is my current tablet but I am in the market to pick up for an Asus Eee Pad Slider. I don’t need the extra battery life the keyboard dock gives me and I don’t want the extra weight either but I love having the ability to use a full keyboard. What I’d like is a touch screen with a full keyboard when I need it without having to carry around a dock or external keyboard and this is what the Slider gives me. I’m also relatively happy with the build quality and Android implementation that Asus did. The Slider has a full sized USB port – killer feature on a tablet. If you want to provide a level of productivity capability at any volume and have a chance in the enterprise market, manufacturers need to make tablets with a keyboard and possibly a stylus – there I’ve said it start the flames :). I run a Motorola Atrix 4G for business and personal use and it is the best phone I have had to date. I sold an iPhone for the Nokia N900 and the Nokia for the Atrix and I have never looked back. Fantastic hardware coupled with a great implementation of Android and cool, very functional accessories make this a very productive and useful phone. I have yet to defeat the phone with any media format or file type and I credit Motorola with doing a great job of implementing Android and a fantastic out of the box Android experience.
  • Jerry: My current kit includes an HTC Evo 3D as my primary smartphone and a Samsung Nexus S 4G as my secondary, both on Sprint. My tablet kit consists of the Lenovo ThinkPad Tablet 16GB, the Acer Iconia Tab A500 16GB, and the Motorola Xoom 3G. The two phones break even as far as the one of choice. I like the stock Android load on the Nexus, and I prefer the display over the one on the Evo 3D. But I like the Evo for its faster processor and speed, and the availability of the 3D camera. Amongst the tablets, while I like them all, my ThinkPad is the device I carry with me every day and I love the utility of digital inking on it over using a capacitive stylus with the Xoom or Iconia. When I originally drafted this, I thought my next acquisition was going to be a Samsung Galaxy Tab 8.9. I mainly wanted it to replace my iPad, which recently died, with  a smaller form-factor option for increased portability. Instead I grabbed a Kindle Fire. It is a lot easier to grab and carry than some of my 10″ devices. I have access to the right amount of my cloud services and content that it makes sense for me to grab it as I head out the door probably about 50% of the time. My initial hour after waking in the AM is spent using the Kindle Fire to read content, communicate with friends, colleagues, and co-workers, and plan out events for the day.
  • Chippy: 15 minutes before writing this sentence I was given an iPad 2. Let’s see what happens in the following weeks but I’m currently writing this text on the Galaxy Tab 7 and I suspect that my mobile productivity will remain in this 7″ space due to size and ease of thumb-typing. Currently that means an Android-based solution. I don’t use an Android phone because of short battery life and poor cameras. Yes, I was locked-in by a test of a Nokia N8 which I still think is a fantastic cam/phone. I’m currently looking at the Galaxy Tab 7 Plus and Galaxy Tab 7.7 as a future upgrade possibility but I may wait for proven Ice Cream Sandwich products first as, to be honest, the Galaxy Tab 7 is still working well for me as a productivity, media consumption, reading and social networking device, despite still running a 2.x build of Android.

Nokia: More Relevant in the US Than Ever (Maybe)

Tags: , , , , , , , , , , , , , , ,


Nokia has only been relevant for me once in my smartphone life, and that was when I was overseas. Since returning stateside, I have not given Nokia news more than a miniscule glance as I pore over the day’s tech reports. In fact, I have not honestly cared about a Nokia phone release since the mid-90s, when they were one of the top name brands in the US. Until this year that is. Nokia has become relevant again, although not quite in the way that you might think. And while their partnership with Microsoft may be doing a little-bit to correct their sky-diving financial position, I question whether Redmond is doing the best thing overall for increased adoption of Windows Phone.

Before we continue on with the editorial, let’s hit some of the facts of the last week’s announcements. At Nokia World 2011, Nokia introduced two phones that are expected to eventually make their way to US carriers. They are the Nokia Lumia 800 and 710. The latter has a 3.7 inch display with a resolution of 480×800, a 5MP camera that can shoot 720p video, weighs in at 4.4 ounces, has 8GB of flash storage, 512MB of RAM, runs on the Qualcomm MSM8255 chip, which is a 1.4GHz single-core CPU, and communicates on GSM bands.

The Lumia 800 also has a 3.7 inch display, a high resolution 8MP camera, weighs in at 5 ounces, has the same 480×800 resolution on an AMOLED display with Gorilla Glass, 16GB of storage and 512MB of RAM, and an identical processor…in fact, much between the two phones is identical.

Back to the editorial. There are a few things I see as positive about Nokia-Soft’s announcements. Kudos to them for getting the product out on time. We did not need another smartphone-delay storyline to track across months of PR apologies. And the big thing? People are talking about Nokia again, and not only in negative terms. At least not entirely.

Nokia needed to hit one of the park last week at Nokia World, but there are a few areas where these announcements fall well short of that. The announcement of these two phones, to me, is more like a “we’re still hanging in there inch level of effort. It feels very analogous to the Palm Pre release, which offered some compelling potential. But from the announcement of the Pre through the first several months up to release, I felt like I was watching a once great boxer taking jabs in the ring, wobbling, unable to put his hands up and protect himself, but still able to remain standing and even dodging a jab from time to time. But I knew that the other guy was eventually going to land a haymaker that the former champ would just not be able to take.

I get the same sense from the Nokia announcements last week. Maybe the better analogy would be watching a once great boxer through the last few bouts of their career. They keep losing, but in each bout there is a round or a few moments when you think they are on the road back, before they finally succumb each time. While the Lumia product line shows promise, and seems to offer a steady, work-horse level device, neither of the two devices are game-changers. Nokia is in the same position that Android tablet-makers are. They cannot afford to bring a device or devices that are within arm’s reach of the current benchmark products, and offer them at the same price. While there is no pricing information on either of the Lumia devices, I cannot see them being offered at less than $199 and $149 price points for the 800 and the 710 respectively. I believe this based on the pricing of Nokia’s handsets in the past within North America, and the fact that, for some reason, they have struggled to land on carriers with subsidized prices. The Nokia Astound debuted back in April on T-Mobile at one of the most affordable release prices for a Nokia smartphone in North America ever — $79.99. But I do not see Nokia being able to match that pricing for either one of these phones. If they come out at or near the same $199 price point as many premium Android handsets or the $199 iPhone 4S model, when the Nokia phones do not have front-facing cameras or equally high resolution screens, their ability to compete will be sorely lacking.

If Nokia can get the Lumia 710 down to a $99 price point, and slug it out against low-end Android phones, then maybe this maneuver has a chance of gaining traction. As for the Lumia 800, I expect it to come out at $199, and likely on T-Mobile as I do not see AT&T having a lot of interest in this device. So it will go to the smallest of the big four US carriers. But it will also be on the one carrier that does not have the iPhone, so for its current customers who enter the market for a new phone, it could very well be a viable choice. I was on an HTC HD7 on T-Mobile at the beginning of the year and was very happy with that selection. But right now, the only thing Microsoft seems to be touting as the differentiating, breakout feature of Windows Phone is Xbox Live integration [ed. note: that integration is majorly lacking and painfully bolted-on]. This was a nice hook at the beginning of the year, but the Xbox is six years old now, and even as a gaming platform, its pre-eminence as being a new place to go is not as shiny as it once was. As for hardware, Nokia phones have always been appealing to photo buffs for their excellent cameras. But great photos and Xbox Live are not enough to bring Nokia back to relevance in the US.

Overall, this does not feel like the mass offensive that it needed to be. Nothing out of this announcement was anything that was not entirely predictable. At the end of the day, it feels like less than what Nokia needed to do to right its burning platform. These are not devices that will save Nokia’s bacon. Nor is it indicative of a strategy that shows a glimmer of things to come that will make sweeping changes in Nokia’s business position within the market. Nokia seems to have generated much more buzz about their one-off Meego phone, the Nokia N9, than their just-announced Lumina series (though it may still be too early to call).

While falling short of what is needed, I also felt like Microsoft and Nokia weakened Microsoft’s position with its other hardware partners. If I were HTC or Samsung, I would have had sharp words the following day over the use of statements that proclaimed the Lumia line as the “first real Windows Phone(s)”. The hardware manufacturers that stepped out with Microsoft for the launch of Windows Phone, at very high risk to their own earnings, should not have suffered the suggestion that their efforts and their hardware designs were of little value. While not all CEO’s make decisions out of spite, I think the Microsoft and Nokia statements would have at least caused me to ask my CFO for the most recent accounting statements on my Windows Phone product line to evaluate how much value-adding it was really providing.

Microsoft took a risk when it migrated its smartphone strategy away from an Enterprise-focus to a consumer-centric one. Without the old corporate in-roads to lean on, they now have to compete in the same arena with the same rule-set as the iPhone and Android products. I do not see the Lumia has being a huge crowbar in that battle. I like Windows Phone, and would not have a problem selecting it as one my next devices. But I still do not see the operating system, the ecosystem, or the new Nokia devices as converging recommendations that I would give to non-techy customers looking for advice on their next smartphone, or first-time smartphone buyers. It is not clear to me where Microsoft and Nokia are heading in terms of starting an offensive that will lead to all of this increased market-share that so many analysts are claiming Windows Phone will achieve in 2014/2015.

The Lumia devices appear to be beautiful hardware, and I thoroughly enjoy Windows Phone 7 when I use it. But this is about what Microsoft and Nokia are doing to convince the consumer population that is not already on their side that the Nokia devices are viable and competitive alternatives to the iPhone and premium Android devices. Based on last week’s event, I am having a hard time convincing myself that the two companies have done enough. This smells very much like the Palm Pre launch (except for fact that Nokia’s phones appear to be arriving on time as promised). Microsoft and Nokia will need to come in at lower price points than the competition, and quickly get to offering compelling, differentiated features and offer unique service partnerships to compete against Apple and Google. Seeing as how it appears that they have missed those targets within this window of opportunity, I am not sure when they can pull this trifecta off before suffering that aforementioned haymaker that could be in the works. An iPhone 5 announcement in the spring, or arrival en masse of Ice Cream Sandwich phones could quickly push Nokia off the stage of relevance if they and Microsoft cannot push some major offensive in the interim. Oh, yeah, and after scoffing at everyone else’s Windows Phone devices, I would not expect help to arrive from the camps of HTC and Samsung anytime soon.

Search UMPCPortal

UMPCPortal Top 10

Viliv S5
4.8" Intel Atom (Silverthorne)
Acer Aspire E11 ES1
11.6" Intel Celeron N2840
Acer Aspire Switch 10
10.1" Intel Atom Z3745
Toshiba Portege Z930
13.3" Intel Core i5 3427U
HP Elitebook 820 G2
12.5" Intel Core i5 5300U
Toshiba Portege Z830
13.3" Intel Core i5 2467M
Lenovo Ideapad Flex 10
10.1" Intel Celeron N2806
Archos 9
9.0" Intel Atom Z510
Intel NUC Bean Canyon
0.0" Intel Core i7 8559U
Dell Latitude 11 3150
11.6" Intel Pentium N3530