Symbian Blog: Articles by Mark Wilcox

It’s Open, So Now What?

Retweet Share on Facebook

Less than 20 months after the initial announcement of the intention to open source Symbian, the major milestone of getting the source code published under open source licenses has finally been achieved. Now anyone with an interest in the future of mobile can take a look around and maybe even start tinkering.

Although we’ve made it 4 months ahead of schedule, for many of those involved it has been a long hard road. This is an extremely significant step forward but we want to go further. Hopefully we’ve now reached the point where more of you can help build a mature and diverse open source community. Read more »

Why more is not always better – Part II – Megapixels

Retweet Share on Facebook

A hotly contested arms race in the mobile world is the number of megapixels in a phone camera. This has generally tracked the megapixel race in the stand-alone digital still camera market.

The fact that people always carry their phones makes them an extremely popular device for spontaneous photography. Hence, back in 2005, Nokia became the worlds largest digital camera manufacturer.

But how many people use the camera in their phone for serious photography, and what do they do with the images? Print them? Blow them up to a poster size?

Not at all often in either case would be my guess, much less so the poster option.

Conventional wisdom on digital still cameras says that anything above 6 megapixels is comfortably capable of producing a 10″x8″ (large size) print.

Viewed on a TV or monitor, the number of pixels displayed is much lower (around 1-4 megapixels) – and when only viewed on the phone or camera itself, typically around a quarter of a megapixel. Past a certain point, what determines image quality far more than the number of pixels in the sensor is the quality of the optics (i.e. lens) and the image processing algorithms applied to the output from the sensor.

Many professionals are perfectly happy with the images produced by 6-10 megapixel digital SLR models.

When squeezing a high resolution sensor into a small device the individual pixels need to be made smaller. Smaller pixels mean less light getting to each one and the result is much noisier images in low-light conditions.

So if you like to take pictures indoors, or on a night out, then a really big megapixel number on a phone camera probably isn’t a good thing for you.

Also, there’s usually limited room and budget for really good optics in a small device. For that reason, most phone cameras have to do without an optical zoom. More megapixels also mean more processing and thus more battery usage, as well as larger file sizes which mean more storage required and greater time to transfer. None of these are good things for the typical user.

So, with all of this well known by mobile device manufacturers, why do we continue ever upward in the race for more megapixels, with the likes of the Sony Ericsson Satio at 12.1 megapixels?

It should be noted that the engineers at Sony Ericsson (some of whom I had the pleasure of meeting in Stockholm last week) appear to have done an excellent job with the optics and the software supporting their sensor, such that one detailed review claims it has “potentially the best camera ever fitted to a phone”.

That said, it clearly suffers from low-light noise, and the default image capture setting is actually 9 megapixels, not 12, suggesting that they aren’t really all needed most of the time! The major reason for adding more megapixels is the “more=better” algorithm in the mind of many consumers when it comes to the numbers on the box.

What does all this have to do with Symbian? Well, to the extent that the platform could define software for the camera sub-system, should it be optimized for a pragmatic megapixel range and an attempt made to educate consumers about the pros and cons of technology choices?

Or, alternatively, should the OEMs that use that platform to build products decide what they think they can sell and drive the architectural requirements and consumer messaging accordingly?

Since the platform is primarily driven by OEM contributions, the latter seems much more likely than the former. However, different OEMs may have different product plans and policies in this area which are likely to lead to some fragmentation. Is this an area where fragmentation is inevitable and if so, how does that affect application developers and the services they can offer to end users?

Why more is not always better – Part I – Apps & App Stores

Retweet Share on Facebook

The technology sector is famous for its numbers races – and the mobile market is no exception. There has been competition to produce the smallest product, the thinnest product, the longest battery life, the biggest screen, the most colours, the largest storage, the fastest data connection, etc. Not necessarily all at the same time of course!

Early adopters tend to buy into these contests and often the numbers on the box are more important that the quality of the product when it comes to a purchase decision. However, sometimes more is most definitely not better for a wide range of reasons. This week I’m picking on two recent ones, inspired by my recent trip to the Mobil Business developer event in Stockholm.

First is a topic that’s very popular right now – apps and app stores. The event was introduced with a slide showing roughly how many apps are available on some of the most important mobile platforms.

The iPhone, Android and Windows Mobile were towards the top of the list, while Symbian and Maemo were at the bottom.

Speakers promoting all of those platforms, with the exception of Android, were at the event and after a series of keynotes from each, the event split into two workshops.

By far the most popular workshop was the one that covered Symbian, Maemo and Qt (the application framework you can use to develop for both).

So, developers (at least this particular crowd) were more interested in learning about the platforms that have fewer apps already. Assuming they don’t buy the argument that the platform with the most apps will dominate the market, this makes perfect sense – go where there’s less competition.

So it seems more apps isn’t better for developers. Indeed it has also been argued that more apps aren’t better for consumers either.

Basic economics says more competition should drive prices down and quality up, increasing value for consumers. Unfortunately a number of factors that have been widely discussed about the early Apple App Store implementation (for example, no in-app purchase/upgrade and ratings from people who hadn’t purchased the app) made it extremely difficult to differentiate on quality. Left with price as the only differentiator, there was the inevitable “race to the bottom” at which point competition was only optimising the quality of very cheap apps.

The result of this is that the vast majority of the applications (one estimate says around 98%) are hardly used at all. This situation isn’t good for developers, consumers, or Apple.

In fact, it brings the number of applications that are actually used well below the number of apps available on most other platforms.

It also reduces the willingness of some developers (particularly small independent ones) to invest in creating high quality apps, since getting one noticed in the crowd is such a lottery.

So, how should an app store get out of this situation? Will it resolve itself? If so, how? Can other growing app stores avoid the same fate? Should stores be more selective? Will minimum pricing work? Or, is the giant catalogue app store model fundamentally broken? Some suggest that better search technology is the answer, comparing app stores with the web, but applications can’t be automatically indexed like web pages and they don’t recommend one another by linking between themselves.

What would provide a better basis for application search? Personally, I tend to agree with the analysis over on Vision Mobile – the future will see many more app stores, serving different audiences or content niches. Of course that can only happen on the platforms that allow multiple stores! Alternatively, is Google right that app stores are just a fad and eventually everything will just be web services? What do you think?

Because we can – part I – the really mobile web

Retweet Share on Facebook

This is the first in a series of posts all about the amazing things you can do with Symbian devices. Among the major mobile device platforms, Symbian has a strong claim to being the most accessible in terms of functionality. It has also been the platform that device manufacturers have used to deliver some of the most feature-packed hardware. In turn, that has led to lots of curious and enthusiastic people pushing the boundaries of what mobiles can do. In many such cases, commercial or practical considerations are not at the top of a developer’s agenda, we’re just doing it because it’s cool, and because we can!

It seems almost everyone is talking about the “mobile web” these days, whether they’re optimising existing web content for mobile devices, or building cutting edge web applications (or widgets as we tend to call them). However, for almost 2 years now, some smart folks at Nokia have pushed the frontiers of the mobile web a step further by providing a mobile web server. The project, called PAMP (Personal Apache MySQL and PHP), is also open source in case you want to play with the code. At its core this project is a port of the LAMP stack, which powers about 40% of the world’s websites, to the Symbian platform and there is a great interview with the project lead describing the challenges involved and potential uses. It’s not anywhere near as difficult as you might think, since there has been ever increasing support for a Linux-like programming environment on Symbian in recent years. Read more »