SSH is great. I'm not being sarcastic either in saying that.
The next time you teach the meat of the market how to do SSH will be the first time it was taught.

Design for your consumers to come, not the ones you have now (skate to where the puck is going, not to where it is).

I kind of get what you are going after, here, but the real truth in here is that the solutions you proposed are something that probably depend on outside resources, some central control point which is between you and your device.
(I suppose so, from what I could find out from Nokia Mobile Web Server and Samsung Kies)

So basically you are trusting your data and your device access to somebody else. Well, that might be okay for you, but I rather like to be guardian of my data and access myself.

These services masquarade as convenience to end-users when actually with a little bit of creative thinking and available tools you can make up a platform for yourself that really is convenient, secure and private.

Nokia's MWS was a mobile web server and Python-driven CMS, pushed thru a Nokia-maintained gateway. The latter being because per their relationships with carriers, the use of a DNS gateway on one's mobile device meant that a user could literally skip the carrier they were on and do other things. Nokia played fair there, but nothing else was on their server. Samsung took everything except the server/gateway side of that tech and made Kies Air - a slightly detuned but smoother CMS over WLAN hosted from your mobile that allows for the management of various aspects of your mobile w/o pulling it from your pocket.

The point of a sever and CMS on your own mobile device - both which were built with open framework, open licences, and open source technologies and behaviors - is that you can manage all of this yourself, without exposing yourself to others.

If people could make it themselves always, then we'd not be having this discussion, because Maemo and the N810 would have been enough. Per the warts of the DIY community, not everyone can - but those who can rarely make it accessible enough that even those w/o their bent can do it. That's the entry point the MWS proposed. It was missed here and especially at Nokia (ask the Jolla board member who was one of the 4 people who created it).

---
Having a server and CMS on your mobile device means that you can create and maintain connections yourself. Every mobile is capable of it, every carrier restricts some important point of it in their terms of use. If people were responsible for this aspect of connectivity and mobility, there'd be a lot less of that central control.

QRcode reader is a must for me, any1 know if theres someone working on app that can read them?

Keepass, AWESOME!!

Strongswan and SIP Client.

Munzee and geocaching applications.. The Android versions dont seem to work on the Jolla...

how about a brightness widget app, in which the cover allows you to swipe left/right to switch brightness manually?!

I don't see KDE connect anywhere on here.
http://www.omgubuntu.co.uk/2013/09/i...-notifications

while waiting native geocaching app you can use c:geo. To make it work you must use osm as map source and disable compass (select use only gps in compass view).