Saturday, December 29, 2012

End of the year look at Nokia

It's almost been 2 years since Nokia CEO Stephen Elop announced the drastic strategy change in smartphones from Symbian & Meego to Windows Phone. The announcement was done in Feb 11, 2011 - a date well remember by all ex-Nokia employees like me. At the time the strategy change was announced all of us knew that a change is needed. Symbian - once the most widely used  smartphone OS - was losing it's appeal. Symbian's UI was unintuitive, execution was slow, and organization was slow and bloated beyond imagination. Meego was promising, but was taking forever! 

A drastic change was needed, but was the shift to Windows Phone - an unproven smartphone OS from Stephen Elop's former employer - the correct choice? Let's take a look at how Nokia has been performing financially, ever since Stephen Elop took over (third quarter, 2010) to today.



Nokia Revenues Q3 2010 to Q3 2012

The above graph plots Nokia revenue & net profit over Q3 2010 to Q3 2012. In Q3 2010 Nokia earned approximately 10 billion euros in revenue, and only 322 million in profits. Not the best performance for a quarter - earning just a few hundred millions for over ten billion in sales means that something needs to change in the company. That "something" would probably be controlling costs, increasing ASP (Average Selling Price of handsets) by focussing more on smartphones, and getting rid of businesses that were burning cash. 

Friday, October 12, 2012

Some Thoughts on Android & Nokia's Lost Oppertunity

After working on Nokia's Symbian OS for around 4 years, I've recently started exploring the Android platform from a technical architecture perspective. The more I explore, the more familiar it seems. One reason of course, is that below the Java layers - what is known as "native" software in Android - it's all regular C/C++ based embedded software on a Linux kernel. Maybe it seems even more familiar to me because my work in Nokia involved a little bit of Maemo/Meego integration also. Indeed, below the Java layers, once could theoretically mix & match code from AOSP (Android Open Source Project) and Meego, and yet have a device that works!

The picture below is an over-simplified system architecture diagram, but helps explain a very high level view of Android.

Android architecture from developer.android.com

The Java layers, which I refer to are the top two layers in blue. The rest (libraries & kernel) is regular C/C++  software running on a Linux kernel. 

Friday, August 3, 2012

Nokia in Q2 2012: A lighter balance sheet, and a free OS


I’m not doing a full analysis of Nokia Q2 2012 results here. Very briefly, Nokia group revenues were 7.5 billion EUR with a loss of 1.53 billion EUR. A billion plus euro loss cannot be very rosy, of course, but maybe investors expected worse, as the stock price spiked up briefly after the announcements of the results on Thursday, 19 July.






Revenue & Profitability has taken a hit for the last one year, when the strategy of shifting from Symbian & Meego OS’es to Windows Phone has gone disastrously wrong for the company. A very detailed analysis of this strategy gone wrong can be found on Tomi Ahonen’s communities-dominate blog. As for this current post, the chart below tracking Nokia revenues is enough to describe the problem.


Nokia revenues - falling since 2011.


But in this post I try to delve into some of the revelations in the Q2 earnings release.

4 Billion EUR Lighter Balance Sheet

If we take a look at the balance sheet on Nokia's Q2 earnings release, there is a reduction of assets of about 4 billion EUR between Q2 2011 and 2012. About 1.4 billion EUR of this comes from impairment of Goodwill & amortization of intangible assets. This is also explained in a discussion on the operating results in the Q2 2012 interim report.

"During the second quarter 2012, based on a combination of factors, including the decline in our market capitalization, credit rating downgrades as well as our operating results, we concluded that there were sufficient indicators to require Nokia Group to perform an interim goodwill impairment analysis as of June 30, 2012. "


This explains the 1.4 billion reduction in goodwill and intangible assets. But what else did to reach this 4 billion EUR figure? 

"In the second quarter 2012, Nokia recognized EUR 800 million in valuation allowances related to its Finnish deferred tax assets in accordance with accounting standards "

Deferred tax assets is when a loss making company expects to make profits in the future, and sets aside a portion of their losses as tax credits to take advantage of, when they return to profitability. But this is allowed, in Finnish and International accounting laws, only if there is sufficient indication of the company returning to profitability. Deferred tax assets sits on the balance sheet as a current asset, and this accounts for another 800 million of the total 4 billion reduction in assets. 

The rest of the 4 billion is made of lower accounts receivable (amounts due to the company), and prepaid expenses. 

