Category Archives: mobile

Farewell to Mobile World Congress at the Fira Montjuïc Barcelona

Mobile World Congress 2012 is over, and while the event will remain in Barcelona next year and for the foreseeable future, this was the last to take place at the Fira Montjuic in the centre of the city. Next year’s event will be at the Fira Gran Via, a modern venue with 240,000 m2 of floor space, four times more space that at Montjuic. 

It is needed; this year’s MWC was over-crowded, with every inch of the site taken up by stands and so many people that it was difficult to get from one hall to another. Nevertheless I am sorry it is moving, since the Fira Montjuic is a romantic venue that pleasantly contrasted the technical content.

image

image

That said, no doubt many unofficial events will still take place in the old part of Barcelona, like Huawei’s Device Night, spotted on the way back from another event. I have no idea why these people are in costume, or what Huawei mobile devices have to do with the Passion of Sailing.

image

Nokia at Mobile World Congress: one year after the Windows Phone shift, how is it doing?

At Mobile World Congress in Barcelona Nokia CEO Stephen Elop reminded the press that this is the anniversary of the company’s big change of direction, when it adopted Windows Phone as its primary smartphone platform.

image

So how is it doing? Nokia’s speed of execution has been impressive. Since that announcement, the Lumia range has been introduced around the world; we were told today that it is on the way to China. The large screen Lumia 900 with LTE support has been launched in the USA and is coming to other territories, the next being Canada.

Nokia is also continuing to launch new Symbian devices. Today we heard about the Asha 202 and 203 which have touch screens as well as keypads, and the Asha 302 which includes an app-capable browser and support for Microsoft Exchange, pushing at SmartPhone boundaries but at a lower price.

Perhaps the most interesting announcement today though was that Microsoft is lowering the minimum hardware requirements for Windows Phone 7 – a surprising move given that technology advances are already making the existing requirements less expensive. The new, lower bar is 256MB RAM and a slower processor. This enables Nokia to launch the Lumia 610 at 189 Euro.

image

One of the intriguing questions: as Lumias fall in price, what is the future of Symbian at Nokia? The question was asked at the end of the press conference but not answered.

To add to the confusion, Nokia announced the Symbian-based 808 Pure View with a 41 megapixel sensor and “CD quality” recording. Apparently it is Symbian because it was developed before the Windows switch.

Nokia is betting on location-based services and announced improvements to Nokia Drive (full offline support) as well as Nokia Transport, for local bus and tram services.

Is Nokia’s Windows adventure working out? That is the question, and remains a wait and see, though my judgment based on the first year is that it remains in the game. In a sea of Android here at Mobile World Congress it does at least have something distinctive to offer.

Imperfect Samsung Slate 7 tablet shows challenge facing Windows 8

I took advantage of a trip to Seattle to purchase a Samsung 7 Slate, similar to the one given to attendees at Microsoft’s BUILD conference last September, though missing some of its sensors.

image

It is a decent machine, fast and well-specified, but not one I can recommend unless, like me, you are keen to give Windows 8 Consumer Preview the best chance to impress, and cannot wait the short interval until machines that are actually designed for Windows 8 turn up on the market.

This is a Windows 7 slate, and that is the main thing that is wrong with it, since Windows 7 does not work well with touch control. Samsung’s solution is to cover all the bases:

  • A stylus is supplied so you can use pen control as with earlier Windows tablets
  • There is a matching Bluetooth keyboard
  • Samsung has created its own touch-friendly desktop with a selection of apps, so that you can avoid the classic Windows desktop

image

All these options make this an expensive device, but there are nevertheless a number of flaws and annoyances, some of which make you wonder “what were they thinking?” Here are some I have discovered in a few days of use:

