Does this mean that multi-threaded Chromebook applications go away? Android doesn't really do threads in the usual sense. It mostly uses a hack involving multiple processes. And the "main thread" is very special.
How do you mean? You can spin up threads using stock Java API or pthread on NDK. (If you intend to run them in the background your app will need an active foreground service to not get killed, though). As far as the "main thread", I don't think that's unusual for most user interface frameworks.
This is not really moving ChromeOS to Android, but rather using their Android Bluetooth component over the crusty Linux blueZ-thingy. And they even talk about the possibility of running the Android Bluetooth component on normal Linux. So there would be no ‘threading’ like repercussions as far as I would see?
