How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
We develop Model X for sports and tourism and for Android and iPhone sport.
Xamarin helped us to develop a cross platform mobile app with less time and resources.
We have been using Xamarin for enterprise mobile application development. Primarily, we are targeting iPhone devices. This field mobility application helps end users to perform their duties and view 360 information about the work to be performed.
The primary use case at Seamgen for the Xamarin platform is to create forms or data-driven apps that utilize mostly stock UI components and benefit greatly by sharing a common core software layer for data processing and handling.
We use Xamarin almost exclusively for development of native mobile applications, even when single platform. The development hardware that we use are MacBook Pros with 16GB RAM and min 500GB SSDs. We run Windows 10 in a Boot Camp partition and virtualized using parallels. We have Xcode installed on the iOS partition and Visual Studio 2017 installed on both Windows and Mac partitions, along with Android SDK and NDK. We use Xamarin.Android and Xamarin.iOS for apps with a complex UI, and use Xamarin.Forms where applicable.
We use this framework when the requirements for mobile application development include different platforms.
Our primary use case is to build high performance mobile applications and bring about maximum code sharing between different platforms.
We mainly build mobile solutions for enterprises. In most of the cases, it does require a lot of complex domain knowledge and multiple integrations with various internal systems, pretty often legacy ones. We decided to work with Xamarin, since it does give us a lot of advantages compared to fully native solutions, which use Java or Swift/Objective-C. First, it allows us to reuse our knowledge of C# and .NET Framework. Next, since .NET and Java are the most common choices for enterprise platforms, it allows us to reuse some parts of business logic without the need to re-write/port them. Then, there is the possibility to apply well-known MVVM patterns to both Android and iOS targeting apps with reuse of up to 70% codebase between platforms, not to mention automated testing possibilities.
I use Xamarin.Forms to develop mobile applications, which basically have the same functionality and cross-platform.
Mobile applications for our music streaming service.
Xamarin provides two ways to build great native apps: Xamarin Native and Xamarin.Forms. We used Xamarin.Forms on many of our solution platforms, but it also can be used on complicated scenarios (with a lot of business logic code), like product configurator apps.
In most cases, I develop apps for iOS and Android, but there are some rare cases that include UWP platform. My environment includes a Windows 10 PC with VS 2017 and a Mac mini with VS for Mac.
The main reason for use is productivity, time gain, and code reuse.
Let’s take an example of a simple restaurant App which needs to be developed for each platform (iOS, Android, Mac, and Windows). Xamarin gives you the power to produce a quick proof of concept where you can use Xamarin.Forms and have your app ready within some days for each platform, using only one Xamarin developer. Otherwise, you need different native developers to have your app developed for each Platform.