1. There is an illumination sensor towards the top right of the screen bezel. This is a battery-saving measure, which adjusts the screen brightness according to the ambient light. Good thinking; except that if you are right-handed and controlling the slate with touch, your hand will often pass in front of the sensor. When that happens the screen dims, because it thinks the room is darker. The effect is that the screen constantly brightens and darkens in use, which is unpleasant. Fix: disable the feature and set the screen to a fixed brightness.

2. The on-screen keyboard is poor. This is the fault of Microsoft, not Samsung. If you have the keyboard set to float, the keys are too close together for fast typing. If you dock the keyboard, it becomes bigger, but impossible to use because it covers the bottom third of the screen. For example, it covers the search box on the Start menu when docked, so that you will be typing into it blind. Fix: Windows 8.

3. I got the matching Samsung wireless keyboard and found that the first key you press sometimes does not register. This is infuriating, especially for things like passwords. The reason, I discovered, is a setting in the Bluetooth card configuration “Allow the computer to turn off the device to save power.” When set, if you pause typing for 30 seconds, then the next key you press is in effect the on button and does not appear on the screen. Fix: uncheck this setting.

image

4. When using wifi at a meeting, I found that every two or three minutes I had to re-enter the username and password for the wifi hotspot. Nobody else had this problem. Fix: I am not sure, but updating the driver for the Intel wireless adapter plus sundry other Windows updates fixed it for me.

5. It is difficult to run without full administrator rights on the machine, as several Samsung utilities prompt for elevation.

6. There is no security button. This is the button that emulates Ctrl-Alt-Delete when you log on to Windows. Instead, you hold down the Windows key and press the power on switch – when you have discovered that this is what you have to do. It is not mentioned in the quick start leaflets. To be fair, this is only likely to be an issue if you do as I did and join the machine to a Windows domain. Samsung does include a Touch Logon application which lets you secure your machine with a simple code instead.

7. The pen sometimes stops working, or more precisely, the screen stops responding to the pen. Fix: pressing the screen rotation lock button seems to kick it back into life.

8. There is some clever coding that disables finger control when you are using the pen, which is a Wacom digitiser and not just a stylus. The idea is that you can rest your hand on the screen when using the pen. This mostly works, but I still find pen control less good on this device than on older Tablet PCs which respond only to the digitiser. The problem may be that when you lift the pen away from the screen, touch control turns back on. Whether or not this is the problem, I find it too easy to get unexpected behaviour.

9. Navigating the BIOS is difficult without a USB keyboard. It can be done. Volume up and down substitutes for the cursor keys, the Windows button is ESC and the rotation lock is Enter. The hard bit: switching between pages with volume and rotation button together. Fix: a USB keyboard.

10. The one solitary USB port has a tiny loose plastic cover which will soon get lost. For that matter, I will probably lose the expensive digitizer pen as well since it does not clip into the slate nor into the official Samsung case.

Is this a poor device then? Not at all. It is powerful and light, and works very well indeed if you pop the slate into its dock and use it with a wireless keyboard and mouse. In this guise though, it is more like a desktop PC.

When used purely as a slate though, this machine is far less usable than either an iPad or an Android tablet, both of which are also much cheaper.

Even some of the good ideas do not quite work properly. If you tap with three fingers, a floating panel appears with common actions that are otherwise tricky with touch, such as Ctrl-C for Copy. A great use of multitouch, except that if I do this in Windows Live Writer, it also registers as a zoom command which enlarges the text. Annoying.

image

All this is thought-provoking on the eve of the Windows 8 beta launch. Windows 8 in metro mode fixes the usability problems in the operating system, but will not prevent OEMs implementing half-baked ideas like Samsung’s illumination sensor. Further, people will buy Windows 8 tablets in part so that they can run desktop applications. How well will that work without docks, keyboards, pens and/or wireless mice, and high prices?

That said, Microsoft is aware of these issues which is why the Metro side of Windows 8 exists. The goal, I imagine, is that you will be able to stay in Metro all the time when using Windows 8 as a slate.

Tablets will be bigger than PCs. Are you ready?

