This article explains why I decided to create a new project, and also what I did differently for this new Android app.

First of all, the name [...]]]> On Tuesday 21st of December 2010, I officially launched ReGalAndroid, the follow up of G2Android, aiming at providing G3 and Piwigo support.

This article explains why I decided to create a new project, and also what I did differently for this new Android app.

Why creating a new project ?

First of all, the name of the app (g2android) did not reflect what I wanted it to be: I wanted it not to be specific to a gallery type (G2) but also compatible with G3 and Piwigo.
In the android world, an app is defined by its package name; since I wanted to change from net.dahanne.android.g2android to the new name net.dahanne.android.regalandroid I had to create a new app.
Sure, I could have keep on using the old package name, but it did not make sense, and also I wanted to start refactoring the app modularizing it.

Modularizing an Android app, using maven-android-plugin

In G2Android, one of the things that frustrated me most was the way it was built : it had dependencies on libraries (jars) not part of the android runtime. So I had to include them in a lib directory; adding them to the classpath so that the Android Developer tools knew that G2Android needed them.
Another problem was the modularity of the application : the Gallery2 client API code was mixed with the Android UI code; it could become a nightmare for testing, as for plain Junit test cases, I had to remove the android.jar lib from my classpath (and Android integration testing was not an option as it takes really too long to launch; and does not make sense to test an HTTP client api…)
Starting ReGalAndroid, the first thing I did was modularizing the application :

• one standard jar maven project for the commons classes (Pictures, Albums, etc..) with its regular Junit tests

• one standard jar maven project for each gallery client java api (one for G2 extracted from g2android, and 2 new ones, one for G3 from scratch, and one for Piwigo extracted from Jiwigo, an existing Java Swing client for Piwigo) with their regular Junit tests

• one android maven project with only android related classes, this project heavily depends on the common module and the 3 gallery implementations; this has been possible thanks to the maven android plugin

To ease the process inside Eclipse, you can use Maven Integration for Android Development Tools , it will allow you to launch your Android application from the IDE, just the same as before.

This way, I am now able to test the remote API implementations independently of the main Android app; and also if someone wants to reuse those implementations for any other Java projects, he can just check out those plain java projects.

Logging an android app using slf4j-android

If your Android application depends on plain java projects; those projects certainly do not use Android logging framework.

So if you want to log all your modules in your android app, you can use slf4j : this is meta API where you can choose at compile time which logging API you will use.

For example, in all the logged classes of ReGalAndroid, I’m depending on org.slf4j.Logger and org.slf4j.LoggerFactory , even in the Android module.

But in my maven dependencies; I tell my android module to depend on slf4j-android :

<dependency>
<groupid>org.slf4j</groupid>
<artifactid>slf4j-android</artifactid>
<version>1.6.1-RC1</version>
<type>jar</type>
<scope>compile</scope>
</dependency>

That way, each call to LoggerFactory.getLogger(My.class)  in any of my modules will be wrapped to the android.util.log APIs

Cool thing is, if anyone wants to use any of the remote gallery implementations (G2, G3 or Piwigo client) in its Java app, he will be able to use Log4J or logback, or any other slf4j bridge he wants !

Moving from Google code to GitHub for code hosting

I’m quite satisfied with Google Code hosting; in fact I still use it as a wiki and a bug tracker; the truth, I wanted to become familiar with Git, to test its benefits.

As I was not starting from scratch, I wanted to be able to keep the history of my project

There is an easy way to do so in GitHub : create a new project, and then select ‘Importing a Subversion repo’; but unfortunately, it did not keep track of all my tags; so I chose to go with the manual way.

Export google code svn repo to a local git repo

I use this utility called svn2git, I had to check out from GitHub : svn2git

It is written in Ruby, so you have to make sure you have ruby and rubygems installed.

Then, according to your gems directory, you can run it :

/var/lib/gems/1.8/bin/svn2git https://g2android.googlecode.com/svn/  –verbose

All the svn tags are imported as git tags (git tag to check all the tags are there) but the authors are not imported (« (no author) author not found in authors.txt)

To manually change the authors name, I found the solution reading this post.

git filter-branch -f --env-filter "GIT_AUTHOR_NAME='Newname';  GIT_AUTHOR_EMAIL='newemail'; GIT_COMMITER_NAME='Newname';  GIT_COMMITTER_EMAIL='newemail';" HEAD </code>

