Linked by Thom Holwerda on Wed 22nd Aug 2012 19:54 UTC
PDAs, Cellphones, Wireless As Sammobile reports: "Samsung will not bring any kind of new Bada phones in the second half of 2012. Samsung's latest bada phones showed up last year at IFA 2011 in Berlin. Samsung showed the Wave3, Wave M and Wave Y, all those devices run on Bada version 2.0. The focus of Samsung in the second half of 2012 is fully on Windows Phone 8 and Android. Because the Windows Phone market is in the hands of Nokia they will try to get that share back. Samsung will also try to make their Android position better than before. Thanks to some new Galaxy products in the second half of 2012. Another sad thing is Samsung moved their first TIZEN OS devices to 2013. Samsung already gave away some developers devices with TIZEN 1.0. The only problem is the support from TIZEN itself." Tizen was a lost cause to begin with, and Bada, while actually pretty good, can easily be replaced by Android. As much as it sucks to lose two operating systems (don't kid yourselves - these are EOL messages), it makes sense from a business perspective. Next up: the TouchWiz team.
Permalink for comment 531978
To read all comments associated with this story, please click here.
RE[4]: Comment by shmerl
by shmerl on Fri 24th Aug 2012 07:55 UTC in reply to "RE[3]: Comment by shmerl"
Member since:

Nemo is for handsets, built on Mer, and has a UI based on QT. Isn't Plasma Active also based on QT? And Jolla will build something based on QT and on a handset, but it won't be Nemo.

Qt is a base library which doesn't force you how UI should look and it can be used with various DEs and window managers, mobile and desktop ones.

Plasma Active uses KWin and their user interface to create a mobile optimized UX. Nemo is using Lipstick QML desktop to create the user experience. Jolla didn't really explain what they'll use besides Mer core and potentially some parts of Nemo to create their UX.

However, all these derivatives share common architecture - they are all conventional Linux (using either or Wayland unlike Android which is incompatible with above) and common libraries (see ).

So if you write a mobile Linux application using those libraries (including Qt for the interface for example) - you'll be able to build it for any of those distributions. Note that they can be built for various architectures (x86, ARMv7hl, ARMv7l, MIPS and etc.). So if you figure out what device you target - you can build your application for it for example with cross compilation (see

Adjusting your application to various form factors (different tablets, handsets and etc.) is the question of your design and flexibility of that application, it's not bound to the distribution per se. If you want to fit a certain theme/style that's already another question.

Android does all three, so I know how to write an app for that. How exactly do I write a... Mer app?

Mer is not an end user distro. Writing a "Mer app" means creating some library or runtime for example.

Nemo app?

GUI mobile application with Qt. You can compile it for Nemo target using the Mer SDK.

Are they all the same? Do they interoperate at all?

Mer derivatives aren't the same, but they are close enough to make porting between them easy. If architecture matches, one can potentially run some application even without recompilation, but there can be version differences and other specifics. In most cases you can just compile your program for different Mer based targets and that's it.

All the docs seem to be aimed at people putting stuff on hardware, or people looking to contribute straight to one of the projects, and there's stuff for writing QT apps... but what do I do as a potential App writer?

You can start with getting familiar with using Mer SDK. There are Hello World examples on the SDK & SB2 page:

Mer also allows using OBS.

Edited 2012-08-24 08:01 UTC

Reply Parent Score: 1