Apple’s CEO Tim Cook spoke at the Goldman Sachs Technology Conference yesterday; Macrumors has what looks like a full transcript. Do not expect hot news; there is little or nothing in the way of announcements. It is interesting though as a recap of how Apple sees its future: iPad, iPhone, iCloud, Apple TV, maybe some future huge acquisition financed by its cash pile.

This is what stands out for me:

From the first day it shipped, we thought that the tablet market would become larger than the PC market and it was just a matter of the time it took for that to occur. I feel that stronger today than I did then.

I agree. The reasons are similar to those that caused laptops to outpace desktops. Mobility and convenience trump the better computing value you get in a desktop PC. Note: we still use desktops, and both desktops and laptops will continue to sell, but in smaller quantity.

Although you can list numerous reasons why tablets are not good enough – no keyboard, small storage capacity, underpowered for cutting-edge gaming, not really expandable, favourite apps not yet available, and more – none of these is sufficient to prevent the tablet taking over in the majority of cases.

You can have a keyboard if you want; build it into the case. Storage is increasing all the time, and we have the cloud. Graphics power is increasing all the time. Most people are happy to sacrifice expandability for the simplicity and reliability of a tablet. If your favourite app is not yet available, it soon will be; or else an equivalent will appear that replaces it.

Tablet benefits? Cost, no flappy screen, light and small, designed for ease of use, reliability of an appliance versus a computer for starters.

In itself, the move from one type of computing device to another is no big deal. The reason this one is such a deep change is because of other factors. I will list three:

  • The lock down

    Pioneered by Apple, this is the idea that users should not have full access to the operating system on their device in almost any circumstances. The lock down is a cost and a benefit. The benefit: resilience against malware, greater reliability. The cost: loss of control, loss of freedom, handing over even more power to those who do have full access, primarily the operating system vendor. Where UEFI secure boot is enabled, it is not even possible to boot to an alternative operating system.

  • The store

    Hand in hand with the lock down is the store, the notion that apps can only be installed through the operating system vendor’s store. This is not a universal tablet feature. Apple’s iPad has it, Microsoft’s forthcoming Windows 8 on ARM has it, Android devices generally let you enable “unknown sources” in order to install apps via a downloaded package, though sometimes this option is missing. Further, both Apple and Microsoft have schemes whereby corporates can install private apps. Still, the consequence of the lock down is that the ability to install apps freely is something which can be tuned either way. Since store owners take a cut of all the business, they have have a strong incentive to drive business their way.

    I have never believed Apple’s line that the iTunes store is intended as a break-even project for the convenience of its hardware customers.

  • The operating system

    I am at risk of stating the obvious, but the fact that most tablets are iPads and most non-Apple tablets are Android is a monumental shift from the Windows-dominated world of a few years back. Can Microsoft get back in this game? I am impressed with what I have seen of Windows 8 and it would probably be my tablet of choice if it were available now. The smooth transition it offers between the old PC desktop world and the new tablet world is compelling.

    That said, this cannot be taken for granted. I watched someone set up a new Android tablet recently, and was interested to see how the user was driven to sign up for a variety of services from Google and HTC (it was an HTC Flyer). Devices will be replaced, but accounts and identities are sticky. Users who switch devices may face having to move documents to a different cloud provider if they know how, re-purchase apps, figure out how to move music they have purchased, re-buy DRM content. A big ask, which is why Microsoft’s late start is so costly. At best, it will be a significant player (I think it will be) but not dominant as in the past.

    Late start? Did not Bill Gates wave a slate around and predict that it would be the future of the PC back in 2001:

    "So next year a lot of people in the audience, I hope, will be taking their notes with those Tablet PCs … it’s a PC that is virtually without limits and within five years I predict it will be the most popular form of PC sold in America."

    Right idea, wrong execution. Microsoft tried again with Origami, the ultra mobile PC, a device that was so obviously flawed that everyone knew it would fail. My belief is that Microsoft, helped by Apple’s example, has a tablet concept that works this time round, but nevertheless the history is discouraging.

    One reason for the relative failure of the Tablet PC and the complete failure of Origami was price. Microsoft’s business model depends on selling software licenses, whereas Apple mostly bundles this cost into that of the hardware, and Android is free. Price of the first Windows 8 tablets is unknown, but could again prove to be a problem.

    Interesting to debate; but however it shakes out, Windows-only is not coming back .