From now on, you have a local git repo with all your code  from your SVN (including the tags !) in a local git repo; let’s share this one !

First create a new repo on github (using the web interface), then set your local repo as the origin :

git remote add origin git@github.com:anthonydahanne/ReGalAndroid.git

Finally, sync the local and remote , including the tags of the master branch :

git push origin master --tags

And youŕe done migrating from Google code SVN to GitHub !

Migrating your users from a previous android app to a new one

The problem when you’re creating a new android application to replace a previous one, is that the users having the old app installed on their phone will not be notified of the availability of the new one, since the package name of your new application (referenced in your AndroidManifest.xml file) is different :

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="net.dahanne.android.g2android" android:versionCode="15" android:versionName="1.6.3">
 
</manifest><manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="net.dahanne.android.regalandroid" android:versionCode="2" android:versionName="1.0.1">
</manifest>

Then the market you’re using (let’s say Android Market) is not aware of your new application replacing the previous one.

For the particular case of the migration from G2Android to ReGalAndroid, I first, during a month, advertised the new app on Twitter, and on the dedicated G2, G3 and Piwigo forums and websites; so that I could have some early adopters.

Then, in a second step, to accelerate the migration, I updated G2Android, with a new activity, launched by default on startup to tell the user that the application is not maintained anymore and that he should tap on the button to download the new application.
Here is the source code to redirect users from the old android app to the new one

At the time of writing this blog post, here are the statistics reported by Android market about both apps :

It means that the migration is quite slow, since many users still have the old application installed on their phones; I may remove the old app from the market in the next few months to make sure they do not use it anymore (please note that ReGalAndroid is also available via other markets and also via direct download)

The final words

The application is open source and if I receive many issues and functional requirements via the ReGalAndroid bug tracker (and I thank the users for that, it clearly influences the path the application is taking) I would love to see new contributors and committers add some code (see the ReGalAndroid github repository); because this is before all what makes the app

Here are the steps I followed to create this project.

Creating this project, I wanted a lightweight Java library, easily embeddable in an Android application  (G2Android not to name it, a [...]]]> I finally started a java library to implement Gallery3 REST remote API; g3-java-client (the name is not really original huh ?!)

Here are the steps I followed to create this project.

The technical choices

Creating this project, I wanted a lightweight Java library, easily embeddable in an Android application  (G2Android not to name it, a Gallery2 client for Android).

So I carefully designed my dependencies, in order to leverage Android already included libraries, such as Apache Http Client, org.json packages (by the way I initially wanted to use the jersey REST client API, but… I wanted to stay as close as possible to the Android platform…)

Finally, I’m developing this library using TDD, and Maven as a CI tool :  I want a really reliable library, for 2 reasons : because it is motivating to create quality code, and also it is really painful to test an android application (you have to start an emulator or AVD and deploy the binary each time you launch a test, and each of these steps can take time) .

The licensing

I chose GPL v3 to make sure my work remains open source and not used in any commercial projects.

I’m using maven-license-plugin to add the license to the source files.

The hosting

I chose Github, mainly because I wanted to get familiar with git : I have heard so many people happy using Git instead of SVN,  and I also wanted to be able to switch easily from trunk to another branch… sounded appealing to me !

To tag the sources, I decided to follow Ulrich’s steps using mvn-release-plugin to tag every new release (in French, but you can follow this link to have an equivalent article in English)

And to host the binaries, I created a maven repo out of  a new Github project following Chas’tutorial; sure I could have asked to host my project on Sonatype’s Nexus for Open Source Software, but as the project is actually really young, I prefer to use my own repo; I guess later on I’ll switch to this better solution.

The commands used

If I had to initialize the workspace from another computer, I would type the following commands :

mkdir g3-java-client
git clone git@github.com:anthonydahanne/g3-java-client.git
cd g3-java-client/
#to make sure everything (compilation, testing) is ok
mvn clean install
#to add the license header to the source files
mvn license:check
mvn license:format
#to commit the changes to github
git commit -a -m 'commit message'
git push origin master
#to release a new version  (be careful there is no file named release.properties at the root of the project)
mvn release:prepare

We just added the license info, committed the snapshot version , committed the stable version and also created a new branch (mvn release:prepare)

Now, we can deploy it to a maven repo

