Evaluating Porting Efforts with Xamarin Mobility Scanner

| by Abel Avram Follow 7 Followers on Jun 25, 2013. Estimated reading time: 1 minute |

A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. Learn more about our new features.

Xamarin has announced the availability of Xamarin Mobility Scanner, a free online service for scanning .NET libraries in order to evaluate the effort needed to port them to Android, iOS, Windows Phone and Windows Store.

The service is useful to companies interested in porting their .NET applications to the three most important mobile platforms using Xamarin’s cross platform solution. The service iterates through all the methods found in .exe or .dll files provided, listing those for which there was no corresponding cross-platform method.

We have tried the service with two projects: JSON.NET, a .NET-JSON serializer with little GUI code, and Windows XP Snipping Tool, a small GUI intensive .NET tool. The result were:



98% for Android means that 98% of JSON.NET code is ready for Android. The missing 2% represent types depending on incompatible methods. It is interesting to notice that Windows Store and Windows Phone have lower percentages of code ready to be ported than Android and iOS.

Windows XP Snipping Tool


The barrels are pretty empty in this case, the smaller number of compatible methods being expected considering that this application is GUI intensive and Xamarin helps building the business logic of an application, the UI having to be developed separately for each platform.

The report includes the listing of all the incompatible methods that are not available on all 4 platforms, and all the methods calling them. The service also computes the amount of saved time in case of porting the application instead of rewriting it, without saying what formula it uses. Perhaps it multiplies the number of compatible methods found with a certain number of minutes considered necessary on average per method.

According to Xamarin, the binaries are not uploaded to Xamarin but rather evaluated locally in the browser. But the results of the analysis – the name and the number of incompatible methods – is sent to their website.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you