Samsung To Merge Bada with Tizen

For most of you, Samsung’s Bada will be a bit of a mystery. As far as I know, it isn’t sold in the United States, and Samsung isn’t pushing it very hard in Europe either. Still, it has a 2% market share, and since my brother has a Bada phone, I can confirm it is a surprisingly good, fast, and easy to use smartphone operating system. Still, Samsung seems to have greater plans for it than just this 2%, since it has announced it will merge Bada with Tizen, the successor to MeeGo.

Technically speaking, Bada isn’t an operating system per se; it’s actually a platform that can utilise multiple kernels. Depending on the hardware it runs on, Bada can employ a proprietary RTOS kernel or a Linux kernel. From this perspective, merging Bada with Tizen makes some sense.

Tizen is the continuation of the failed MeeGo project from Nokia and Intel, and Samsung has been part of Tizen from day one. It makes sense they had plans with this project that went beyond a supportive statement, and this seems to be it. Apart from serving the lower-end of the market in certain areas of the world, it’s pretty clear Bada+Tizen has another role to play as well.

Samsung is the largest Android vendor – and by a wide margin, too. They’re also the only one posting sustained and continuous growth. Most – if not all – of this comes from Android phones (as opposed to features phones or Bada phones), making the company’s mobile phone business incredibly dependant upon Google (and vice versa, but that’s another matter).

As such, it makes sense to develop an in-house mobile operating system as “een stok achter de deur”. If Google ever gets cocky or wants to tighten the rules too much, Samsung can simply ramp up its efforts with Bada. As such, I wouldn’t be surprised to learn Samsung is also working on bringing the Dalvik VM to Bada to ensure Android application compatibility – in case it’s needed.

All in all, one of the largest smartphone manufactures getting behind its operating system is a good sign – although there is always the possibility that this is a step towards actually downgrading its importance by handing over development to an open source project.

As usual, time will tell.


  1. 2012-01-16 1:18 pm
    • 2012-01-16 1:23 pm
      • 2012-01-16 1:30 pm
        • 2012-01-17 5:22 am
    • 2012-01-16 6:42 pm
      • 2012-01-16 10:03 pm
        • 2012-01-17 5:26 am
  2. 2012-01-16 2:04 pm
    • 2012-01-16 11:55 pm
      • 2012-01-17 5:05 pm
  3. 2012-01-16 2:08 pm
    • 2012-01-16 2:47 pm
      • 2012-01-16 4:07 pm
      • 2012-01-17 6:12 am
        • 2012-01-17 7:26 pm
          • 2012-01-23 11:32 pm
    • 2012-01-16 7:38 pm
      • 2012-01-17 8:50 am
    • 2012-01-17 6:23 am
  4. 2012-01-16 3:37 pm
  5. 2012-01-16 6:06 pm
    • 2012-01-16 11:36 pm
      • 2012-01-17 2:20 am
        • 2012-01-17 8:23 am
          • 2012-01-17 12:39 pm
          • 2012-01-17 7:06 pm
    • 2012-01-17 9:32 am
  6. 2012-01-16 6:44 pm
    • 2012-01-17 5:29 am
      • 2012-01-17 4:06 pm
        • 2012-01-22 12:44 am
  7. 2012-01-19 3:32 pm