Android for .NET Developers2

Posted on Updated on

Image result for androidAndroid for .NET Developers

The work of a Mono-based Android application goes through four stages: preparing assets from Android asset records into .NET-perfect asset documents; making of the .NET code; handling of the .NET code to make Java wrappers; and last bundling of the Android executable.

As I would see it, the essential explanation behind utilizing Mono for Android lives in the likelihood of a speedier startup time as you can remain in Visual Studio and write in C#. Be that as it may, the last application is somewhat bigger in light of the additional Mono runtime. For an Android application, size might be an issue substantially more than for an iOS or Windows Phone application on account of the extensive variety of various gadgets out there with extremely constrained memory abilities.

Another justifiable reason explanation behind going Mono is that you can reuse some code over numerous portable stages. In the event that you need an application for iOS, Android, and even Windows Phone, it’s feasible that you can reuse some code.

Note, however, that this last point, while wonderful, is very less engaging than it might sound at first. The code you can sensibly reuse in a Mono-based arrangement of portable applications is just the business rationale code you keep running on a gadget. The presentation layer of Mono-based Android applications should in any case nearly mirror the reasoning and conduct of Android exercises. You should know this keeping in mind the end goal to successfully compose Mono-based Android applications. (Also, similar remains constant for Mono-based iOS applications.) Making feeling of the presentation rationale of portable stages is the hardest piece of composing versatile applications.

Another alternative for composing Android applications is PhoneGap (see An application worked against the PhoneGap structure is a great customer side Web application made of HTML5 pages utilizing CSS and JavaScript. You compose and test the application inside your most loved advancement stage, and utilizing your most loved devices. For instance, you can utilize Visual Studio or maybe JetBrains’ WebStorm or whatever other content tool for the HTML pages and JavaScript rationale. Once the Web center is prepared, however, you have the issue of bundling that into a genuine Android application. You require an IDE for that like Eclipse or JetBrains’ IntelliJ IDEA. eOr, you can influence the PhoneGap Build benefit (see and transfer your application to the administration for bundling.

In the event that you decide on doing everything independent from anyone else, then you wind up with a plain Android extend in an IDE that backings Android advancement. Since the whole application is HTML and JavaScript, however, for this situation, your presentation to Java and show records is insignificant, in spite of the fact that not invalid.

Choosing the IDE

With everything taken into account, I incline toward composing Android applications the hard (not by any stretch of the imagination) way, utilizing Java, Android SDK, and an IDE of decision. Be that as it may, which IDE? There are two vital IDEs for Android: Eclipse and JetBrains’ IntelliJ IDEA.


For more details and queries please feel free to email, visit or call us. Wishing you the very best for all your future endeavors.
Helpline: 9814666333, 8699444666

Please fill the form and we shall contact you soon.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s