It follows that as tablet use continues to grow, both business and consumer computing are transforming into something different from what we have become used to. Considering this fact, it would be interesting to analyse affected businesses in terms of how ready they are for this change. It would be fascinating to see companies ordered by some kind of tablet readiness index, and my guess is that those towards the bottom of that hypothetical list are in for a nasty shock.

image

Compile Object Pascal to JavaScript with Smart Mobile Studio

Here is an interesting project for Delphi developers: a compiler and IDE that takes your Object Pascal code and outputs HTML and JavaScript. 

image

Smart Mobile Studio, also known as OPJS (Object Pascal to JavaScript) is a project from Optimale Systemer AS, and supports not only the Object Pascal language. but also reusable components in true Delphi style. The goal is to bring Object Pascal programming to mobile platforms, using PhoneGap to wrap the generated code as a native application for iOS, Android or other platforms.

According to the developers, “The Smart object pascal dialect is more or less identical to Delphi 7”. That said, there are no pointers, and ASM blocks contain normal JavaScript instead of machine instructions. This enables use of JavaScript libraries such as JQuery from Smart Mobile code:

You can access native JS through an ASM section, create an instance of it to a variant, and then access its methods directly.

Smart Mobile Studio is currently in closed Alpha so not ready for most of us just yet. Note that there are other options for mobile development with Delphi, including Embarcadero’s official FireMonkey project which can be used with the Free Pascal iOS compiler. Embarcadero has promised its own compiler for IOS in a future version, as well as an Android option.

Where are the tablets for Windows 8 Consumer Preview?

Microsoft will deliver Windows 8 Consumer Preview shortly, probably on February 29th, since it has been promised by the end of this month and there is a launch event at Mobile World Congress.

The Windows Consumer Preview, the beta of Windows 8 on x86/64, will be available for download by the end of February. This next milestone of Windows 8 will be available in several languages and is open for anyone to download.

says Windows President Steven Sinofsky

The name of the preview suggests that Microsoft intends this release to be broadly downloaded and tried, in contrast to the developer preview with its more specialised role.

In preparation for the preview I looked around for a suitable tablet on which to test it – noting that it must be a Intel x86 or x64 tablet, since the ARM build (WOA) is not for general release, but only for manufacturers.

WOA will not be available as a software-only distribution, so you never have to worry about which DVD to install and if it will work on a particular PC.

Sinofsky writes.

So what is available? A quick Twitter consultation turned up a few options, such as the Acer Iconia Tab W500, the Asus Eee slate B121, and the Samsung Slate 7.

However, of these only the Samsung is really suitable, because it has a 1366 x 768 display. The others have 1280 x 800, and while this will run Windows 8 and the new Metro user interface, it will not support the Snap feature which gives you two applications on screen together:

The resolution that supports all the features of Windows 8, including multitasking with snap is 1366×768. We chose this resolution as it can fit the width of a snapped app, which is 320px (also the width designed for many phone layouts), next to a main app at 1024×768 app (a common size designed for use on the web).

Yes, it’s Sinofsky again.

Unfortunately the Samsung Slate 7 is not fully released in the UK, though I did find it on offer at ebuyer.com, for the not too unreasonable price of £973.19.

Samsung XE700T1A Series 7 Slate Tablet PC, Intel Core i5-2467 1.6GHz, 4GB RAM, 64GB SSD, 11.6" Touch, Intel HD, Webcam, Bluetooth, Wifi, Windows 7 Home Premium 64

