dw2

14 January 2009

Robert Scoble and the fallacy of uniqueness

Filed under: innovation, Nokia, operators, Qt — David Wood @ 11:58 pm

I was surprised to see esteemed blogger Robert Scoble fall into a weird reality distortion field in his recent piece, “Smartphone competition: It’s too late for Nokia and Microsoft, but not too late for Palm in USA“.

Here’s the core of his argument:

…in the USA there are only these major carriers: AT&T, Verizon, Sprint, T-Mobile.

  • AT&T? Gone. Apple has them sewn up.
  • Verizon? RIM has them sewn up. I met with RIM’s director of marketing at CES and he was smiling. That should give you a hint.
  • Sprint? Palm has them in the Palm of their hands now.
  • T-Mobile? Google’s Android is their key smart phone.

So, what does this mean? All the US carriers now have their SmartPhone choices. All the trains have left the station.

Who is out in this game? Microsoft and Nokia.

This argument depends on the fallacious idea that each major network operator can be “sewn up” by just one provider of smartphones – that there will be one uniquely preferred smartphone platform per network operator – and that this choice is already set in stone.

It’s true that almost all major network operators, worldwide, have expressed a desire to reduce the number of smartphone platforms that they have to support. The reason for this reduction is to avoid lots of effort being duplicated across different platforms.

However:

  1. Most major network operators are aiming at a number of supported smartphone platforms that, while small, is greater than one;
  2. One reason for supporting more than one platform is to benefit from an important element of competition – this is particularly relevant while so many smartphone platforms are either relatively new, immature, or going through a significant transition;
  3. Another reason for supporting more than one platform is that end users on the network frequently want a choice;
  4. Even if a carrier decides not to actively support a given smartphone platform – in the sense of becoming involved in customising phones from that platform to take advantage of specific network features – they often allow phones from that platform to run on their network.

Scoble also dismisses the prospects for future Nokia products:

I’ve seen the new Nokia OS, just a month ago. They don’t have it.

This judgement seems highly premature to me. It also seems that AT&T, for one, maintain an interest in shipping Nokia phones. Witness, for example, the AT&T-branded user’s manual for the Nokia E71.

More fundamentally, there’s much more to the future of Nokia than just one initiative (“the new Nokia OS”). There’s a whole raft of new initiatives coming. Some will come to light through forthcoming releases of the Symbian Platform. Others will reach the market in many other ways.

Nokia’s announcement today of an additional licence for the Qt Platform, in order to strengthen developer interest and participation in that platform, is just one example. To quote Sebastian Nyström, Vice President, Qt Software, Nokia:

Broader use of Qt by even more leading companies will result in valuable feedback and increased contributions, ensuring that Qt remains the best-in-class, cross-platform UI and application framework. The accelerated development of Qt will allow developers, including Nokia, to deliver better devices and applications, reduce time to market and enable a wider deployment base for their solutions.

In short, there are plenty more trains to come.

15 December 2008

Accelerating out of molasses

Filed under: disruption, modularity, Nokia, time to market — David Wood @ 4:00 pm

Michael Mace has posted a characteristically thoughtful article on his Mobile Opportunity blog:

Every time I think about Nokia and Symbian, I can’t help picturing a man knee-deep in molasses, running as fast as he can. He’s working up a sweat, thrashing and stumbling forward, and proudly points out that for someone knee-deep in molasses he’s making really good time…

The posting is entitled “Nokia: Running in molasses“. It arose from Mike reflecting on some of what he heard at the recent Symbian Partner Event (SPE) in San Francisco. The posting is well worth reading. I appreciate the issues that Mike raises. These issues are significant. But as you might expect, I have a somewhat different perspective on some of them.

Large software doesn’t mean that software development has to go slow

Charles Davies, Symbian CTO, pointed out to us that Symbian OS has about 450,000 source files. That’s right, half a million files. They’re organized into 85 “packages”…

There are economies of scale as well as dis-economies of scale. The point of the careful division of the Symbian Platform software into packages is to enable each of the resulting packages to have greater autonomy – and, therefore, to progress more quickly.

There’s one subtle point here. Many of the packages include teams from both Symbian and from S60. This applies to cases where the separation of functionality between the two formerly distinct companies resulted in sub-optimal development. Now that Nokia’s acquisition of Symbian has completed, these boundaries can be intelligently re-designed.

