Ask / Submit

Jolla devices / Sailfish OS – genes & distinctions that matter ....

asked 2015-10-06 11:11:39 +0300

launchpad gravatar image

updated 2015-10-23 12:16:20 +0300

After the release of Sailfish OS 2 and looking towards the development of upcoming releases & devices - which "genes" / principal features / design elements are crucial to advance & distinct the "unlikeness" associated to Sailfish OS & jolla devices ?

[ Focusing on holistic approaches no specific requests for patches & features to be named here – except for reference ]

Some topics that might be of interest :

  • The other half - is there life without one before even ever really tried it's potentials ?

  • UI straightness & behaviour ( e.g. efficiency vs beauty and so forth )

  • business-related usability / workflow support

  • context & situation aware ambiences

  • privacy & security

  • car / vehicle integration

  • resource efficiency

  • availability of ( community-voted ) device ports

Or does jolla / Sailfish need to differentiate at all ?

e.g. FAZonline-article on Chinese Anroid bargains flooding the markets: original version | Google translated version

edit retag flag offensive close delete

10 Answers

Sort by » oldest newest most voted

answered 2015-10-06 14:12:00 +0300

inte gravatar image

updated 2015-10-06 14:20:53 +0300

I think it would be cool to rely more on gestures in upcoming releases. For instance, the pull and edge swipe gestures in SF2.0 homescreen are merged and don't have dedicated functions. It would be nice to have different functions for these gestures, e.g. use the side-pull gesture for coveractions and only the edgeswipe to go through the caroussel. Also, it would be nice to treat the eventsview as a seperate screen and not as part of the caroussel. That would allow to reach/peak to eventsview from every caroussel-page without having to rotate the caroussel to the events page. The eventspage-display could be triggered by the bottom edgeswipe which currently has the same function as the bottom-pull (app drawer). Just a few thoughts.

edit flag offensive delete publish link more

answered 2015-10-19 15:29:07 +0300

ossi1967 gravatar image

The only thing I really think is crucial (and "unlike") in Sailfish is the fact that I find a very normal, desktop-like system when I go to the command line. The UI, hardware features like the "Other Half" and other stuff are all nice, but they wouldn't matter at all should Jolla ever decide to lock me out of /etc or switch to a CLI that doesn't understand ls and cd. Simple as that.

edit flag offensive delete publish link more

answered 2015-10-19 15:13:38 +0300

ApB gravatar image

The features that need to be implemented are "documented" in TJC. Its more a matter of polishing the OS and adding some basic features that matter in order to be a reliable everyday tool.

A new device of high quality is needed.

edit flag offensive delete publish link more



Not just one but two devices. J2 to replace the current phone and J3 with similar specs in a smaller format.

vattuvarg ( 2015-10-19 23:56:24 +0300 )edit

@vattuvarg: I don't understand what use could be a smaller device, unless it 's a smartwatch. A BIGGER device is absolutely needed, at least 5 inches but 5.5 would be highly desirable.

Giacomo Di Giacomo ( 2015-10-20 11:29:24 +0300 )edit

@Giacomo Di Giacomo

Because even the current device is pushing the limits of use with one hand. Plus the awkward shape doesn't help much with the way the phone feels in the hand. And then there is pocketability. Many people don't carry bags or whatever and need a phone that will fit in a pant pocket.

ApB ( 2015-10-20 11:42:16 +0300 )edit

@Giacomo Di Giacomo: current movement towards bigger screens on phones doesn't attract me at all. The N9 was ideal size for me. If I want a bigger screen I'll use a tablet instead.

Mohjive ( 2015-10-20 11:49:37 +0300 )edit

@Giacomo Di Giacomo - It is quite possible that another company will produce a sailfish phablet. ...but...

Jolla is the only company with enough guts to create a smaller phone.

vattuvarg ( 2015-10-20 11:50:45 +0300 )edit

answered 2015-10-19 22:52:10 +0300

kaktux gravatar image

updated 2015-10-19 22:57:47 +0300

well- the most unlike thing with jolla phone is the update policy. where all other manufacturers only give updates for a year,maybe a little more, often less. i love that jolla phone gets ongoing support. i would love to see that continuing -kind of like lts versions with linux distributions. i don't need bigger,better,faster every time my mobile provider wants me to. i would like my phoneto be supported for longer periods and would surely be alright to pay a fee to get that (like an update subscription or so). this combined with the phone concepts with replacable parts is what is my favourite scenario.

