A
AC Question
Hi there,
I recently read up about android and I'm quite puzzled how they do what they do.
From wikipedia, I understand that android runs on ARM as well as x86.
As a developer, would I only need to develop one app and that runs on all phones, tablets, android tvs etc? Both on ARM as well as x86? (similar to JAVA using bytecode?)
So they fully capsuled all hardware drivers, including graphics drivers? Is that still fast enough for 4k 3D?
And I'm even more puzzled by the driver model.
As a thought experiment, let's say that I developed an amazing new sensor that can e.g. check blood sugar (as far as I know, there isn't). Let's say Samsung developed this sensors and wants to bring it out in their Galaxy S9.
Can they write their own sensor hardware drivers that plug into Android? That would mean that the apps using that sensors are Samsung-specific, which I think doesn't work in the Android OHA. So do they need to push a standard sensor driver / API into Android first before shipping the new phone?
Or, if LG decides to bring out their own sensor, could there be two different kinds of sensors with different drivers/APIs, so that Samsung/LG apps using a sensor like that would not be compatible to each other?
I'm very curious about how that works and would appreciate any help.
Cheers,
Holger
PS: is there any good high-level introduction on how the android platform and app store ecosystem works?
I recently read up about android and I'm quite puzzled how they do what they do.
From wikipedia, I understand that android runs on ARM as well as x86.
As a developer, would I only need to develop one app and that runs on all phones, tablets, android tvs etc? Both on ARM as well as x86? (similar to JAVA using bytecode?)
So they fully capsuled all hardware drivers, including graphics drivers? Is that still fast enough for 4k 3D?
And I'm even more puzzled by the driver model.
As a thought experiment, let's say that I developed an amazing new sensor that can e.g. check blood sugar (as far as I know, there isn't). Let's say Samsung developed this sensors and wants to bring it out in their Galaxy S9.
Can they write their own sensor hardware drivers that plug into Android? That would mean that the apps using that sensors are Samsung-specific, which I think doesn't work in the Android OHA. So do they need to push a standard sensor driver / API into Android first before shipping the new phone?
Or, if LG decides to bring out their own sensor, could there be two different kinds of sensors with different drivers/APIs, so that Samsung/LG apps using a sensor like that would not be compatible to each other?
I'm very curious about how that works and would appreciate any help.
Cheers,
Holger
PS: is there any good high-level introduction on how the android platform and app store ecosystem works?