That is still expensive, and it is hard to see it becoming a mass-market bestseller as Windows 8 fans rush to try out the new OS.

The consequence is that most users will try Windows 8 Consumer Preview on a virtual machine, or on an ordinary PC or laptop, or possibly on one of the cheaper 1280 x 800 tablets.

Since Microsoft’s main focus with Windows 8 has been on the new Metro touch user interface, this will not show the new operating system at its best.

I can personally testify to this. The Samsung slate handed out at the BUILD conference last September, which I had on loan for a few days, was delightful to use, whereas Windows 8 Developer Preview (the same build) is nothing special in a virtual machine.

All will be well, one assumes, when Windows 8 launches with both ARM and Intel-based machines available. Nevertheless, it seems to me a significant obstacle as Microsoft tries to build pre-launch enthusiasm; the risk is that users will not take into account how much better it is on a real tablet.

Update: a few other options have been suggested, like the Dell Inspiron Duo, a convertible 10.1” tablet with an Intel Atom  N570 Dual Core, 1366 x 768 display and 2GB RAM, and around one third of the cost of a Slate 7, but perhaps under-powered to show off the best of Windows 8.

What to do when your Nokia Lumia 800 will not turn on?

Nokia Lumia 800: delightful smartphone but with a few irritations. If you have one, I recommend that you do not let the battery fully discharge – a challenge since the battery life is not the greatest – since if you do, you may have problems turning the phone on again.

I am not sure what proportion of Lumias are affected, but what happens is this. The battery runs out and the phone turns itself off as you would expect. You plug it into the charger, but even after several hours it appears to remain uncharged and will not turn on. The problem is discussed in this thread: Lumia 800 won’t power on or charge.

This has happened with my review Lumia. In my case, the phone vibrated when plugged into the charger and the charging screen appeared, with a red line showing an empty battery, and there it stayed.

So what is the fix? I have had the problem a couple of times, and each time it eventually fixed itself, though it is hard to pinpoint the exact fix. Things people have tried:

  • Unplugging and reconnecting the charger to the phone
  • Attaching the phone to a PC, then to a charger
  • Reset the charging cycle by holding down the power button, while charging, for 8 seconds or so
  • Warming the device to create a small charge in the battery, then starting to charge it

One theory is the battery discharges so deeply that there is not enough power to detect the charger, therefore it never charges. Kind-of too smart for its own good.

If the phone had a removable battery, I would suggest removing and replacing it, an old trick to revive a frozen phone. Should your Lumia not be covered by a warranty, you could try disassembly in order to do this.

The best hope is that a further firmware update will fix the problem.

Windows on ARM: Microsoft can write Desktop apps, but you cannot

Microsoft’s Windows chief Steven Sinofsky has written a long post describing Windows on ARM (WOA), which he says is a:

new member of the Windows family, much like Windows Server, Windows Embedded, or Windows Phone

There are many point of interest in the post, but the one which stands out for me is that while the traditional Windows desktop exists in WOA, third party applications will not be allowed there:

Developers with existing code, whether in C, C++, C#, Visual Basic, or JavaScript, are free to incorporate that code into their apps, so long as it targets the WinRT API set for Windows services. The Windows Store can carry, distribute, and service both the ARM and x86/64 implementations of apps (should there be native code in the app requiring two distributions).

says Sinofsky. He writes with extreme care on this issue, since the position for which he argues is finely nuanced. Why have the Windows desktop on WOA at all?

Some have suggested we might remove the desktop from WOA in an effort to be pure, to break from the past, or to be more simplistic or expeditious in our approach. To us, giving up something useful that has little cost to customers was a compromise that we didn’t want to see in the evolution of PCs

he says, while also saying:

WOA (as with Windows 8 ) is designed so that customers focused on Metro style apps don’t need to spend time in the desktop.

