Develop for Android with Scala(code.google.com)
code.google.com
Develop for Android with Scala
http://code.google.com/p/scalaforandroid/
8 comments
I really love my Droid, and generally find Android to be a fairly well-designed SDK, but I also find working in Java really annoying. One of my good friends took the time to make it really easy to develop for Android using Scala instead. Since I know that we have a lot of Android users in these forums who are working on various apps, I thought that this might make the whole experience more pleasant.
Last year I submitted a patch to Dalvik which adds support for JNI in Scala. So Scala calling C (via the Android NDK) should now work in all recent versions of Android!
Cool! Do you know if this ads much/anything to the apk runtime size? The documentation seems a little bit scarce at the moment.
I need to get around to doing up Hecl for Android 'nicely'.
I need to get around to doing up Hecl for Android 'nicely'.
I used it to create a hello world app that clocks in at 18K.
I did a hello-world in Scala for Android (without this toolkit) shrinking it with proguard and the apk increased by 800kbyte.
Installing on a real device or the emulator is noticeable slower.
Installing on a real device or the emulator is noticeable slower.
You should be able to get the final size to less than 100kb, I can't remember exactly what I ended up with using Proguard but I think it was 30-40kb. It should manage to remove virtually all the Scala library code as hardly any of it would be used.
I added a little more info to the AFS home page.
IT includes a proguard.jar file which I assume is used to remove unnecessary classes from your final application. I managed to get Scala working with Android a while ago by following online guides (a lot more hassle than this looks to be!) and I used proguard for this purpose.
It took me forever to get it working for another app, and after I got it working, I decided to start this project, which makes things a lot easier since it just works.
How is the performance compared to straight Java?
I know the Clojure on Android project is at the moment, slower due to the functional nature of the language. Apparently the Dalvik garbage collector has to work overtime cleaning up because of the emphasis on creating new objects rather than mutating existing ones.
> I know the Clojure on Android project is at the moment, slower due to the functional nature of the language.
There are two things that can hurt performance for functional languages on top of the Java VMs ... the lack of TCO and the mapping of a type-system that's too different to be mapped efficiently.
In Clojure though what hurts is its dynamic nature, but you can go a long way by using type-annotations when you discover clear bottlenecks.
There are two things that can hurt performance for functional languages on top of the Java VMs ... the lack of TCO and the mapping of a type-system that's too different to be mapped efficiently.
In Clojure though what hurts is its dynamic nature, but you can go a long way by using type-annotations when you discover clear bottlenecks.
Is there any reason that the Dalvik VM shouldn't get TCO even if the JVM doesn't? I read somewhere that implementing TCO would necessitate a change in the bytcode and the jvm guys didnt ant to do this to break backward compatibility.
N.B: I haven't investigated the Dalvik VM and/or the Android ecosystem in any great detail, so this might be afoolish question,but any answers appreciated.
N.B: I haven't investigated the Dalvik VM and/or the Android ecosystem in any great detail, so this might be afoolish question,but any answers appreciated.
You can write Java-like code in Scala that compiles down to nearly identical bytecode to the Java version. If you're not using any primitives it will be 100% as fast.
If you write idiomatic Scala code, or use many primitives in Java code, the performance of Scala becomes relatively worse. Every first-class function you use turns into the equivalent of a new class and object at runtime, and the immutable data structures are slower than their Java equivalents.
I'm not sure how the performance delta differs between the JVM and Android's Dalvik VM. It may be that Dalvik's lack of JIT or less efficient garbage collector makes the Scala performance penalty bigger on Android. I would be interested in seeing some benchmarks.
If you write idiomatic Scala code, or use many primitives in Java code, the performance of Scala becomes relatively worse. Every first-class function you use turns into the equivalent of a new class and object at runtime, and the immutable data structures are slower than their Java equivalents.
I'm not sure how the performance delta differs between the JVM and Android's Dalvik VM. It may be that Dalvik's lack of JIT or less efficient garbage collector makes the Scala performance penalty bigger on Android. I would be interested in seeing some benchmarks.
I have one app in the market that uses it and it runs great.
Cool! Which one, out of curiosity?
Nice. I looked into using Scala for an Android app a few months ago, and the number of moving parts involved to get "Hello World" working scared me off. Automating that makes it less scary, so I am glad to see this.
I wish I could write my Android apps in Haskell instead, though. Scala just isn't quite as nice.
I wish I could write my Android apps in Haskell instead, though. Scala just isn't quite as nice.
Any Android OpenGL bindings for Scala? I would like to try some 3D stuff with it. The first time I tried 3D stuff on Android, I didn't like the fact that I had to write ~70 lines of Java code just to get a blank black screen
This goes up here and now I'm so annoyed at myself for not getting better directions to the Friendly Toast for the Scala talk on Android SDK.
Wow. First place for Scala. The world is becoming a better place!