As the author of the article on SISC, I looked int ASE. The emphasis, as far as I can see, on the ASE is on 'scripting', running scripts to access certain parts of the android os. Which parts of the OS depends on the interfaces the ASE projects implements for the respective scripting languages to connect to. So far, I don't think the ASE project is focusing too much on the interactive elements (in android speak, 'Activities') of Android, those elements that users/developers think of as part of the 'app'. So, at the moment, ASE isn't really about building apps, but allowing scripting functionality to apps. Using JRuby or in this case SISC Scheme outside of the ASE environment could lead to full Android apps. (Hopefully)