#to deploy the current version to a repository on my local file system :
mvn -DaltDeploymentRepository=snapshot-repo::default::file:../../m2repo/snapshots clean deploy
#to commit this repo to github (I created this Github repo to serve as a maven repo http://github.com/anthonydahanne/m2repo)
cd ../../m2repo/snapshots
git commit -a -m 'new snapshot for g3-java-client'
git push origin master

Pretty clear and easy right ? (except the deploy phase…) all of this thanks to Maven and my pom configuration.

What’s next ?

First, finish implementing all the Gallery3 REST remote API commands; and then, create a new android project (G3Android ?!) to consume this library; using … maven-android-plugin of course !

or you can read it, Asynchronous [...]]]> Tonight I gave a presentation at Android Montreal about the AsyncTasks API, for the Android platform.
Although the main content was « said » during the presentation, you can download the support :

• Asynchronous Tasks with Android (OpenDocument format)
• Asynchronous Tasks with Android (PowerPoint format)
• Asynchronous Tasks with Android (PDF format)

or you can read it, Asynchronous Tasks with Android on slideshare.

If you want to compare the different ways to deal with multi threading on the android platform, you can also have a look at the project I created on Github, AsyncTasksDemo.
Also, you can have a look at the source code of G2Android, in this application I use a lot of AsyncTasks to be able to run worker threads fetching remote content over HTTP (you can particularly have a look at AddPhotosTask)
Many thanks to the Android Montreal volunteers for hosting my presentation! It’s a really nice event with bright developers !

References :

if you’re interested in the AsyncTask API, you MUST read those blog posts from Android developers :

• Painless threading, by Romain Guy
• Multithreading For Performance, by Gilles Debunne

As always, you can get more info going to the project web page : http://code.google.com/p/g2android/, and even download the new [...]]]> Here is the new stable release of G2Android, your favorite Gallery2 application for Android, and great new features are now available :

• new cache feature
• fullscreen navigation with gestures
• download full res. picture to sdcard

As always, you can get more info going to the project web page : http://code.google.com/p/g2android/, and even download the new version
So what’s next ? tweeting and sending email with photo url, shortcuts for full screen navigation, synchronization between views… well, expect a new version by the end of November !

Now, you can still see your albums and pictures, but you can also :

The ergonomy is not yet perfect, as you may have [...]]]> I’m writing this small post just to indicate that the new version of the open source Gallery2 client for the android platform, G2Android, is out !

Now, you can still see your albums and pictures, but you can also :

• upload photos
• create new albums

The ergonomy is not yet perfect, as you may have already noticed, even though almost everything is multi threaded (using AsyncTask), meaning the ui won’t freeze anymore; the next features will probably will allow the user to insert a photo to his gallery from every picture context on the android platform (declaring a « share image » intent)

Stay tuned !

This method is [...]]]> In this article, I invite the reader to discover the different methods to access http resources from the Android platform.
These methods can be adapted to access web services (using REST) or simply to download files !

First Method : getting an input stream given a simple url from Android using HttpURLConnection

This method is the most basic one : it allows you, using the basic HttpUrlConnection, ( contained in java.net) to get an InputStream from an Url :

private InputStream downloadUrl(String url) {
		HttpURLConnection con = null;
		URL url;
		InputStream is=null;
		try {
			url = new URL(url);
			con = (HttpURLConnection) url.openConnection();
			con.setReadTimeout(10000 /* milliseconds */);
			con.setConnectTimeout(15000 /* milliseconds */);
			con.setRequestMethod("GET");
			con.setDoInput(true);
			con.addRequestProperty("Referer", "http://blog.dahanne.net");
			// Start the query
			con.connect();
			is = con.getInputStream();
		}catch (IOException e) {
                        //handle the exception !
			e.printStackTrace();
		}
		return is;
 
	}

You can also use the Post method, sending data in the HTTP POST payload :

private InputStream downloadUrl(String url) {
                InputStream myInputStream =null;
		StringBuilder sb = new StringBuilder();
                //adding some data to send along with the request to the server
		sb.append("name=Anthony");
		URL url;
		try {
			url = new URL(url);
			HttpURLConnection conn = (HttpURLConnection) url.openConnection();
			conn.setDoOutput(true);
			conn.setRequestMethod("POST");
			OutputStreamWriter wr = new OutputStreamWriter(conn
					.getOutputStream());
                        // this is were we're adding post data to the request
                        wr.write(sb.toString());
			wr.flush();
			myInputStream = conn.getInputStream();
			wr.close();
		} catch (Exception e) {
                        //handle the exception !
			Log.d(TAG,e.getMessage());
		}
                return myInputStream;
}