From a developer perspective, the desktop is more than just a different Windows shell. Apps that run on the Windows Runtime (WinRT) are isolated from each other and can call only a limited set of “safe” Windows APIs, protecting users from malware and instability, but also constraining their capabilities. The desktop by contrast is the old Windows, an open operating system. On Windows 8 Intel, most things that run on Windows 7 today will still work. On WOA though, even recompilation to target the ARM architecture will not help you, since Microsoft will not let desktops apps install:

Consumers obtain all software, including device drivers, through the Windows Store and Microsoft Update or Windows Update.

What if you really want to use WOA, but have some essential desktop application without which you cannot do your work, and which cannot quickly and easily be ported to WinRT? Microsoft’s answer is that you must use Windows on Intel.

That said, Microsoft itself has this problem in the form of Office, its productivity suite. Microsoft’s answer to itself is to run it on the desktop:

Within the Windows desktop, WOA includes desktop versions of the new Microsoft Word, Excel, PowerPoint, and OneNote, codenamed “Office 15”.

No Outlook, which I take to imply that a new WinRT-based Exchange client and PIM (Personal Information Manager) is on the way – a good thing.

Microsoft’s aim is to give customers the security and stability of a locked-down machine, while still offering a full version of Office. If you think of this as something like an Apple iPad but with no-compromise document editing and creation, then it sounds compelling.

At the same time, some users may be annoyed that the solution Microsoft has adopted for its legacy desktop application suite is not also available to them.

The caveat: it is not clear in Sinofsky’s post whether there may be some exceptions, for example for corporate deployments, or for hardware vendors or mobile operators. It will also be intriguing to see how Office 15 on ARM handles extensibility, for example with Office add-ins or Visual Basic macros. I suspect they will not be supported, but if they are, then that would be a route to a kind of desktop programming on WOA.

It will be interesting to see how Microsoft locks down Explorer, which Sinofksy says is present:

You can use Windows Explorer, for example, to connect to external storage devices, transfer and manage files from a network share, or use multiple displays, and do all of this with or without an attached keyboard and mouse—your choice.

By the way, this is a picture of the Windows ARM desktop as it looked at the BUILD conference last September. The SoC (System on a Chip) on this machine is from NVIDIA.

WebKit dominance threatens mobile web standards – but who will care?

Daniel Glazman, co-chairman of the W3C CSS working group, has written a strongly-worded post describing how the “over-dominance” of the WebKit rendering engine threatens web standards.

Everyone loves the open source WebKit, so how is this so? The issue is a complex one. Those who make web browsers do not want to be tied only to those standards already ratified by the W3C as part of HTML or CSS. Therefore, they add features, sometimes in the hope that they will become standards, but use a vendor-specific prefix such as -webkit-,-moz- or -ms-. If you use those features in your markup, you do so in the awareness that they will only work on that specific vendor’s browser. The idea is that the best vendor-specific extensions become standard, in which case the prefix is dropped; or are replaced by an equivalent standard, in which case the prefix is also dropped. This has become an accepted part of the way standards are formed.

The issue now is that WebKit dominates the mobile web to the extent that web authors can assume its use without losing many users. WebKit is used in Apple iOS, Google Android, RIM BlackBerry 6 and higher, as well as on the desktop in Apple Safari and Google Chrome. Amazon also uses WebKit in the Kindle and of course the Android-based Kindle Fire.

The consequence, says Glazman, is that:

technically, the mobile Web is full of works-only-in-WebKit web sites while other browsers and their users are crying.

The further consequence, and this is Glazman’s strongest point, is that other browsers will have to pretend to be WebKit and support its extensions in order to give users a good experience – even if they have their own vendor-specific extensions that support the same features:

All browser vendors let us officially know it WILL happen, and rather sooner than later because they have, I quote, "no other option".

Glazman says “all browser vendors” which suggests that even Microsoft will do this, though that would be a surprising development.

