Wednesday, 1 August 2012

Tizen Platform: 5 steps to success

Tizen is an open software platform for smart phones and other connected devices. The platform is a successor to the LiMo and Meego platforms, sharing some code elements from both and is being primarily developed by Samsung and Intel. It is hosted by the Linux Foundation, to bring some Open Source credibility, and the marketing is supported by the Tizen Association. It is early days for the Tizen platform with no devices released so far, but a "1.0" SDK and source code do show some promise. However given the limited amount of success that LiMo and Meego enjoyed, what does Tizen need to do to ensure better success? Here are 5 steps that I propose:


1. Find a niche, exploit it and expand

Quite honestly its tough out there for a fledgling OS. Its already a crowded market with some big players (i.e. iOS and Android). Not only did LiMo and Meego fail to make a mark, we see that Nokia's Symbian, Palm/HPs WebOS and others have either already died or are winding down. Tizen needs to find a niche, or two, or three, that it can successfully exploit and expand from. The advantages that Tizen should be able capitalise on are its potential to avoid major IPR issues, its openness (reducing product/platform development costs), and the support of Operators (who don't want to be sidelined from profitable areas of business by Apple and Google).


2. Utilise Samsung Bada experience

Samsung have their fingers in many mobile OS pies, including some they have developed themselves such as Bada. This platform is more of a low-end smartphone platform but its rather successful. For example, according to Tomi Ahonen (one of my favourite analysts/bloggers) for Q1 2012 Bada was ranked 5th by unit sales ("3.8 million sales, 2.6%" market share). That's pretty good for something that isn't their main focus, and to put it in a bit of context, it's well ahead of any Microsoft phone OS. Clearly Samsung are able to create and. more importantly, market a successful platform and ecosystem. If they are able to fully utilise this Bada experience for Tizen, it should be a success; and that's without considering what Intel and others can contribute.


3. Become the platform of choice for connected cars 

Well OK, this is a bit similar to point 1; it's a niche. However it is a very important niche for the future that I have blogged about in the past. Not only that, but Tizen already supports an In Vehicle Infotainment version of the platform with some industry following due to the Meego history. If Tizen can become the platform of choice for connected cars then a successful ecosystem can be built.


4. Utilise the Open Source Community

Tizen, like Meego before it, is largely based on existing well-known Open Source components. Utilising good, proven components leveraging the Open Source Community will aid Tizen by reducing costs (e.g. support, development). A fully open platform can also provide a playground for innovation; innovation that Tizen and device manufacturers can make good use of - potentially providing something unique from iOS or Android. At the time of writing though, the development and governance of Tizen isn't really open and is going on behind closed doors. That's OK for the time being as Samsung and Intel get the project fully off the ground and take the time to create something sufficiently complete and stable to be a compelling (useful) platform. It will have to be fully open soon though to keep the Community on board and behind it - goodwill doesn't last forever.


5. Learn from past mistakes

Tizen already has a history, and it's a bit mixed to say the least. As in life, it is very important to learn from past mistakes and try not to repeat them. I have already blogged about some lessons that could be learnt from LiMo,
 

5 steps to success for the Tizen platform....it all seems so easy doesn't it? It really wont be, but I believe Tizen has the potential to deliver on its promise.

Martin Yagi.
Martin is available for freelance consulting on mobile standards/collaboration, emerging applications/technology and innovation. To discuss your requirements check contact details in Martin's profile.

Tuesday, 17 July 2012

LiMo Foundation: 5 Lessons to Learn

The LiMo (Linux Mobile) Foundation was formed in 2007 as an open Industry collaboration to create a shared linux-based software platform for smart phones. It was a grand groundbreaking initiative from the founding members; Motorola, NEC, NTT DoCoMo, Panasonic, Samsung and Vodafone. Important Industry players sharing real platform code and not just API and protocol specifications was a first. Not heard of it? Well, it was comprehensively eclipsed by the Android platform that came later the same year. Many LiMo compliant handsets were still sold though, but mostly in Japan and those actually contained no code received from LiMo. The only 'real' LiMo handsets were the Vodafone 360 service H1 and M1 handsets from Samsung (neither of which were loved by their owners).