But there are better ways to achieve that, using Apache HttpClient, included in android.jar (no need to add another jar, it’s included in android core)

Second Method : getting an input stream given a simple url from Android using HttpClient

Why is it a better to do it ? because the simpler, the better ! See by yourself :

public static InputStream getInputStreamFromUrl(String url) {
		InputStream content = null;
		try {
			HttpGet httpGet = new HttpGet(url);
			HttpClient httpclient = new DefaultHttpClient();
			// Execute HTTP Get Request
			HttpResponse response = httpclient.execute(httpGet);
			content = response.getEntity().getContent();
                } catch (Exception e) {
			//handle the exception !
		}
		return content;
}

But you maybe wondering if it’s still easy with HTTP Post method ? You won’t be deceived !

public static InputStream getInputStreamFromUrl(String url) {
		InputStream content = null;
		try {
          		HttpClient httpclient = new DefaultHttpClient();
			HttpPost httpPost = new HttpPost(url);
			List nameValuePairs = new ArrayList(1);
                        //this is where you add your data to the post method
                        nameValuePairs.add(new BasicNameValuePair(
			"name", "anthony"));
			httpPost.setEntity(new UrlEncodedFormEntity(nameValuePairs));
			// Execute HTTP Post Request
			HttpResponse response = httpclient.execute(httpPost);
			content = response.getEntity().getContent();
		        return content;
	        }
}

But what if you want to read a cookie from the response ? And how can you send a cookie back to the server for the next request ?

Reading / Sending a cookie along with the requests

Using Apache HttpClient, it’s easy to retrieve cookies ! Everything is in the headers after all !

[...]
Cookie sessionCookie =null;
HttpResponse response = httpclient.execute(httpPost);
Header[] allHeaders = response.getAllHeaders();
CookieOrigin origin = new CookieOrigin(host, port,path, false);
for (Header header : allHeaders) {
			List parse = cookieSpecBase.parse(header, origin);
			for (Cookie cookie : parse) {
				// THE cookie
				if (cookie.getName().equals(COOKIE_I_WAS_LOOKING_FOR)
						&& cookie.getValue() != null && cookie.getValue() != "") {
					sessionCookie = cookie;
				}
			}
}

To send a cookie along with your request, keep it simple :

HttpPost httpPost = new HttpPost(url);
CookieSpecBase cookieSpecBase = new BrowserCompatSpec();
List cookies = new ArrayList();
cookies.add(sessionCookie);
List cookieHeader = cookieSpecBase.formatCookies(cookies);
// Setting the cookie
httpPost.setHeader(cookieHeader.get(0));

What about the resulting InputStream ? You definitely want to transform it into a String or an Drawable (to set it to an ImageView for example !) don’t you ?

Converting the InputStream into a Drawable in Android

The Drawable class already handles that for you :

Drawable d = Drawable.createFromStream(myInputStream, "nameOfMyResource");

Converting the InputStream into a String in Android

This is some classic java stuff (don’t tell about how easier it is in Ruby.. I know … but hey ! Java SE7 at the rescue with NIO !!! maybe one day in 2010 ! )

BufferedReader rd = new BufferedReader(new InputStreamReader(myInputStreamToReadIntoAString), 4096);
String line;
StringBuilder sb =  new StringBuilder();
while ((line = rd.readLine()) != null) {
		sb.append(line);
}
rd.close();
String contentOfMyInputStream = sb.toString()
 
That's it folks ! If you have any other methods to achieve these goals, feel free to share them sending a comment !

During his talk, the speaker described the audience the future of a Java platform, because it is actually going to be there for a long time now. He mentioned [...]]]> Vous pouvez lire cet article en français sur le blog de valtech.

The Changing Nature of Enterprise Java Application Development, 9:00 – 9:45 by Adrian Colyer

During his talk, the speaker described the audience the future of a Java platform, because it is actually going to be there for a long time now.
He mentioned the dynamic languages compatible with the JVM : Groovy, JRuby, Scala, and Clojure.
He mainly focused on Groovy (which belongs to SpringSource by the way), even if he was not sure if whether JRuby or Groovy would win the « war of dynamic languages ».
For the web platform, he mentioned Grails, built on top of Groovy, Rails running on top of Ruby, and Lift built on top of Scala.
He finished his talk introducing OSGi and Spring DM; the future of enterpise is application may be in the cloud : easily to deploy and scale applications are to come.