This would mean that the -webkit- vendor-specific extensions were no longer vendor-specific. It would also meant that WebKit is in effect able to create web standards without the bother of going through the W3C:

It will turn a market share into a de facto standard, a single implementation into a world-wide monopoly. Again. It will kill our standardization process. That’s not a question of if, that’s a question of when.

says Glazman, suggesting that there is a risk of a return to the bad days when the dominance Microsoft’s IE6 prevented standards from evolving.

The parallel with IE6 is weak. IE6 was not an open source project, and the damage it did was in part because Microsoft deliberately chose not to invest in advancing HTML, preferring to drive users towards rich internet-connected Windows applications. It is difficult to see how that can happen to WebKit.

Nevertheless, the situation with WebKit is making it difficult for other mobile browsers to compete and does undermine the standards process. This is not really the fault of the WebKit team, though the W3C would like to see support for obsolete vendor-specific extensions dropped more quickly to discourage their use. Rather, it is a consequence of web authors seeing little value in adding support for other browsers that have little actual use on the mobile web.

It is worth observing that Glazman is a Mozilla guy, and his company Disruptive Innovations makes Mozilla extensions.

How can this be resolved? Glazman and others are right to raise awareness of the issue, but I doubt that many outside the standards community or browser vendors themselves will see this as a major problem.

The best fix would be for non-WebKit browsers to become more popular on the mobile web. Growing use of Windows Phone, for example, would give web authors more incentive to fix their markup. Another route to improving standards is via tools which do the right thing. Adobe’s strong support for CSS in Dreamweaver, for example, gave a significant boost to its use and helped to rescue us from font tags and the like.

Finally, it seems to me that the distinction between the “mobile” web and the “full” web is blurring, and rightly so. Users on mobile devices often tap the “full site” link where available since they have big enough screens to benefit. WebKit does not yet dominate the desktop Web. 

On BlackBerry 10, Cascades UI and Adobe AIR

I spoke to Jeff Lejeune, RIM’s Advanced User Interface Director, here at BlackBerry DevCon Europe in Amsterdam.

He is part of the team responsible for the Cascades UI, a native code UI framework for the forthcoming BlackBerry 10 OS. One of the things he told me is that the Cascades name is actually being used for parts of the API beyond the user interface. It is a major part of the new operating system.

I had not appreciated until today the extent of the likely difference between BlackBerry 10 and the current Tablet OS 1.0 or Playbook OS 2.0. Since the PlayBook OS is already based on QNX, I had assumed that BlackBerry 10 would be an incremental update rather than a radical new direction.

Certainly there is less difference between PlayBook OS 2.0 and BlackBerry 10 then there is between BlackBerry 7.0 and the PlayBook OS, so my assumption was not completely wrong. That said, the introduction of the Cascades UI acquired with The Astonishing Tribe is a major change. Lejune told me that Cascades UI will be in effect the native UI of BlackBerry 10, and the built-in apps will use it.

The first version of the PlayBook uses both native code and Adobe AIR for its built-in apps.

RIM has given full backing to Adobe AIR at this event, presenting it as one of the supported development platforms and saying that it will support AIR for as long as Adobe does and maybe even longer. Even so, it would be fair to say that RIM is moving away from AIR and towards native code and Cascades UI in BlackBerry 10.

Further, Adobe itself has changed direction since the launch of the PlayBook last year. Adobe has made it clear that while Flash, Flex and AIR are still important, its strategic direction is HTML 5 when it comes to development platforms. Some aspects of Flex, the code-based approach to AIR authoring, are being wound down, including the visual designer in Flash Builder.

My sense therefore is that AIR is not the best choice if you are considering how to develop for BlackBerry 10 – and BlackBerry 10 is the future of RIM’s platform. The primary choice should be between Cascades UI, for best performance and integration, or WebWorks (PhoneGap), for development in HTML and JavaScript and cross-platform code.