Sure! Conrod itself aims to be "backend agnostic", and isn't (or _shouldn't_ be) restricted to any specific window or graphics backends.

The examples use piston_window, primarily just because it's easiest to setup, but hopefully we can get some examples using other window/graphics combinations too.

piston_window itself uses a combination of glutin and gfx's gfx_device_gl, so if both of those support Android, it should be possible to get conrod's current examples going on it.

One thing i'm unsure about is whether or not freetype-rs can be compiled for Android, however hopefully this shouldn't be an issue much longer as we're aiming to remove it in favour of the rusttype crate. Come to think of it though, conrod doesn't actually depend on freetype-rs explicitly, it just happens to be the font rendering used by the piston_window graphics backend (which is only used for the examples).

Also, we may be lacking events specific to touch devices, but i'd be happy to see them added :+1:

• glutin supports android
• gfx.rs supports android with backend gles (is that sufficient for conrod?)
• any news on the touch-event front?

I made https://github.com/jbg/conrod-android-skeleton which could be interesting to people looking at this issue.

945 seems to be the main blocker to conrod being quite usable on Android.