There are two possible approaches to this: a) packaging html5 version in to android App. There are plenty of frameworks for this. Probably the performance will

There are two possible approaches to this: a) packaging html5 version in to android App. There are plenty of frameworks for this. Probably the performance will not be the best. b) hashlink -> in theory possible, a couple of people have done it, but in practice the issue for documenting the process has been opened for years. Approximate structure for the hashlink approach would be: compile hashlink and required multimedia libs for Android, haxe->hashlink C -> Android SO, create a basic android Java activity which loads all the native code so libs. Consider the knowledge required for porting (not compiling existing port) Doom or some openGL c++ game (with custom engine) to android. This will be similar experience. On one hand actual work may be somewhat less since some people have done it and code is mostly there, on other hand you will have to deal with half a dozen different projects and their build systems and glue them together. You can find a couple of example projects from people who have gone through this struggle, but they will likely not work out of the box due to version changing and not being common combination so the requirement of knowledge or good code reading and learning skills remains.