Now, I may be reading a bit too much into this, but cleaning up the balance sheet of intangibles, and deferred tax assets may be to make it more palatable to a buyer. Even though Nokia is currently valued low (it's currently valued lower than what Motorola was picked up for), most buyers would not be convinced by intangibles & goodwill on the balance sheet. Goodwill comes up when a company acquires another company, and pays more than the net asset valuation of the acquired company. The excess amount paid is not treated as a loss, but projected as an asset, which is the intangible valuation of expected synergies from the acquisition. Goodwill appears on the Nokia balance sheet because of the past acquisitions of Navteq, and others. 

Thursday, May 31, 2012

Open Source Licenses - Part 2

In my last post, I wrote an overview of what is open source, and common concepts for open source licenses. In this post, I would focus on a few popular licenses in open source software.

GNU General Public License (GPL)

The GNU General Public License is the license under which the GNU operating system is licensed out. The license has been authored by Richard Stallman’s Free Software Foundation, and is a copyleft license. The current version of the license is version 3.0, however the previous version 2.0 is also quite popular. Since I personally have not dealt with version 3.0, I would stick to version 2.0 in this post.
The GPL v2.0 starts with a preamble, which summarizes the philosophy behind the license. In other words, the belief that software should be free to run, modify, and distribute (while noting that "free" means freedom, and not free of cost). It also points out that there are certain restrictions which are necessary to ensure that a user of the software does not limit the freedom of other users. Paragraph-4 in the preamble section states...


This is a good summary of what the license is trying to achieve. The authors believe that the software should be available to all to use and modify freely, however, such modifications should not result in the restriction of the freedoms of other users. The preamble goes on to mention that in order to enforce this, the authors assert their copyright over the software, and are licensing it out to users under the terms and conditions of the next section. The preamble ends with an explicit patent grant.

The preamble is followed by the main "Terms & Conditions for Copying, Distribution and Modification" section. Paragraph-0 states that the license applies to both the original software work, and any derivative works. The term "derivative works" is defined as "...a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language". This is a bit generic definition, and is one reason why GPL is not very popular for use in commercial software products. Companies that want to use open source along with their proprietary software architecture are deterred by this wide definition of derivative works. The concern is that under such a definition, all of their software stack would become a "derivate work" if they link with the open source library, and/or use the functions of the open source library. This would cause proprietary software to become "contaminated" - a term used to define the situation where proprietary code has to be licensed out in source code form, because it comes under the copyleft clause of an open source license. However, in certain cases - notably in the Linux kernel license - the authors clearly state what they consider as derivative works, and what are unrelated code. Here is a snippet of the explicit notice put in the Linux license (rest of the license is GPL v2.0)



Thursday, May 24, 2012

Open Source Licenses - Part 1

Having worked with open source software for quite some time, I thought it would be nice to jot down a few of my thoughts on open source, in general, and the common licenses, in particular. Open source is quite common in technology, and especially the smartphone industry today. As I have noted in one of my previous posts, open source is used in four of the popular smartphone OS’es today (iOS, Android, Symbian and Bada/Tizen). While I started, I thought this would be one post, but as I rambled on, I thought it would be better readability to divide this across two posts. So here is the is the first part in a 2 part series on open source.


What Is Open Source?

Before getting into the details of licensing, it maybe good to define the concept of open source. In very simple terms, "open source" means software that is available in source code form, and which allows users to debug, modify, enhance, and re-distribute it. However, there is a belief or philosophy behind open source, which is deeper than just having source code available. The philosophy is that users of software should have freedom to run the software, customize it according to their needs, improve the software, and also make it available for others to use, thereby propagating "good" software. Due to the fact that the open source concept revolves around the freedom of software users, it is also sometimes called "Free Software". Richard Stallman founded an organization called the "Free Software Foundation", and he stresses that the "Free" does not refer to price, but to freedom. A famous and funny quote from Mr. Stallman is "To understand the concept, you should think of ‘free’ as in ‘free speech’, not as in ‘free beer’". Open source resolves around this fundamental philosophy of freedom, and most of the licenses reflect this in their terms & conditions.
Another non-profit organization - Open Source Initiative(OSI) - goes a step further and actually defines the criteria that a software should have before it can be considered to be open source. The criterion are (in summary, full list at http://www.opensource.org/docs/osd)

  • Freedom to redistribute the code.
  • Freedom to access source code.
  • Freedom to make modifications.
  • Integrity of the original author’s source code.
  • No discrimination against persons, group, or fields of use, or specific technology.


Why Open Source?

Having defined what it is, the question arises why it is so popular. Here are a few reasons why I think open source is popular.
  • High quality, and/or feature rich software: This is a general statement, and of course, there may be many exceptions. However, most open source projects have contributions from highly dedicated software engineers/programmers from around the world. Development is not budgeted by a single organization, but spread across many individuals, and the time and effort invested in the software is high. The result is either high quality code, or a plethora of features, or both. Note also that the source code access means that each programmer’s work is being scrutinized by an open peer review, which is one of the reasons for high quality code.
  • Significant savings in R&D cost: More and more organizations are using open source rather than develop their own proprietary versions of the same software. One of the reasons has to be the large savings in R&D effort (which translates into R&D expenses, that reduces the bottom line).
  • Faster time to market: As well as saving R&D costs, using open source means that time is not wasted in designing, implementing and testing the software which is already available. It involves significantly lesser effort in modifying existing software to meet a specific need, than to develop something from scratch. Again, this is a very generic statement, and exceptions will be there.
  • Supplier Lock-In is prevented: During my tenure as a multimedia integration engineer in a mobile handset manufacturer, I had encountered a case where a chipset supplier had used closed, proprietary API’s to implement some media accelerators. This meant that for every small minor API change, every little enhancement or bug fix, we had to raise a request to this chipset supplier. This would take time, and of course, money as well. Had this handset manufacturer mandated that the supplier use open source API’s to implement their components, the situation would have been much easier. Anyone could have made the minor tweaks that are always needed when integrating complex software components. Moreover, the company could also choose to switch suppliers without risking costly changes in their own code (as the open API’s would ensure a new supplier’s implementations worked).