Xamarin docs; Geofencing; TouchDraw code reuse

The Xamarin docs team have had a massive docs push, with lots of new content around Cross Platform development, Android and iOS, including recipes.

September is now in full swing, and you’ve got homework. The Xamarin Developer Center has added mounds of amazing new material to our portal, and we can’t wait for you to start reading!

Worth a read for anyone using MonoTouch or Mono for Android.


Kevin McMahon has a cool article up on GeoFencing in iOS. Geofencing is where you tell the phone to alert you (in code) when you enter or exit a location - latitude/longitude/radius - which is how things like Reminders work to tell you "Oh, you just left work, remember to pick up milk".

To create contextually aware apps, information about surroundings needs to be obtained, and one of the main ways of accomplishing this is to leverage 'geofences': virtual perimeters around real-world locations. The ability to create and monitor geofenced regions was recently added to iOS, and this article will show you just how easy it is to integrate geofencing into your location-aware apps.

The code looks simple enough to port to MonoTouch in a very short amount of time.


Jon Lipsky has updated his code reuse stats for TouchDraw. Touchdraw is on iPad, Mac and Android, and shared code between MonoTouch, MonoMac and Mono for Android. Very impressive that he's getting around 70% shared code.

At a first glance, it seems like the Android version requires quite a bit less code than the iPad version; however the statistics don't tell the whole story. What's not accounted for in the numbers is all of the things (layouts, menus, etc...) that is managed in code in the iPad version vs managed via resource files in Android.