Disruption, size, and organisational design

This brings me to a comment on the ideas of Clayton Christensen. Here’s another extract from Mike Mace’s article:

If the folks at Nokia really think they are well positioned to crush Apple, they need to go re-read The Innovator’s Dilemma. Being big is not a benefit in a rapidly-changing market with emerging segments.

Agreed, being big is no guarantee of being able to respond well to changing market conditions. That’s why I’m personally a big fan of Agile. Agile can help established companies (whether large or small) to launch and embrace disruptions. As Scott Anthony, one of Christensen’s co-authors, has recently commented in his article “Can Established Companies Disrupt?“:

The data suggests that it is increasingly common for an established company to launch disruptive innovations. More and more incumbents are learning how to embrace disruptive principles such as:

  • Put the customer, and their important, unsatisfied job-to-be-done at the center of the innovation equation
  • Embrace the power of simplicity, convenience, and affordability
  • Create organizational space for disruptive growth businesses
  • Consider innovation levers beyond features and functions
  • Become world class at testing, iterating and adjusting

As I said, being big can have its advantages as well as its disadvantages, so long as individual parts of the company have sufficient autonomy. The hard part is knowing when to seek closer ties, and when to seek looser ties. One of Christensen’s later books had some very interesting advice on that score. I can’t remember for sure whether that book was “The Innovator’s Solution” or “Seeing What’s Next“. The advice was that where performance remains a critical differentiator, you should look for a tight coupling. Where performance is already “good enough”, you should seek a loose coupling – with open APIs and a choice of alternative solutions.

As soon as I read these words, some time around 2003-2004, I had a gut reaction that, one day, the relevant teams in Symbian software engineering and S60 software engineering ought to be combined. It took a long time for that insight to be fulfilled. But now that it’s happening, there’s plenty of good reason to expect the resulting combined company to start accelerating its development.

Development in parallel with change

Back to Mike Mace, commenting on the SPE presentation by Charles Davies:

Davies talked about the substantial challenges involved in open sourcing a code base that large. He said it will take up to another two years before all of the code is released under the Eclipse license. In the meantime, a majority of the code on launch day of the foundation will be in a more restrictive license that requires registration and a payment of $1,500 for access. There’s also a small amount of third party copyrighted code within Symbian, and the foundation is trying to either get the rights to that code, or figure a way to make it available in binary format.

Those are all typical problems when a project is moving to open source, and the upshot of them is that Symbian won’t be able to get the full benefits of its move to open source until quite a while after the foundation is launched. What slows the process down is the amount of code that Symbian and Nokia have to move. I believe that Symbian OS is probably the largest software project ever taken from closed to open source. If you’ve ever dealt with moving code to open source, you’ll know how staggeringly complex the legal reviews are. What Nokia and Symbian are doing is heroic, scary, and incredibly tedious. It’s like, well, running in molasses.

I have four comments on this:

  1. Even though the full transition to open source may take up to two years from the initial announcement of the foundation (that is, until mid 2010), there are plenty of other things happening in the meantime – with a series of interim releases that progressively convert more of the software from the community-source Symbian Foundation Licence to the open-source Ecliplse Public Licence;
  2. There will be new technologies and new UI features in these interim releases;
  3. The interim releases should already achieve at least some of the considerable benefits of both open source and community source; the first packages which will become available under the EPL are being chosen so that independent developers can do useful things with some of them (including contributing back working code enhancements);
  4. The legal reviews may initially seem daunting, but with the help of modern code-scanning tools and with the advantage of “practice makes perfect”, the process is likely to speed up considerably along the way.

Cool stuff in the lab

Mike ends the main part of his article as follows:

Nokia still has a lot of time to get it right. But do they really understand what needs to change? I can’t tell, because all I usually get from them is monologues on how big their business is and how much cool stuff they have in the lab.

I accept that analysts must inevitably hedge their bets, regarding the extent of future success of the main mobile operating systems, until a period of proving over the next 12-24 months has shown what these operating systems can actually accomplish. I eagerly look forward to the day when more of the Symbian and Nokia roadmap of stunning new technology, new services, and new user experience attains greater visibility. When that happens, analysts are likely to come down off the hedge.

