Mobile Developer at a non-profit with 51-200 employees
Real User
Top 10
Nov 29, 2024
We use the Xamarin Platform since we have a .NET team that is familiar with .NET, and we appreciate the idea of shared code between platforms. We still use MVVM architecture, so we have loads of shared code in view models and services, which are all shared between our apps.
I need to use Visual Studio to use Xamarin. Xamarin is the platform, and Visual Studio is the IDE. I use Visual Studio 17.6.2 Community Edition for Mac. The organization I'm working for is a retail company. We have hundreds and hundreds of stores across multiple countries and regions in the Middle East and Asia. The app I develop, build, and enhance is used by about 30,000 to 40,000 store employees across all these stores. It's a store management app that has a huge amount of functionality built into it. It can do inventory management, store receiving, and customer management. We built the app using Xamarin.Forms. We not only have external people who use our app, but we also have in-house house people, especially store employees, who use the app, and that's where the MDM solution, Microsoft Intune, comes into play. Microsoft Intune is more for distributing the app internally to our store employees. It's a device management kind of thing. The apps automatically get upgraded without users being required to update the app. Intune does a whole lot of other things, like match policies or devices.
Xamarin Platform is used for base unit testing and the creation of new projects. The solution lets us apply the application tools for automation IDs, so we can test our unique testing. We can check step by step the automation ID by the codes or controls and all the functionality based.
We have so many applications on Xamarin Platform. We can use Xamarin native Developer, Xamarin.Android or Xamarin.iOS. It is a true native solution, and we can use the cross-platform framework using Xamarin.Forms. There are a lot of times when we have to code or complete beginning steps with the Ionic Framework. We can target the core native platform like Android, iOS, and Mac.
Senior Mobile Developer / Senior Xamarin Developer at Imparta
Real User
Aug 8, 2022
We use the Xamarin Platform for developing applications for businesses. I've worked and used the solution for property management companies, and the medical and education sector. We consume APIs and distribute them within app stores.
Software Engineer (Xamarin/MAUI Mobile, .NET APIs, Azure Cloud) at rseg
Real User
Aug 8, 2022
The strongest use case for this solution is developing cross-platform mobile apps. Most people are building both Android and iOS, and Xamarin lets you reduce your development efforts and build it from a single code base. You can build for Windows and Mac from it also, but most people are using it to build mobile apps.
Data Management Technical Lead - Project Manager at a computer software company with 51-200 employees
MSP
Nov 18, 2020
I used this solution for three years. I am not using this solution anymore, but I had Visual Studio and Xamarin installed — we were using components of Xamarin. We were trying to integrate some PSPDFKit functionality. We wanted to open up a PDF document to the last page that the person opened it. If it was a five-page document and they opened it on page two and then when they closed it, they wanted it to open back up to the page where they left off. They were trying to get the PDF to be sticky.
Software Development Lead at a tech services company with 51-200 employees
Real User
May 28, 2018
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.
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.
Manager Mobile Software Development at SEAMGEN, LLC
Real User
May 28, 2018
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.
Technical Architect at a tech services company with 10,001+ employees
Real User
May 28, 2018
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.
C#/Xamarin/Mobile Technical Lead at a tech vendor with 1-10 employees
Real User
May 23, 2018
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.
Technical Consultant at a tech services company with 1,001-5,000 employees
Consultant
May 23, 2018
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.
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.
Xamarin is an open-source platform for developing modern and performant applications for iOS, Android, and Windows using.NET. Xamarin is an abstraction layer that manages how shared code is communicated to the platform's underlying code. Xamarin is for developers with the two following goals:
Cross-platform sharing of code, tests, and business logic.
Writing cross-platform apps in C# with Visual Studio.
Xamarin allows developers to share an average of 90% of their program across platforms....
We use the Xamarin Platform since we have a .NET team that is familiar with .NET, and we appreciate the idea of shared code between platforms. We still use MVVM architecture, so we have loads of shared code in view models and services, which are all shared between our apps.
We use the product to build Android, iOS, and Windows mobile applications.
Primarily, I use it to develop mobile applications for both Android and iOS.
I need to use Visual Studio to use Xamarin. Xamarin is the platform, and Visual Studio is the IDE. I use Visual Studio 17.6.2 Community Edition for Mac. The organization I'm working for is a retail company. We have hundreds and hundreds of stores across multiple countries and regions in the Middle East and Asia. The app I develop, build, and enhance is used by about 30,000 to 40,000 store employees across all these stores. It's a store management app that has a huge amount of functionality built into it. It can do inventory management, store receiving, and customer management. We built the app using Xamarin.Forms. We not only have external people who use our app, but we also have in-house house people, especially store employees, who use the app, and that's where the MDM solution, Microsoft Intune, comes into play. Microsoft Intune is more for distributing the app internally to our store employees. It's a device management kind of thing. The apps automatically get upgraded without users being required to update the app. Intune does a whole lot of other things, like match policies or devices.
We use the solution for inventory management in our warehouse and also for unbound deliveries.
Xamarin is a framework for creating mobile applications. It can be deployed on any device for mobile app development. I am a user of this solution.
Xamarin Platform is used for base unit testing and the creation of new projects. The solution lets us apply the application tools for automation IDs, so we can test our unique testing. We can check step by step the automation ID by the codes or controls and all the functionality based.
I am using the Xamarin Platform because I am using Visual Studio or Xamarin Studio.
We have so many applications on Xamarin Platform. We can use Xamarin native Developer, Xamarin.Android or Xamarin.iOS. It is a true native solution, and we can use the cross-platform framework using Xamarin.Forms. There are a lot of times when we have to code or complete beginning steps with the Ionic Framework. We can target the core native platform like Android, iOS, and Mac.
We use this solution mainly for mobile app development.
We use the Xamarin Platform for developing applications for businesses. I've worked and used the solution for property management companies, and the medical and education sector. We consume APIs and distribute them within app stores.
The strongest use case for this solution is developing cross-platform mobile apps. Most people are building both Android and iOS, and Xamarin lets you reduce your development efforts and build it from a single code base. You can build for Windows and Mac from it also, but most people are using it to build mobile apps.
Xamarin Platform is being used for building applications. For example, shopping and e-commerce applications.
I used this solution for three years. I am not using this solution anymore, but I had Visual Studio and Xamarin installed — we were using components of Xamarin. We were trying to integrate some PSPDFKit functionality. We wanted to open up a PDF document to the last page that the person opened it. If it was a five-page document and they opened it on page two and then when they closed it, they wanted it to open back up to the page where they left off. They were trying to get the PDF to be sticky.
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 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.
Our primary use case is to build high performance mobile applications and bring about maximum code sharing between different platforms.
We use this framework when the requirements for mobile application development include different platforms.
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.
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 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.
I use Xamarin.Forms to develop mobile applications, which basically have the same functionality and cross-platform.
Mobile applications for our music streaming service.
The main reason for use is productivity, time gain, and code reuse.
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.
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.
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.