Scripting Your Android Device

One of the issues that arose when Apple released the iPhone SDK earlier this year was the restriction on language interpreters:

No interpreted code may be downloaded and used in an Application except for code that is interpreted and run by Apple’s Published APIs and builtin interpreter(s)…An Application may not itself install or launch other executable code by any means, including without limitation through the use of a plug-in architecture, calling other frameworks, other APIs or otherwise.

Presumably, these terms are in place for security reasons — Apple and AT&T may be worried that un-vetted code might corrupt phones, consume large amounts of bandwidth, etc.

To date, Android has no such restriction, and if it will indeed be released as open source, it may be difficult for it to ever have such a restriction. Moreover, the Dalvik VM can be used with Java scripting languages. Today, we’ll take a peek at one such scripting language, discuss what languages may or may not work, and review the ramifications of scripting on the device.

My all-time favorite Java scripting language is Beanshell. To some extent, Beanshell was Groovy before Groovy. It gives you Java-compatible syntax with implicit typing and no compilation required. And, it isn’t all that big of a JAR to include — 143KB for the core.

To use Beanshell with Android, download the bsh-core.jar file, put it in a /lib folder in your project, and adjust your Eclipse settings or Ant script to reference that JAR during compilation and packaging. Note: I haven’t tried any of the add-on JARs for Beanshell — more on this below.

For example, here is a snippet of an Ant script that shows compiling a project and incorporating the Beanshell JAR in the build:

[sourcecode language=”xml”]


From there, using Beanshell on Android is no different than using Beanshell in any other Java environment:

  1. Create an instance of the Beanshell Interpreter class
  2. Set any “globals” for the script’s use via Interpreter#set()
  3. Call Interpreter#eval() to run the script and, optionally, get the result of the last statement

For example, here is the XML layout for the world’s smallest Beanshell IDE:

[sourcecode language=”xml”]



  1. Nice – Article

    You could incorporate this into your book to easily test out examples on the emulator.

    Your book is very well done.

  2. @ecompositor

    One limitation of scripting is that you can’t register a script in AndroidManifest.xml. And you can’t script layout XML files, resources, or anything else that gets packaged in the APK. So, you always need some Java code as the entry points into your application (e.g., your activity) and probably some other files as well. You can’t create an Android application that is 100% scripted, at least with the current frameworks at our disposal.

    While I will probably add a chapter on scripting to an Android book (possibly the Advanced Android one I have on the drawing board), I am a little hesitant to make it the foundation of all the examples, particularly in the current book.

    And thanks for the feedback on the article and book!

  3. Maybe there should be, or Android is already on top of it, a program or company that validates a new program/game/app/etc. before a user can dl it so the user knows it’s gonna be safe

  4. @Phil:

    My hope is that it’s more of a “seal of approval” vs. the Apple-style “it only runs if *we* say it runs”. Prospective buyers/downloaders can look for the seal of approval and make their decision based upon whether it’s there or not.

  5. I’m hoping for the same thing. A “plays nice with other apps” type sticker. Lets people feel comfortable downloading or installing onto a device. The term open source scares people a little bit and that would go a long way to calm fears. Not required by any means, just looks good if Google and the OHA say it’s A-OK.

  6. Nice example, I’m fond of BeanShell too. Of course with BeanShell on Android 1.0 you’ve got an interpreted interpreter. I wonder if pnuts would work?

    Good luck with the book.

  7. @Mr. Burnette

    From their FAQ: “Pnuts runs with on-the-fly bytecode compiler by default.” A Dalvik-aware Pnuts might work, but I suspect otherwise it’ll try executing ordinary Java bytecodes on Dalvik and run into issues.

    I think most Java scripting languages went this route (Jython, Groovy, JRuby, etc.), which may limit one’s options in the near term. That’s one of the reasons I went with Beanshell, figuring its execute-off-an-AST approach might well hold up on Android.

    “Good luck with the book.”


  8. Great example! I’ve made a few changes on mine to support 1.5 ‘droid, but as is the promise of Java, the code still runs on the new platform without major changes. I’m trying myself to put together some nice use cases for scripting language use on the platform.

  9. that’s enough. you can expand on your…

    attention getter with a good sub-headline after you have your visitors’ attention.note: be very careful that your wording doesn’t create a “double meaning” or something you “don’t” want to say. check this very closely.3. try using a question in …

Comments are closed.