My own expectation is that the moves to integrate Symbian and Nokia, and to create the Symbian Foundation, will see a substantial speed up of innovation over that time period. But I’m not taking this for granted. After all, I’m well aware of the original subtitle of “The Innovator’s Dilemma”: “When new technologies cause great firms to fail“.

5 December 2008

All Carbide C++ editions are now free of charge

Filed under: Carbide, developer experience, Nokia — David Wood @ 2:35 pm

One of the persistent “niggle points” with Symbian OS C++ development has been that developers had to pay significant amounts of money to purchase those features of the Carbide integrated developer environment (IDE) which provided some highly desired functionality such as on-target debugging.

So there’s great news today: Carbide v2 now has ZERO licence fee for all editions:

Carbide.c++ 2.0 is now available with support for the latest technologies based on Symbian OS, such as S60 5th Edition and the Qt platform, and it offers significant improvements throughout.

In addition to the technical improvements, Carbide.c++ 2.0 is now available free of charge.

This has already been picked up by various bloggers, including Lucian Tomuta – Carbide.c++ – new and free (yes, like in “free beer”) – and Simon Judge – Carbide.c++ 2.0 Free of Charge.

The cost reduction isn’t the only piece of good news about this new version. As the Carbide product pages emphasise:

Improvements throughout Carbide.c++ have been designed to make developing Symbian OS C/C++ applications quicker and easier. These improvements include speed and accuracy in code completion, faster response in the Performance Investigator reporting tools, and new connection management for on-device debugging.

This news deserves to run and run.

3 December 2008

Accelerating the transformation

Filed under: China, Nokia, partners — David Wood @ 9:59 am

As noted by Tom Krazit of CNET News, there was lots more news from yesterday’s Nokia World event than merely the buzz about the newly announced highly attractive N97. It was also announced that the acquisition of Symbian by Nokia has completed.

One practical impact of the completion of this deal is that preparation can now accelerate – for the forthcoming Symbian Foundation, and for the deep integration of the Symbian and S60 software engineering teams.

As Tom Krazit notes:

After entertaining the world press in Barcelona during the early part of this week, Symbian and Nokia executives will be in San Francisco later this week to discuss their plans for mobile computing and open source, and we’ll have reports from the Symbian Partner Event on Thursday.

Personally, I’m about to board my flight to San Francisco for this event. I’m particularly looking forward to open and insightful discussion at this event – including the panel discussion on “Succeeding in the US: the key factors“, where I’ll be asking for comments and questions from the audience.

Just as I expect very significant amounts of wireless innovation to come from North America in the near future, I also expect very significant amounts to come, perhaps more in the future, from China. Later this month I’ll be speaking at an event in Beijing, about “Symbian Platform Development“. I’m looking forward to learning a lot – since I plan on listening as well as speaking 🙂

In case anyone would like to try to meet up while I’m in San Francisco or in Beijing, please get in touch.

Footnote: There’s still time to register for the Partner Event.

24 August 2008

Market share is no comfort

Filed under: disruption, innovation, iPhone, Nokia — David Wood @ 9:55 am

In the discussion of whether Symbian and Nokia are fundamentally threatened (or even “irrelevant”) in the face of the huge market buzz around the Apple iPhone, I take no comfort in the fact that Symbian’s share of the global smartphone market is an order of magnitude larger than that of the iPhone. Therefore I disagree with those replies to my previous blog post that highlighted Symbian’s very considerable market share lead, worldwide (but admittedly not in the USA), over the iPhone.

At first sight, strong market leadership should count for a lot. It should trigger a virtuous cycle effect. More phones should attract more developers (who are interested in their apps running on large numbers of phones) which should result in more software tailored to that platform, which should in turn increase the attractiveness of these phones to end users. And that should result in even more phones being sold, and so on – virtuous cycle.

And in reality, a powerful virtuous cycle effect does exist. An experienced and sophisticated ecosystem (“ES”) has grown up around the Symbian operating system (“OS”) and is continuously adding more value to this platform. The OS-ES virtuous cycle does work. However, it’s not invulnerable.

