Is MonoDroid worth the effort?

Having finished and successfully published my first iPhone application using MonoTouch, I am now looking for an Android version of the same application.

MonoTouch has been very helpful to me since I still think that Objective-C is crazy to read and write (especially on German keyboards). So C # was a good alternative.

In Android, Java is the main development language from what I know. Since Java is much closer to C # than Objective-C, I doubt whether I really need to add an extra β€œlayer” of MonoDroid or just use regular Java.

My question is:

From your experience, should you use MonoDroid or could you make your next project directly with Java?

Update 1:

After a tip from @Dani, I found out that there is already a similar question and answer on p.se.com . Should I remove or close this question or ask the administrator to do?

+4
source share
2 answers

If you are developing the same application for Monodroid, then this will probably make sense, since you will have to use most of your existing code and just overwrite the user interface layer, as well as any code for a specific platform.

+4
source

Recently, I was also interested in this issue and wrote in this article . It reveals almost all the pros and cons that I encountered when developing my first MonoDroid application.

+1
source

All Articles