Code Sharing by Xamarin

Xamarin provides a code sharing technique throughout all the devices. You just need to write a code once and you can use that code throughout the project.

There are basically three types of code sharing technique provided the the Xamarin platform.

1. Shared Code
2. Portable Class Library

The goal of a code-sharing strategy is to support the architecture shown in this diagram, where a single codebase can be utilized by multiple platforms.

Basic reasons of using Xamarin

Xamarin is a  new emerging technology for the cross platform as well as the native mobile applications.It provides the native user interface by the use of C# language as provide by the android studio for android application using java and the XCode for ios and iphone application using objective C/swift language.

Why Xamarin

Today mobile application development has been growing exponentially because of the huge consumer reachability in mobility. This has created ocean full of opportunity for companies and developers to join this mobile revolution. We want to reach as many as possible consumer which means inclusion of these three platform at least: Android, IOS, Windows.

We all know the dominance and popularity of Native which highly overwhelm HTML apps. Developing native app for major three platforms will not be cost effective as it will require java developer for android, objective-c/swift developer for IOS and .NET developer for windows and respective QA and extra resources.

What is Xamarin

When considering how to build iOS and Android applications, many people think that the native languages, Objective-C, Swift, and Java, are the only choice. However, over the past few years, an entire new ecosystem of platforms for building mobile applications has emerged.

Xamarin is unique in this space by offering a single language – C#, class library, and runtime that works across all three mobile platforms of iOS, Android, and Windows Phone (Windows Phone’s native language is already C#), while still compiling native (non-interpreted) applications that are performant enough even for demanding games.

Each of these platforms has a different feature set and each varies in its ability to write native applications – that is, applications that compile down to native code and that interop fluently with the underlying Java subsystem. For example, some platforms only allow apps to be built in HTML and JavaScript, whereas some are very low-level and only allow C/C++ code. Some platforms don’t even utilize the native control toolkit.