The history of the technology industry is full of examples of companies who were in similar leadership positions to that currently held by Symbian, but whose markets were transformed by disruptive new entrants. Harvard Business School professor Clayton Christensen is deservedly applauded for his description and analysis of how market disruption takes place:

  • Celebrated examples include how the leading providers of mini-computers, such as DEC, Data General, Wang, Nixdorf, and Prime, failed to appreciate the significance of the initially small market that grew up around fledgling personal computers. These manufacturers saw little profit in that market. But when PC technology improved and the surrounding ecosystem matured, it was too late for these erstwhile computing giants to take leading roles in the new industry (despite lots of effort which they eventually but unsuccessfully expended on that new cause).
  • An earlier example, also told by Christensen (in “Seeing what’s next: using theories of innovation to predict industry change“), concerns the disruption caused by the invention of the telephone to the communications industry of that era (1870s): market leader Western Union evaluated the new technology created by Alexander Graham Bell, but concluded it lacked the power to handle the long-range business communications from which the company made most of its profits. Again, technology improved and new business relationships formed, faster than Western Union could respond – with Western Union being plunged into decline as a result.

And there’s more. MIT professor James Utterback elegantly recounts many intriguing and salutary examples in his book “Mastering the dynamics of innovation: How Companies Can Seize Opportunities in the Face of Technological Change”. The book shows how familiar technologies such as refrigeration, electrical lighting, and plate glass, were all clear underdogs at the time of their initial market introduction, and faced serious competition from entrenched industrial alliances whose technologies (such as large-scale ice transportation, or gas lighting) themselves appeared to be regularly improving.

Could the iPhone fit into a similar pattern? It might. There are possible futures in which, say, more than half of all phones sold in the world have iPhone technology inside them. I don’t see that as the most likely future – far from it! – but it does have a certain logic to it:

  1. The iPhone is in many ways a simpler product proposition than existing smartphones (just as PCs were simpler than mini-computers). There are considerably fewer applications built into the iPhone than you can find in a standard S60 phone. That relative simplicity means that some feature-focused users will decide not to use the device. But the device taps into a new market that is arguably underserved by previous offerings. This is the very considerable market of users who don’t need every bell and whistle in feature-packed smartphones, but who are ready for a better experience than can be had from ordinary phones.
  2. The iPhone uses physical components that “break the rules” regarding cost: they’re considerably more expensive to manufacture than most other smartphones, and this makes the device more expensive to purchase. However, again, it may be that now is the right time to break this rule: a greater number of users may be willing to bear this additional cost (in view of the additional benefits that buys them).
  3. The iPhone isn’t growing its ecosystem from scratch; it can benefit from a crossover effect from various components that were already in place in Apple’s pre-iPhone product offerings. Principally, the highly-evolved iTunes distribution mechanism plays a big part in ensuring a good end-user experience with the iPhone.
  4. The iPhone has put special emphasis upon a number of usability aspects, including the graphics “wow”, the UI itself, the mobile web browsing experience, and the discovery and installation of new applications. Users have been drawn to these aspects of the device, even though the device lacks other aspects that are present (and well-evolved) in other smartphones.
  5. Despite what some critics have said, these innovations aren’t (all) easy for other companies to copy. The “look” can be mimicked, but the “feel” is the result of countless small design and implementation details, that are anchored in a sophisticated underlying software system.

For another analogy, the iPhone is similar to the initial Palm Pilot devices, which fared much better in the market than earlier attempts at pen-input handheld devices. The Palm Pilot delivered less than these other devices (such as the Apple Newton, the Casio Zoomer, and the General Magic “Magic Cap”) but provided a much more usable experience.

So, let’s evaluate this scenario. Do disruptive new market entrants always succeed in reaching market leadership position? Of course not. Although it is difficult for market leaders to respond to this kind of change of rules in their industry, it’s not impossible.

Here’s one counter-example: Microsoft and the Internet. Initally, it did look as though Netscape was succeeding in building an impregnable position by bringing a compelling new product to market in an area that Microsoft had previously ignored – an Internet browser. But Microsoft managed to turn around the situation, by dint of two measures:

  1. Clear internal recognition, from the highest leadership, of the fundamentally changing market landscape
  2. Swift and effective execution, continued over many years.

I’m loathe to compare Nokia/Symbian to Microsoft, but in this case the comparison has merits.

What’s more, I expect that it will become clear, over the next year or so, just how much the Symbian Foundation is itself changing the rules of the mobile industry – and (crucially) enabling companies who use this software to change the rules even further. If you think the iPhone is innovative, you’re right, but you ain’t seen nothing yet.

19 August 2008

Nokia and the valley iPhone super-fans

