SailfishOS as an AutomotiveOS
asked 2016-05-30 23:51:18 +0200
This post is a wiki. Anyone with karma >75 is welcome to improve it.
Greetings everyone,
during the the recent Google I/O conference there was a prototype showing Android running on the board computer [1]. Could this be an option for SailfishOS as well to open up new markets and revenue streams for Jolla? What would be the obstacles?
Further, SailfishOS could be Automotive Grade Linux (AGL) [2] or GenIVI [3] compliant.
[1] http://www.theverge.com/2016/5/18/11704960/google-qualcomm-maserati-future-of-android-cars
[2] https://www.automotivelinux.org/
Obstacles:
- new UI design (distraction free, controllable animations, conform to national street safety regulations)
- vehicle function integration (e.g. AC, Button Arrays)
- start-up time improvements (most automotive systems give power to the head-unit only after ignition phase, so no always on)
- Jolla would need more developers to support an automotive and mobile branch of the OS
- ....
Collaboration and Business Model
From the comment I understood that Jolla on its own won't enter the automotive marked. Therefore, which partners does it take and what kind of collaboration and business needs to be in places?
The gesture-controlled nature of Sailfish OS would make it a safer alternative to the button-based user interfaces of the competitors. Real multitasking is another significant advantage.
The main obstacle is the massive domination of american mobile operating systems such as android and iOS. ...with possible integrity issues that most people simply don't care about.
The Jolla Helm concept was suggested in february 2014...
vattuvarg ( 2016-05-31 00:15:08 +0200 )edithttps://together.jolla.com/question/6613/sailfish-car-mode-ui-or-future-sailfishjolla-ivi/?answer=27939#post-id-27939
It will need a totally new UI. The way you will interact with the car controls needs to be quite different compared to the way you interact with a phone on your hand.
And of course you have to limit a lot what a user can do with it. You are supposed to be driving instead of checking your emails or whatever.
TBH i want integration with a smartphone in a car instead of a full blown os. Get in > the phone (no matter what is) connects to the car > have functions like navigation music etc from my phone controlled by the car controls. Ie the phone acts as the "brain" of the car systems.
ApB ( 2016-05-31 00:17:37 +0200 )editYes, you are right the UI needs to change. I put this in the list.
The UI could also be a joined effort of the automotive supplier or OEM. They want to add their branding there as well ;-)
gq0 ( 2016-05-31 00:47:04 +0200 )editThere is also a need to support some alternate input method. If we are talking about IVI OS and it supports only touchscreen, then I will never buy a car with it. The reason: I haven't met a touchscreen which works reliably in winter (temperatures -20° C and lower). It doesn't matter if there are gestures or buttons. If my input doesn't reach to program, then the input device is useless piece of **.
Another important item is the ability to show output from multiple apps at the same time. Something that was planned for the tablet.
krs ( 2016-05-31 15:12:07 +0200 )editDefinitely, touch screen only won't work. I summarised this under the point "vehicle function integration", so every CAN connected ECU, including buttons.
gq0 ( 2016-05-31 18:15:46 +0200 )edit