The android runtime environment, 10:30 – 11:20, by Joerg Pleumann

The speaker first made an introduction to the Android system, as a platform competing windows mobile and palm.
More technically speaking, it is based on a Linux kernel (along with necessary drivers : display, camera, sound, etc…).
On top of it come the Android Runtime and libraries; the talk is about the Android Runtime and its Dalvik VM.
Dalvik VM : CPU between 250 and 500 MHz, RAM >=64 (equivalent to a 1999 PC), but low power consumption is critical.
The Dalvik VM is really efficient, using explicit registers to keep temporary values: the immediate benefit is the number of lines of the bytecode resulting from the DalvikVM compilation : nearly 30% less than a standard VM compilation.
A dex file (Dalvik Executable) contains several files, and is not compressed.
JNI is ready, a sdk for using JNI is about to come out in the next days; also an Android Debug Bridge is available from the beginning.
The core libraries
dalvik vm specific libraries : dalvik.*
java compatibility libraries : java.* and javax.*
and some apache libraries(mainly for http) : org.apache.*
The core libraries are partly taken from Apache Harmony (a JDK implementation by Apache), partly written from scratch; and some of them have been optimized (using JNI)
The core libraries are mostly compatible to a subset of J2SE 5.0.
JDBC 2.0 is supported, but the SQLite driver is limited., but one can use the alternative in android.database.sqlite which are better integrated.
To conclude with, with Android you can reuse your java knowledge and tools.

Android Application Model, 11:30 – 12:20, by Dominik Gruntz

4 main components :activities, services, content providers and broadcast receivers.
A single class, uses intents to communicate with the other activities; when you launch an activity, you can (or not) expect a result; if this is the case, the method onIntentResult will be called.
You can also define intent filters to describe the intents an activity can handle.
An intent specification is on its way : http://www.openintents.org
An application is packaged using an APK (Android package).
Every activity has a lifecycle containing 4 steps : new, running, paused, stopped, killed and the corresponding methods (onCreate, onStop etc..)
For each activity a new process (with a single thread) is created.
The Looper.loop() dispathes the actions to a queue.
If an activity does not conume events in 5sec, the system issue a warning message.
A service is running background and can communicate with an activity (in process if it’s the same application (APK)) or via AIDL.
Finally, a content provider is the only way to share date between Android applications; it can using SQLite, a file, or a remote storage.

Scalable Agile Web Development: REST meets JCR meets OSGI, by Michael Marth

JCR : JSR 270 for accessing content repository : located on a file or database; can be versioned; node ahave read/write group properties, etc…
Apache Sling is a web framework, on top of REST/Scripting (Ruby, Groovy, etc…)/OSGi(in this case Apache Felix Container, to switch on/off part of the frameework live)/JCR.
So basically Apache Sling allows the user to create/edit/read/update content in a restful manner (http methods), the data being created is then stored on the JCR repository, organized in a very similar WebUrlFriendly way (and then you can manipulate the data through rest or webdav and so on, thanks to JCR)
The demo was really smooth and interesting !

The charm of Mockito: Test Spies in action, 14:30 – 15:20, by Szczepan Faber

The speaker begins asking who uses JMock : 2 or 3 people among an audience of 60 people, half of the audience using EasyMock.
So let’s start with EasyMock : coding in TDD a dictionnary, (and its history) depending on a translator : the translator is mocked.
With easymock the speaker keeps it old fadhioned : createMock/expect/replay/assert/verify , (his test extends Assert) and then refactor a bit in the @Before and @After test methods, nothing special here.
Then Mockito : mock/when/assert/verify : it’s a lighter syntax indeeed!
Szczepan insisted on the fact that usually developers using easymock create replayAll and verifyAll methods called in the @After method; which make Easymok fail when many behaviours are attached.
The speaker uses BDD style template (given/when/then) in eclipse, when creating a test.
Mockito eases the use of a given/when/then syntax when writing a test.
Has good point of failure ?
The failure trace in mockito is linked to the source code and more explicit about the error, it does not whow internal classes exceptions
Mockito or mockito-like for python, flex, javascript, C++; there are mockito extensions
He concluded with : « Do TDD and write great tests with whatever tools that work for you »
May the force be with you !