It was more successful than Nokia's open sourcing of Symbian (presumably a measure Nokia took partly in response to LiMo and Android) but nowhere near as successful as Android. As I was involved in the LiMo initiative since before its official launch, here some, an arbitrary 5, lessons that I think can be learned:-

1. Don't try to make a patchwork quilt of technology - at least not in a short time frame and all at once.

Patchwork quilts of components integrated from many places can certainly work; arguably most Linux-based systems are (or were originally) like this. However making a whole quilt in one go based on functional or political lines in a short time frame leads to problems (performance, stability, functionality, lack of extensibility, etc). This is what LiMo tried to achieve for its first version of the platform and it effectively failed - nobody really used the result in products. Just creating the platform did, however, prove that the members could work together to create something...an achievement in itself.

2. Don't let politics get in the way of technical progress.

Easy to say and understand...difficult to achieve in practice. If the organisational structure and procedures can be set up in a way that focuses on a business-like footing i.e. to serve the need of defined customer(s), that is all for the better.


3. If the (decision-making) power is to be shared equally, then the true commitment level must also be equal.

Not just the wish for equal commitment (ie investment), which is often difficult to achieve in practice given that the relative (financial/market) strengths of different players are very likely to differ significantly in an open collaboration. If this cannot be achieved, its better to recognise the fact; give the main decision making powers to a few (or 1) to craft the bulk of the platform and empower others to be able to innovate around the edges to be successful.

4. To be adopted by others, a platform has to be sufficiently complete, mature and stable enough compared to competing platforms.

Despite the marketing messages to the contrary (erm, at every MWC), this was where LiMo failed the most. The platform was never really complete (or complete enough) and kept changing significantly from one release to the next. Consequently it was immature and a really expensive and/or very high risk option that in the end nobody (apart from Samsung as one of the many operating system options they have) was able to take a bet on.


5. Delivery is Everything

For any platform to succeed today, open or otherwise, it not only has to meet #4 but also keep evolving and delivering, because that is what the competition (e.g. iOS, Android) is doing. To serve a niche need may be sufficient for survival in the short term, but the niche is likely to be eroded over time; so plan for the long term and don't rely on it - deliver, evolve, improve and deliver, again and again.

Uh oh, I've run out of lessons to give already, so this will have to be 5a: Don't necessarily give up easily when the core raison d'etre is still there (Google effectively control Android for instance; not the ideal situation for mobile Network Operators). The platform code was effectively transferred by Samsung to form the basis of the Tizen platform and the Limo Foundation re-scoped and re-branded itself as the Tizen Association. I wish every chance of future success to Tizen.

Update: Many thanks to the Carnival of the Mobilists (@theMobilists) for mentioning this blog entry in their weekly roundup of most interesting/best blogs, I really feel honored.


Martin Yagi.

Martin is available for freelance consulting on mobile standards/collaboration, emerging applications/technology and innovation. To discuss your requirements check contact details in Martin's profile.

Wednesday, 11 July 2012

There's war going on out there

You didn't know there was any war going on? Well, actually there are several, and they are getting increasingly messy, but today I will be covering only at the mobile IPR (Intellectual Property Rights) wars. First though, let me be clear - although I am an inventor/co-invented of 5 granted patents, I am not a patent expert, not by a long way, but I am very interested in the area. Don't sue me over this blog, ok?

We are talking disputes about copying without authorisation (i.e. without paying for the privilege). With IPR disputes its very tit-for-tat; anyone sued tries to sue back in a "my gun is bigger than yours" play...although sometimes the gun is a bit of a fake. The wars are going on with the following non-geograhical fronts:-
  1. Patents (function)
  2. Copyright
  3. Design Patents (the form of the product)

