Architecture of Android application support
asked 2017-10-27 20:21:31 +0300
This post is a wiki. Anyone with karma >75 is welcome to improve it.
Posting the following question and reading the answers/comment,
https://together.jolla.com/question/171733/how-relevant-is-android-support-version-444/,
I started to wonder how the Android application support is built more specifically (concerning all Sailfish devices).
I can't really get the whole picture of the components and the structure of it, because different names are used in different discussions and descriptions:
- Alien Dalvik
- Myriad Group (http://www.myriadgroup.com/en/products/device-solutions/mobile-software/alien-dalvik/
- Dalvik (https://en.wikipedia.org/wiki/Dalvik_(software)))
- Android Robot (mentioned in the description of the Android support app)
- ART / Android Runtime support (https://en.wikipedia.org/wiki/Android_Runtime)
Then we have a general description here: https://sailfishos.org/wiki/Android_Compatibility
Can someone, who really knows this in detail, explain how it is all structured? A detailed, yet brief explanation, if possible.
What about security? Sailfish is supposed to be more secure than Android. Is the Android support a potential security threat to Sailfish? This probably depends on the architecture.
I am not sure in which sense Sailfish is supposed to be more secure than Android. There is no attempt at all to isolate apps into containers, unlike Android. There is no possibility to remove permissions from an app.
Federico ( 2017-10-27 22:15:47 +0300 )edit