Eclipse Galileo and JBoss Tools, 16:30 – 16:50, by Max Andersen

Galileo (3.5) is a huge release.
Must-sees : Eclipse Memory Analyser (to see which plugin consumes all the memory for example), using jmap
XML and XSL editor is really better.
P2 (eclipse update manager) works for real; you shouldn’t use dropins anymore (single zip files to unpackage in /plugins and /features), for offline installation plugins providers should suggest copies of the update site, then you may use P2 to explore these files, as if you were online).

Description of the new features in Java SE 7 : modularity, ?. operator, new API for java.io (Path, Asynchronous FileVisitor), [...]]]> The following sessions were given during Jazoon 09, on Wednesdaythe 24th of Ju ne 2009, vous pouvez lire la traduction en français sur le blog de Valtech

Danny Coward Keynote, 9:00 – 10:00

Java 7

Description of the new features in Java SE 7 : modularity, ?. operator, new API for java.io (Path, Asynchronous FileVisitor), http://openjdk.java.net/projects/jdk7

Java FX

The new version is 1.2, running on all OSes (even Linux and Solaris, a TV, some phones to come out), more UI components (skinnable with CSS) , new layouts, better performance; then Danny showed the audience some JavaFX applications : a pacman application, a video player, with some nice visual effects …

OSGi and Java Modularity, 10:30 – 11:20, by Peter Kriens

If you think your application is modular only by using the VM, well, think again…
You can’t hide interfaces in the classsloader, and if there are no enforcements of rules at runtime, it’s uselesse to try to make these interfaces secrets…
In OSGi, you can set secret interfaces (not exported) and also use MANIFESTs to explicitely specify exports.
With an OSGi bundle (a jar actually, with its MANIFEST), you can dynamically specify which others bundles it can depend on, if one of the bundle you depend on is no more available, OSGi will remove the dependency; then it will put it back when the bundle is available again.
The problem is : many implementations of modularity exist and JSR 294 do not specify a particular one … From a programmer point of view, you will have to choose between OSGi, Jigsaw, guice, the modularity implementation you want to use …

Next generation Wikis: Mixing Content-Oriented Applications with Wikis, 11:30 – 12:20, by Vincent Massol

Wiki 1.0 : just used for text
Wiki 2.0 : you can add everything : images, videos, comments, notes, etc.., the datas can be structured, unstructured or mashups (datas coming from everywhere) the wiki 2.0 is the excell… of the web !
After presenting a demo showing us the possibility in Xwiki to define in 10 minutes (knowing velocity or groovy syntax) an application hosted on the wiki, Vincent listed the Xwiki features and the new features to come : real time collaboration, mobile skin, social features and … merge of CMS and wikis.

JavaFX Rich Internet Applications connected to GlassFish Java EE 5 services, 16:00-16:20, by Ludovic Champenois – Sun Microsystems

First of all, Ludovic showed us the GlassFish v3 admin console (looks good !) and reminded us with REST (standard HTTP methods, resources, etc…), and the REST annotations in Java EE6.
Why ? because the example given during his demonstration is communicating with a JAX-RS Java EE6 application, hosted by Glassfish V3.
To test the REST application, you can simply use : curl -HAccept:application/xml http://localhost/domain, or use your browser or use Glassfish v3 Admin Backend Tester.
And then, down to the JavaFx application code, using Netbeans, only 15 lines of code are necessary to consume the REST service.
TO finish with, Ludovic showed us some other JavaFX demo applications.

JavaFX / Android: Competing technologies or the ideal partnership? , 16:30 – 16:50 by Mike Mannion and Andreas Hölzl

Presented as a theater play : 2 guys talking about phone technologies around a coffee : one is a JavaFX supporter, the other is an Android supporter.
They then compared a similar application (using Flickr, Lastfm, youtube web services): developed both for JavaFx and the Android Platform.
*UI : JavaFX needs UI designed by designers, Android defines it in an extermal layout XML file
*UI (2) : Android provides a richer API, providing a photo gallery for example, JavaFX does not…
*language : you have to learn JavaFX script for JavaFX, Android uses Java 5 API (with some restrictions…, for example it does not use AWT or Swing for graphics)
They also told us that Sun is not clearly decided about supporting Android : they said that they were thinking about it… but since then (a year ago) nothing came out !