Filed under: iPhone, Nokia — David Wood @ 9:47 pm

“Nokia’s Software Problem”, proclaimed an article in Forbes yesterday, that gave voice to excited Silicon Valley adulation over the can’t-do-anything-wrong iPhone.

The article contained a report on a recent roundtable organised by Michael Arrington. Arrington himself is quoted in the article as pronouncing,

“I believe that Nokia and Symbian are irrelevant companies at this point.”

Part of the problem, apparently, is that:

“Nokia sells hundreds of phone models and supports three different operating systems. No two phones work exactly the same way. Simple models like Nokia’s 2610 aren’t compatible with the Symbian software used on Nokia’s best handsets, such as the N95. Applications written for the iPhone, by contrast, will run on every iPhone.”

Now there’s such a thing as being a fan of the iPhone. That’s understandable. Indeed, there are many great features to the iPhone. It’s proved to be an impressive device. What’s much less understandable is when this fanship extends into super-fanship of the type reported in this article, which makes people blind to:

  • the genuine merits of devices from other manufacturers (such as Nokia);
  • the likelihood that these manufacturers will come out with impressive new devices.

(I almost used a less polite word than “super-fanship” here, but hey, let’s try to be objective.)

Let’s get real. Of course there are big differences between different Nokia phones. Nokia supplies phones catering to very wide varieties of taste, usage model, and pocket. It’s no surprise that different software is used to power these different devices. In contrast, up till now, there’s really only one kind of iPhone. That makes it relatively easy for developers to write apps that work on (err) every kind of iPhone. However, the current iPhone isn’t to everyone’s taste. Some people love the big screen form factor, and are happy that there’s no keyboard. Others would definitely prefer different form factors and UI mechanisms. Others again would prefer a far less expensive phone. If/when Apple produce a variety of phones comparable to that produced by Nokia, it will be interesting to see exactly how portable the different applications remain.

I have another reservation about the arguments in the Forbes article. The email capabilities of the N95 are criticised as being less immediately usable than those of the iPhone. However, a fairer comparison in this case would be with those Nokia phones that specialise in email connectivity. (Remember, there is more than one kind of Nokia phone…). The recently released E66 and E71 would be better comparators. (See eg here for one review of the E71.)

It’s true that we can anticipate very interesting times, as forthcoming new Nokia phones reach the market in the months ahead. Naturally there will be impressive new smartphones from several other suppliers too (running both Symbian and non-Symbian operating systems). We can expect new kinds of user interface models, as different manufacturers build and riff on the innovations produced by their competitors – and bring out some totally new ideas of their own. In achieving these new effects, Symbian-powered phones can take advantage of the following features that are missing (so far) from the iPhone stable: Flash, Java, and the new ScreenPlay graphics architecture.

Looking slightly further afield, the new levels of openness enabled by the Symbian Foundation should have the additional benefits of providing new routes to market for Symbian technology, as well as more rapid collaborative development. If that’s a “software problem”, it’s a problem of the most attractive sort!

3 July 2008

Nanoscience and the mobile device: hopes and fears

Filed under: Morph, nanotechnology, Nokia, risks — David Wood @ 10:56 am

Nokia’s concept video of a future morphing mobile phone, released back in February, has apparently already been viewed more than two million times on YouTube. It’s a clever piece of work, simultaneously showing an appealing vision of future mobile devices and giving hints about how the underlying technology could work. No wonder it’s been popular.

So what are the next steps? I see that the office of Nokia’s CTO has now released a 5 page white paper that gives more of the background to the technologies involved, which are collectively known as nanotechnology. It’s available on Bob Iannucci’s blog, and it’s a fine read. Here’s a short extract:

After a blustery decade of hopes and fears (the fountain of youth or a tool for terrorists?), nanotechnology has hit its stride. More than 600 companies claim to use nanotechnologies in products currently on the market. A few interesting examples:

  • Stain-repellant textiles. A finely structured surface of embedded “nanowhiskers” keeps liquids from soaking into clothing—in the same way that some plant leaves keep themselves clean.
  • UV-absorbing sunscreen. Using nanoparticulate zinc oxide or titanium dioxide, these products spread easily and are fully transparent —while absorbing ultraviolet rays to prevent sunburn.
  • Purifying water filters. Aluminum oxide nanofibers with unusual bioadhesive properties are formulated into filters that attract and retain electronegative particles such as bacteria and viruses.
  • Windshield defoggers. A transparent lacquer of carbon nanotubes connects to the vehicle’s electrical source to evenly warm up the entire surface of the glass.