The first biggie is (or was) between Oracle and Google and covered patents and copyright. Google's Android operating system supports applications via the dalvik virtual machine. The applications are written in Java and compiled to dalvik code in much the same way as Java code is compiled to then run on a Java virtual machine; Java-based technology is critical to Android (that's millions of handsets therefore millions of dollars, folks). Google even copied some of the code and used the same developer familiar Java APIs. Google and Sun Microsystems discussed licensing but nothing was ever penned. When Oracle bought and rescued Sun Microsystems they obtained the Java assets and started looking to Google for some pay-back claiming also that Android fragmented and thereby damaged Java. This action recently went to trial in the USA and Google despite clearly doing wrong, got out of jail free by the skin of their teeth. For now anyway, as Oracle are almost certain to appeal the judgement and keep this rolling on for many more months (to the joy of the lawyers involved no doubt). Can't wait to see the Hollywood movie about this one.

The next biggie is Apple against Samsung. Although Apple is pretty much suing everyone else, or anyone else big in Android (Samsung, HTC and Motorola) over patents they also have action against Samsung over design patents, successfully claiming the Galaxy Tab is a blatant copy of the iPad (even a scene in 2001 A Space Odyssey where an iPad-like tablet computer was used was not considered significant prior art to let Samsung off the hook) . This is an interesting fight as Samsung is also a critical supplier of components to Apple, i.e. despite their differences they still need each other badly. Essentially Apple is portraying Samsung as a copier and attempting to protect the Apple brand and market-leading user experience - both of which lead to higher margins for Apple (ah, dollars again!). All the posturing will probably lead to a "win" of some sort for Apple, but we shall have to wait and see.

There are also some significant skirmishes between Microsoft and Motorola, Nokia and HTC, RIM, Viewsonic. Smaller players are mostly staying out of court, for now, but will certainly come in the sights after the current cases finish and provide precedent.

I will come back to this subject in the near future to talk about the types of patent being used in the wars and the strategies of the players involved, but in the meantime, If you are interested in learning more, check out the following:-



...and finally... this.


Martin Yagi.

Martin is available for freelance consulting on mobile standards/collaboration, emerging applications/technology and innovation. To discuss your requirements check contact details in Martin's profile.

Tuesday, 3 July 2012

Congratulations to Dr. Mike Short CBE

A brief post to congratulate Dr. Mike Short for being awarded the CBE in the recent Queens Birthday Honours list for services to the Mobile industry. Dr. Short is currently VP of Telefonica Europe and has racked up an impressive list of past achievements in Mobile;Director of Cellnet, VP of Technology O2, Chairman of the GSMA, WAP Forum/OMA Board member, served on many UK Government mobile-related boards/task forces/Councils to name but a few.

Along with his many other activities Dr. Short also somehow finds time to be the President of the Institute of Engineering and Technology (IET). Two weeks ago I attended the IET Berkshire Annual Mobile Telecommunication Lecture where Dr. Short spoke on the "Internet of Things".  It was a very interesting lecture that taught me a few new things, and I was fortunate to be able to briefly talk to Dr. Short afterwards.


So, big congratulations to Dr. Mike Short, Commander of the Order of the British Empire!


Martin Yagi.

Martin is available for freelance consulting on mobile standards/collaboration, emerging applications/technology and innovation. To discuss your requirements check contact details in Martin's profile.

Tuesday, 26 June 2012

Tizen: Can it refresh yer phone's 'ead?

Tizen, if you don't know , is the open linux based OS for smartphones and other devices backed by the Linux Foundation, Intel and Samsung. It could best be described as a follow-on project to Meego and Limo (which is one of the things I was working on at NEC).

I don't know who came up with the name Tizen, the Linux Foundation, Intel, Samsung or some marketing consultant, and I don't know what meaning its intended to convey, if any.

For me though, when I think of Tizen I immediately think of Tizer, a somewhat obscure UK brand of soft fizzy drink I remember liking when I was young, even though it was always far from fashionable (much like myself!). Even when it was sponsoring, presumably at big expense, the highly popular Saturday morning music TV shows "The Chart Show" and "CD:UK" with the (annoying) catchphrase "refresh yer 'ead" slogan it never really took off. They tried big sponsorship, re-branding, various slogans and still it didn't become particularly popular. It does, however, still seem to exist, so at least it has fared better than New Coke!