edit flag offensive delete publish link more

answered 2015-10-19 19:11:12 +0300

AkiBerlin gravatar image

Talking about "genes" (which goes back to Meego/N9):

one-handed operation facilitated by gestures would be such feature. However, this feature is compromised to a large extend by the hardware design of Jolla 1 which cannot easily be held and operated by one hand.

But than again, IMHO this is still a feature worth having in a future phone with better ergonomics improving usability a lot.

edit flag offensive delete publish link more



For me the size of the J1 is just about perfect. For my daughter not so much.

There are two ongoing threads about possible future phones:

Crowdsourcing the J2 - A phone of the same size as the current product.

Suggestions for J3 - A smaller phone (roughly the size of iPhone 5).

The idea is to create two phones in parallel, both sized for one-handed use but for different hands. I think you (and many others, including my daughter) would like the size of the J3. Personally I am still dreaming of owning a J2. My hands are large enough...

vattuvarg ( 2015-10-19 23:35:05 +0300 )edit

answered 2015-10-21 20:46:04 +0300

alamaki gravatar image

Official support for major UI-customizability.

Since the writing on the wall is that Sailfish UI must be like android rather than unlike, I think it should be possible to develop and install UI customizations as easily as apps. Lock screen, home screen, app launcher, events view and navigation logic between them should be fully replaceable. Maybe add possibility to create a new views to the carousel (I can't think of a good use for this, but somebody might).


  • Don't operators/other partners already expect to be able to customize everything like they do on android? Why not make customizing Sailfish much easier than it is on android (OS updates from official source when they became available and operator updates its customizations whenever).
  • If Sailfish is to someday run on varying device form factors, its going to need to be customized for them anyway, or it'll be a poor fit (already bit of a compromise on the phone).
  • There's probably some product identity BS reason not to allow customization, but being like-android isn't much of an identity. Just go ahead and embrace the fact that there's nothing that's always on screen advertising what OS the device is running. Highly customizable UI would actually fit perfectly with the "unlike" slogan. Why should your Sailfish device be limited to looking and functioning like mine when they could be unlike?
  • Customization possibilities would peace us whiny early adopters bitching about unwelcome changes in Sailfish almost 2.0.
edit flag offensive delete publish link more

answered 2015-10-21 23:12:23 +0300

pedrox gravatar image

I think that there is lots of (unlike) potential for expanding the possibilities of the ambiance concept within Sailfish.

The new way of switching to Silent, by changing ambiance from the top swipe works well for me...but also makes me want more options: e.g. could I quickly switch to a flight-mode ambiance like this? Or one with a specific bluetooth pairing enabled? Or data-roaming off? Or a bedtime ambience where the fonts are bigger (because I'm not wearing my glasses)?

Ambiances might also be a good vehicle for partner UI customisations (as mentioned in previous answer above), and are more practical to change than TOH's.

edit flag offensive delete publish link more



Indeed there is potential. This might give you some clue:

lakutalo ( 2015-10-21 23:28:42 +0300 )edit

answered 2015-10-19 23:53:30 +0300

vattuvarg gravatar image

The user experience should be swift. Decorations are nice but should not slow down the operation of the device.

One good example is the remorse countdown. It does not lock everything while counting.
One bad example is the pulley menu of Eineheminlampi. It keeps the user waiting.

edit flag offensive delete publish link more

answered 2015-10-20 00:05:46 +0300

vattuvarg gravatar image

Vehicle use has two important factors.

  1. A very dark display, suggesting the use of AMOLED technology.

  2. Audio interaction, such as spoken directions from the navigation software.

edit flag offensive delete publish link more


To me awesome would be a "car docking other-half cover", where the phone detect and switch to a "car mode":

  1. Nav mode: enable GPS and open Maps...

  2. Music mode: enable bluetooth and open Player (with the possibility to do play/stop/next.. from the stalk remote controller)

Amilcar Santos ( 2015-10-23 13:07:31 +0300 )edit

answered 2015-10-22 17:06:13 +0300

shfit gravatar image

Paid apps in Jolla Store. This is way overdue to attract and support developers and generate revenue for Jolla. I'd rather pay for good apps than be data-mined or bombarded with adds. I know this isn't our current situation, but that partner space got my alarm bells ringing.

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools



Asked: 2015-10-06 11:11:39 +0300

Seen: 1,601 times

Last updated: Oct 23 '15