Even more interesting, to my mind, than the explanation of what’s already been accomplished (and what’s likely to be just around the corner), is a set of questions listed in the white paper. (In my view, the quality of someone’s intelligence is often shown more in the quality of the questions they ask than in the quality of the answers they give to questions raised by other people.) Here’s what the white paper says on this score:

As Nokia looks toward the mobile device of 2015 and beyond, our research teams, our partner academic institutions, and other industry innovators are finding answers to the following questions:

  1. What will be the form factors, functionalities, and interaction paradigms preferred by users in the future?
  2. How can the device sense the user’s behavior, physiological state, physical context, and local environment?
  3. How can we integrate energy-efficient sensing, computing, actuation, and communication solutions?
  4. How can we create a library of reliable and durable surface materials that enable a multitude of functions?
  5. How can we develop efficient power solutions that are also lightweight and wearable?
  6. How can we manufacture functional electronics and optics that are transparent and compliant?
  7. How can we move the functionality and intelligence of the device closer to the physical user interface?
  8. As we pursue these questions, how can we assess—and mitigate— possible risks, so that we introduce new technologies in a globally responsible manner?

That’s lots to think about! In response to the final question, one site that has many promising answers is the Center for Responsible Nanotechnology, founded by Mike Treder and Chris Phoenix. As he explains in his recent article “Nano Catastrophes“, Mike’s coming to Oxford later this month to attend a Conference on Global Catastrophic Risks, where he’ll be addressing these issues. I’ll be popping down that weekend to join the conference, and I look forward to reporting back what I find.

This is a topic that’s likely to run and run. Both the potential upsides and the potential downsides of nanotechnology are enormous. It’s well worth lots more serious research.

24 June 2008

Symbian 2-0

Filed under: Nokia, Open Source, Symbian Foundation — David Wood @ 6:13 am

Months of planning culminated this morning with the announcement of an intended dramatic evolution for Symbian – an evolution that should decisively advance the Symbian platform toward its long-anticipated status of being the most widely used software platform on the planet.

The announcement of the Symbian Foundation comes on the very first day of the second decade of Symbian’s existence. It also sets the scene for a much wider participation by companies and individuals in the development and deployment of novel services and applications for all sorts of new and improved Symbian-powered mobile devices. Because this second decade of Symbian’s history should witness radically greater collaboration than before, the designation “Symbian 2.0” seems doubly apt.

Subject to the deal receiving regulatory approval, I envision a whole series of far-reaching changes to take place in the months and years ahead:

  • It will become possible for the best practices of Open Source Software to be applied in and around the software platform that is the most suited to smartphones

  • Closer working relations between personnel from Symbian and S60 teams will result in more efficient development, accelerating the rate at which the overall platform improves

  • The lower barriers to usage of the Symbian platform should mean that the number of customers and partners will rocket

  • The unification of the formerly separate UI systems will further increase the attractiveness of the new platform

  • The platform will be royalty free – which will be another factor to boost usage

  • Because of increased adoption of the platform, the ecosystem will also grow, through the OS-ES volume-value virtuous cycle mechanism

  • For all these reasons, smartphone innovation should jump forward in pace, to the potential benefit of all participants in the ever expanding, ever richer, converged mobile industry
    Customers and partners alike – both newcomers and old-timers – will be on the lookout for fresh options for differentiation and support

  • In short, there will be lots of new opportunities for people with knowledge of the Symbian platform.

Great credit is due to Symbian’s shareholders, and especially to Nokia, for enabling and driving this bold and powerful initiative.

Of course, with such a large change, there’s considerable uncertainty about how everything will work out. Many people will be unsure exactly where they, personally, will end up in this new world. Lots of details remain to be decided. But the basic direction is clear: participants in the Symbian 2.0 ecosystem will be part of a much bigger game than before. It’s going to be exciting – and no doubt somewhat scary too. As Symbian’s first CEO, Colly Myers, used to say, “Let’s rock and roll!”

Postscript: For a clear rationale of some key aspects of the Symbian Foundation plan, take a look at what my Symbian colleague John Forsyth has to say, here.

« Newer Posts

Blog at WordPress.com.