I doubt that a Tizen powered phone will "refresh yer 'ead" anytime soon, but I do wonder if there will be any parallels between Tizer the drink and Tizen the OS. We will get the first indications later this year when the first handsets hit the stores....I wonder what the advertising will be like; anyone want to suggest a floating, red, flip-topped head character?


Martin Yagi.

Martin is available for freelance consulting on mobile standards/collaboration, emerging applications/technology and innovation. To discuss your requirements check contact details in Martin's profile.

Thursday, 21 June 2012

A Driving Opportunity

Maybe you don't know this, I didn't until very recently, but from 2015 all new cars sold in Europe should be "connected" due to the EU eCall recommendation. The eCall concept is to allow the car computer systems to automatically (or manually if selected by a passenger) call for assistance in the event of an accident. A key point being that it is not just a voice call to an emergency service operator, but also data such as location. This may be the first mobile Machine to Machine (M2M) application that consumers will actually become aware of.

OK, there is nothing especially new about the concept or the technology. For example, Vodafone and BMW recently announced that Vodafone M2M SIMs will enable the connectivity for BMW's ConnectedDrive service. A premium service that fits well with a premium car brand, where the prestige is likely to outweigh the cost implications for the target market. "Yaah, my car is smarter than yours!". 

However, if as expected, this is applied across all vehicles regardless of brand, from Kia to Rolls Royce, then there will be opportunities there to be exploited - no manufacturer will want to incur the cost of including basic connectivity without trying to monetise it to their advantage, e.g. by offering value added services. This should drive (no pun intended) the growth of connectivity modules, display panels (for user interface), services and applications.

It will be interesting to see which Companies can make the most of this opportunity, and most importantly engage with the consumer. How long will it be before my dad asks me which car he should buy next - the one with iCar or gCar inside?


Martin Yagi.

Martin is available for freelance consulting on mobile standards/collaboration, emerging applications/technology and innovation. To discuss your requirements check contact details in Martin's profile.



Thursday, 14 June 2012

Nokia: Desperate measures for desperate times?

Today Nokia made several announcements, including one outlining redundancies and downgrading profit outlook and one regarding the sale of the luxury handset Vertu division. What is the significance as Nokia struggles to reverse its recent downwards spiral?

The sale of Vertu means Nokia is exiting the luxury handset market. No more of making profitable bling powered by a fairly run-of-the-mill-OS (the OS Nokia CEO Stephen Elop considers outdated). I guess Nokia doesn't like growth of sales, it doesn't fit with the current strategy! Vertu could have been a safe haven ensuring Nokia continues to make mobile phones, as its other mobile divisions are in a sorry state.

The operational changes and redundancies mean doom and gloom. The reports are that it means the total cancellation of the Meltemi platform - a linux based platform being developed for future low-cost phones (i.e. to replace the Symbian OS and be a Nokia competitor to Samsung's Bada). As Symbian was already on limited time life-support, these changes today appear to mean that Nokia is accelerating towards a Windows Phone only future. However Windows Phone will not run on low-powered hardware, and therefore this means Nokia is also exiting the low-end phone market as it will be difficult to compete with Samsung, ZTE and all with more modern software.

So, Nokia ploughs ahead with Plan A (Windows Phone Lumia handsets), a plan which hasn't been working out very successfully so far, and dumps Plan B (Meltemi) whilst ensuring any new low-cost handsets won't be (perceived as) competitive or attractive either. I know these are not good times for Nokia, and things are getting desperate for them, but this seems a desperately risky plan. Its sad to see a once-proud Company in such dire straits.

You can now buy a Nokia share for about the same as a ringtone or app...which will be the wiser investment?


Martin Yagi.

Martin is available for freelance consulting on mobile standards/collaboration, emerging applications/technology and innovation. To discuss your requirements check contact details in Martin's profile.