Following my piece on different approaches to building the user interface in cross-platform frameworks, twitter user Sam Hogarth pointed me to the PropertyCross project. This implements a non-trivial application in 8 different cross-platform tools, covering Android, iOS and Windows Phone. Note that only four of the frameworks support Windows Phone.
Using the pie charts presented for each framework, I was able to order them by percentage of shared code as follows:
1= Adobe AIR (100%), JQTouch (100%) , RhoMobile (100%), Sencha Touch (100%)
5. Appcelerator Titanium (around 90%)
6. JQuery Mobile (around 80%)
7. Xamarin (around 40%)
8. Native (0%)
A couple of notes. Of the 100% frameworks, three do not support Windows Phone, and the one which does (Rhomobile) seems to be a bit broken on Windows Phone, judging by the screenshots. The Property Details and Favourites pages do not render properly.
You would get more code sharing with Xamarin if you only supported two rather than three platforms. That is logical: since it does not abstract the GUI.
In most cases (not Rhomobile) it is striking how different Windows Phone appears versus iOS and Android, even with jQuery Mobile which uses HTML5.