r/Xamarin • u/HadyElHady • Apr 05 '19
r/Xamarin • u/danysdragons • May 19 '20
Introducing .NET Multi-platform App UI (evolution of Xamarin Forms)
r/Xamarin • u/titan_khalil • Dec 06 '24
Facing Xamarin Sunset: Our journey migrating 600k users to Flutter
I'm a mobile dev lead who just wrapped up a massive migration project, and I thought sharing our experience might help others in the same boat.
The Challenge With Xamarin's support ending and our app serving 600k active users, we had to figure out how to migrate our entire codebase while keeping the lights on. Here's how we did it.
Our Approach: The TL;DR
Complete migration from Xamarin to Flutter
Parallel app strategy (kept both versions in stores)
User segmentation based on feature usage
Phased rollout over 1.5 years
Full UI/UX redesign along the way
The Strategy That Worked
Parallel App Development We maintained both Xamarin and Flutter versions in the stores simultaneously. This was crucial - it gave us a safety net and kept pressure low. Users could always fall back to the old app if needed.
User Segmentation We mapped all user groups based on feature usage and complexity:
Basic users (simple viewing/interaction features)
Standard feature users
Power users
Edge cases with custom configurations
Migration Waves Started with simplest use cases and gradually moved to complex ones. Each wave:
Forced specific user segments to migrate
Validated core functionality
Gathered feedback before moving to more complex users
Allowed us to fix issues before they affected everyone
Lessons Learned
Planning is Everything
Spend time mapping user segments
Document feature dependencies
Create clear success metrics
Don't rush the planning phase
Communication Strategy
Clear messaging about the migration timeline
In-app notifications about upcoming changes
Dedicated support channels for migration issues
Regular updates to all stakeholders
Technical Insights
Flutter's hot reload saved us countless hours
Cross-platform consistency improved significantly
Performance gains were substantial
Dev team morale improved with modern tooling
What Would We Do Differently?
Start user segmentation earlier
Build better analytics from day one
Document edge cases more thoroughly
Tools & Resources That Helped
Sentry
Automated E2E Tests + Widget tests
Feature flags
Questions? Happy to dive deeper into any aspect of our migration - whether it's technical details, project management, or specific challenges we faced. Drop your questions below!
r/Xamarin • u/BurkusCat • May 22 '19
Welcome to the Shell Era: Xamarin.Forms 4.0 Released | Xamarin Blog
r/Xamarin • u/prabakarinfo • Aug 06 '19
Free and beautiful XAML pages for Xamarin.Forms apps.
r/Xamarin • u/Ljosmyndun • Feb 05 '19
We worked with Xamarin for almost three years, this is what we learned:
r/Xamarin • u/ReactDOM • Jun 22 '19
Learn Xamarin from the best tutorials, courses & books
r/Xamarin • u/[deleted] • Jun 14 '19
Making Xamarin.Forms apps 'pretty'
What does everyone do to make their xamarin apps 'pretty'? My out of the box controls seem to be blocky and amateurish. I've seen some React Native apps and they look remarkable. I'm trying to figure out what I'm missing, and what I need to add it to make my Xamarin.Forms apps prettier.
r/Xamarin • u/haavamoa • Apr 06 '20
Xamarin.Forms UI library
Hi guys and happy easter! Hope your all doing well in these corona times.
I want to share a link to our UI library that our organization is using to develop apps with Xamarin.Forms.
We aim to provide simple to use and well documented controls and useful APIs. Everything is heavily based on supporting MVVM.
Feel free to start using it and we appreciate every feedback we get.
Much love for the community! ❤️
r/Xamarin • u/Qgsr • May 29 '21
I made a list of Xamarin & MAUI communities around the world
r/Xamarin • u/48K • Jul 12 '20
My Xamarin Journey: the Good, the Bad, and the Ugly
I've thought about writing this post for a while and I'm sure it won't win me any friends on this subreddit, but somebody might benefit from my experience and I will feel better getting it off my chest. I'm breaking up with Xamarin and I feel I owe it an explanation.
The Good
I've been writing C# for 15 years and using Xamarin for 7. I have created multi-million dollar products using Xamarin on Android and less successful ones on iOS (my fault not Xamarin's) . If you love C# above all else then this can be a good way to develop apps.
The Bad
I'm sure veteran Xamarin developers will recognise some of these:
Persistent IDE bugs. Crashes and compilation errors that disappear with a rebuild or restart are a daily hassle. This happens with other languages and IDEs, but more so with Xamarin I feel.
Compile errors can be very opaque, particularly those involving support libraries or native resources.
The form designers never work. Well, they might work once in a while, but as soon as the form gets complex or tries to reference some custom component or there's an IDE update you are straight back to source code. Don't get me started on the XCode XIB interop, which is probably Apple's fault, but is certainly our problem.
Compile times are long even for small apps and deployment is slow. This works against my hack-and-hope programming style.
Performance analysis is very temperamental and connections to instrumented applications come and go mercurially. A few years ago the analysis tool was premium, but that might have changed and things may have improved.
APK sizes are very large compared to their native counterparts. Even when the "linker" trims out unused parts of the .NET libraries it's impossible to get an APK under 10MB. This impacts start times on slow devices and increases the chance that background apps will be closed under memory pressure.
The Ugly
When you find yourself on the bleeding edge you may also trip over some of these:
Sometimes you just need to use a native library, but mapping complex native libraries is hard and is almost impossible to debug because of the opaque managed/native boundary even when the library is open source.
Native integration in general can be painful when large data sets have to be marshalled across the managed/native boundary. For instance, taking a camera image frame and passing it to a face recognition library typically requires the pixel data array to be copied.
I never got the hang of build system automation, but maybe things have improved since I looked last.
The availability of cool new support libraries always lags behind because of the mapping delay, this isn't a huge problem but it does give me FOMO.
System apps written in Xamarin are fiddly to test because Xamarin Studio refuses to deploy over the top of a system app even when the signatures match.
Conclusion
I continue to use Xamarin on an occasional basis for maintaining one of our core apps, but since narrowing our platform target to just Android I have switched all future development to Android Studio and Kotlin, which is nearly as expressive as C# (except for their generics implementation). Even if we needed to add support for iOS I would probably just start a parallel project in XCode / Swift. For me the multi-platform development experiment is over.
I am very grateful to the smart people who work on Xamarin and the .NET libraries and they have achieved a miracle given how complex the modern platform ecosystem is. It's just that the number of compromises involved has gone past what I can tolerate on a daily basis.
I always thought C# would be the language they buried me with, but some of these new fangled languages are worth considering especially if you are prepared to renounce the gospel of a single cross-platform solution.
r/Xamarin • u/rickrocks28 • Jul 10 '20
Why are very few companies doing xamarin development?
I always see flutter and react native being used to develop the apps. Though xamarin is really an awesome dev stack.. I wonder why very few companies are reluctant to adopt it.
r/Xamarin • u/Thaik • Jan 23 '20
Visual Studio Preview 16.5- HOT Reload, Custom Startup Tracing, XAML Document Outline: Available now
r/Xamarin • u/kroe761 • Mar 12 '19
When using Xamarin, what costs money?
I am playing with the idea of writing my an app, and i've always wanted to use Xamarin, but I thought you had to have a $2000+ MSDN license in order to do it. I just found out it's free, and am super excited to get started. But, is there anything when using Xamarin that you DON'T get without shelling out hundreds of $$, and if so, how important are those tools? Thanks!
r/Xamarin • u/OneLostOstrich • Mar 02 '21
Strategies for working around the "Xcode 12.3 Xamarin is currently selected in Preferences and is incompatible with the version of Xamarin.iOS being used"
FYI this expects that you're developing on a Mac.
If you're trying to install Xamarin & build a project but aren't running the latest MacOS you'll see this error since you can't use Xcode 12.4. Don't worry. You don't have to update your Mac to macOS 11 but you will need to download Xcode 12.4. You can download a version of Xcode 12.4 from here: https://developer.apple.com/services-account/download?path=/Developer_Tools/Xcode_12.4/Xcode_12.4.xip
Unzip it in another directory, rename it to Xcode-12.4.app and move it into /Applications folder next to the other version of Xcode that you're using.
You'll have two versions of Xcode, but they'll be sitting next to each other and that's not a problem.
In Visual Studio, go to the File menu and select Preferences.
Within Preferences, select Projects > SDK Locations > Apple and in the right for location, enter this path: /Applications/Xcode-12.4.app
Quit and restart Visual Studio.
Reload your project and build for iOS. It will launch in the Simulator.
I hope this helps someone.
Other options involve copying and renaming folders, but with this approach, you can still keep your current version of Xcode while you have a version of 12.4 installed which will not launch on any MacOS prior to Big Sur (11).
r/Xamarin • u/Astrophysics_is_cool • Aug 07 '20
What should I learn specifically about C# before starting?
I'm 14 and would like to start on Android application development early. I'm already familiar with C#, to the extent of understanding some of the concepts of OOP, but I'm still wondering where I should stop with C# and move onto learning how Xamarin works. I also know that I would need to learn XAML, so if I could also get an answer about what I should learn specifically about XAML, that would be pretty cool.
P.S - I apologize about my lack of terminology and ignorance, I've only started to grasp the early concepts of application development.
r/Xamarin • u/gandhiN • Jul 02 '20
Collection of top Xamarin Courses and Tutorials for Beginners
Made a collection of the best Xamarin tutorials that can be useful to learn Xamarin.
Sharing here so it can be useful for other fellow developers
r/Xamarin • u/robotorigami • Feb 04 '20
Why Does This All Feel So Unstable?
I recently started learning Xamarin at work to help rebuild our mobile applications. I'm 5 days in and I can't seem to get anything to work. I have my PC and my Mac Laptop and started reading about how it all works. Setup the provisioning profile on the Mac, update xcode, install Visual Studio for Mac, link the PC's Visual Studio to the Mac, all ready to go. First step, pairing to the Mac fails. Ok, looks like its a version mismatch, luckily VS has a link to update... this was the first failure. Ok, maybe I can just update Xamarin on the Mac, even though I just installed VS for Mac. Cant find a Xamarin installer that's not bundled with VS. Finally figure that out and now it's MTouch complaining. I setup the signing on my PC, but it wont let me find any provisioning profiles (yet it finds my Signing Identities no problem). I figure out I need to set it to Automatic Provisioning and pick a team. Seems like I need to do this quite frequently because my settings keep disappearing after restarting VS.
Once the version mismatches and provisioning were fixed I needed to update XCode from 13 to 13.1 because VS didn't like 13. But XCode wont update on my Mac. Another hour spent hunting this down and it turns out I need to set my clock back on the Mac to September 2019 for the updater to work. Huh?. XCode is updated now I think it will be smooth sailing from here.
I try to walk through some tutorials, and none of the tooling is the same. I guess I'm used to that by now, so I work my way through it. Then I go to build and get a "Cannot link assemblies" error due to a package that isn't supported, even though I was able to install it from Nuget no problem. Fix that, start creating a class library, but I clicked .NET Standard 2.1 instead of 2.0 which, again, lets me reference it, but doesn't build. Finally get all of that working, click run with the simulator and I get "Cannot install the app because the folder doesnt exist". That happened exactly one time. After trying again I finally get the simulator to pop up with an alert message that says "Failed to install the requested application" with no more info than that. StackOverflow seems to think it's a remote simulator issue so I disable that and nothing shows up at all. Then somewhere along the way I suddenly start getting a build error "The Target Framework Moniker is invalid" which returns zero useful google results. Luckily that just fixed itself magically.
Have any of you wonderful people had similar experiences with Xamarin? Am I just brain dead or is this not easy to work with? I really, really want to like this but it's very hard. I've been working as a developer for a very long time, I honestly don't remember the last time a technology has given me such headaches.
EDIT: I still don't have anything working. The simulator on the PC just shows a pinwheel. The simulator on the mac just shows an empty iPhone screen. I check the logs and it says "An error occurred, check the logs" which is where I am when I'm reading that message. It's eternally frustrating and I don't know how much sanity I have left at this point.
r/Xamarin • u/[deleted] • Oct 10 '19
Xamarin Forms - Sample projects in MVVM architecture. Hope it's helpful for new developers.
r/Xamarin • u/mycall • Aug 02 '19
AirNZClone - Awesome animation tricks in Xamarin.Forms
r/Xamarin • u/voyher22 • Feb 27 '22
[Rant] Xamarin iOS is shit. I really, really wish it weren't.
I've been using C#/.NET professionally since 2003, apart from a couple of stints in Java shops. I love C#, and think that C# + Visual Studio is the most productive combination of language and IDE I have ever encountered for both server-side and thick-client GUI development, with no equal. Usually I work in the field of high-performance trading systems.
That said, I have been doing a Xamarin Forms iOS app on the side for a couple of years as a favour for a friend, and..oh my god. It has probably been the most frustrating thing I've ever done in 30+ years of development. And that's saying something.
First off, it was the regular random errors, crashes and hangs in Visual Studio 2019 when building for no discernible reason. Then I found I could reliably hang VS just by trying to stop an in-progress compile (wtf? never had that in regular C# app dev). It got to the point where 40%+ of the time I try building, I would get some meaningless build error that might, or might not be from the Mac build host I have on the local network (which is not used for anything other than building this app I might add). I could have one build succeed, and a rebuild immediately after with no changes fail with some obscure error. Other times hitting F5 to build/debug would just disappear off into the ether after a while, with no feedback as to what's happening. Is it building slowly? Has it hung? Or failed? No idea. How on earth can one develop software in such an environment?
Honestly every time I open the solution after a few weeks or months of not touching it, I get a new, different error on compilation. The latest issue? I can no longer deploy to a device attached to my local Mac for debug/testing due to some signing issue. Why? Beats me. I tried manual signing after revoking and re-creating all certificates; that fails. I tried Automatic signing (VS is supposed to handle all that, right?). Nope; I get a 'No iOS signing identities match the specific provisioning profile'. Despite the fact that VS reports no issues in the iOS Bundle signing settings, and I've gone through the documented process 3+ times. And this isn't even to mention all the other build errors I've encountered over the last couple of years, which will sometimes magically resolve themselves quickly, other times seem to go away after restarts of VS/the Mac, and sometimes after just throwing my hands in the air and walking away for a day or two. This isn't how software development should be.
Honestly, I'm ready to give up and just redo the whole damn app in some other technology, because for as much as I love C#/VS, Xamarin iOS ABSOLUTELY SUCKS from an application build reliability perspective. I'm sure a lot of people at MS have worked hard on it, and no doubt Apple makes things very difficult by changing their tooling without a heads-up, so I hate to shit on all the hard effort that's no doubt gone into it. At the end of the day though, the product has to work for the user, right? And it JUST. DOESN'T. DO. THAT.
Oh, and if I hear another 'please provide an example that reproduces the problem' on submitting a bug report, I just might kill someone. Many of these problems don't show up on a simple sample app created from scratch, but do show up once you've invested so much time and effort that you can't easily start again from scratch elsewhere or extract bits into a sample that reproduces the problem. You know, once you've actually build something USEFUL.
EDIT: As a perfect example of the difference between the Xamarin sales pitch and day-to-day reality, Hot Reload sounds great, right? Awesome! Develop UIs really quickly by changing your XAML and immediately seeing the results!
Oh wait.. my app references a single compiled library (Realm), and Hot Reload doesn't support that scenario. So it's as if it never existed, and every change requires multiple minutes to rebuild and deploy (if it succeeds, given regular failures above), even for what is a fairly simple application with only a few UI tabs, just to discover that there's an error in the XAML and I have to change things and start all over again.
I'm thankful that I don't depend on Xamarin dev for a living, because that would be like tying your success to the outcome of a roulette wheel. One that is heavily weighted against you.
I really, really, really want to like Xamarin given my love for C#, and I want all its promises to be true. But I've been lucky enough to have a successful career developing everything from low-level embedded firmware to GUIs, so I feel I can again say confidently, this really isn't how software development should be.
EDIT 2: Just a selection of the build/error messages I've captured in recent times, the vast majority of which I never figured out the cause, but managed to get rid of after enough retries/restarts/hail Marys. These are all from the same project, and usually occurred out of the blue or after a platform software update, rather than after any changes I made in the project:
















</rant>
r/Xamarin • u/vlatheimpaler • Jan 18 '22
Connect a .NET Maui app to Arduino Bluetooth
r/Xamarin • u/ddavid8888 • Oct 04 '21
Choosing Xamarin or MAUI for a new project
Hi guys, I'm about to start working on a new app(still not 100% sure about what it will be but the idea right now is some kind of a social media platform for creators) somewhere around January and I am wondering if I should choose xamarin or go straight for MAUI I would like to hear your input about it
Btw it will be my first app
Thank you for your help