As you know, Sailfish is for developer purposes equal to Mer Core + Nemo MW and Sailfish UI.

Having that in mind and spirit of openness, the SDK has been developed and is developed within the framework of the Mer and Nemo projects which serves as good places to develop this. Mer's Platform SDK is the basis of the backend for the Qt Creator frontend.

The Qt Creator sources that work with this backend is linked in Sailfish wiki and the backend is described in http://img.merproject.org/images//we...121115-132446/ (.ks file) and associated OBS projects in the public community OBS. The page https://wiki.merproject.org/wiki/Pla..._on_VirtualBox also describes it quite well.

Nemo has been used as a reference for application development and the current API offering right now is that of OpenGL ES2, Qt4 (as is in Mer) and the middleware APIs in Nemo. We're working on extending the API offering in Sailfish but at the moment it's equal to that of Mer and Nemo. Hence Sailfish SDK = Mer SDK at the moment.

The Mer SDK is as with anything else in Mer (Mer itself, Platform SDK, etc) for the purpose of taking, customizing towards vendor needs, so there'll be more Sailfish specific things coming as the API offering evolves and that'll be provided as future updates of Sailfish SDK.