What Features Would You Like To See In 1.1

We are already gearing to close 1.0 and are looking at the features we would like to get into 1.1 currently slated for May 2013. In that spirit we would love if you would take a few minutes to answer this quick survey.

Test It

One of the common questions we get for Codename One is regarding testability. Cross platform frameworks are notoriously hard to auto-test and so fail when you try to build more complex applications.
We see this as one of the most important areas in which we can innovate and leapfrog native OS environments by offering testing that is just as cross platform as Codename One is. We aren't just announcing our own unit testing API, we are announcing a fully integrated test recorder to auto-generate GUI tests for your applications and run them on the simulator.

We will also integrate this exact same testing framework into our build server to seamlessly test device support for you in the future.

In the video above you can see me going through the process of recording a test for the kitchen sink and then running it in the simulator.

I'm sure I'm going to get this question so I'll hit it right now before it comes up. No the tests are not JUnit compatible and we haven't used another well known testing framework. The main logic behind this is that tools such as JUnit rely on reflection to work since they use annotations or method invocation without an interface. This doesn't mesh well with Codename One's device targets so we chose to implement something of our own.
You would have to write most of the test cases for Codename One anyway since the API/functionality would be pretty different.

Codename One Benchmarked With Amazing Results

Steve Hannah who ported Codename One to Avian has just completed a set of benchmarks on Codename One's iOS performance putting Codename One's at 33% slower performance than native C and faster performance than Objective-C!
I won't spoil his research results so please read his full post here.

A small disclaimer is that the Objective-C benchmark is a bit heavy on the method/message calls which biases the benchmark in our favor. Method invocations in Codename One are naturally much faster than the equivalent Objective-C code due to the semantics of that language.