4 ms·
Any 3rd party solution will have some issues. Whenever you see mostly positive testimonials, you should be both suspicious and scared, because it means you will
by blub 11y ago
Any 3rd party solution will have some issues. Whenever you see mostly positive testimonials, you should be both suspicious and scared, because it means you will be the one to find those issues in production, and you won't find any help on the internet.
That was a long time the case for Xamarin, but if you look at their customer forums, reddit, stackoverflow etc you will find the negatives too nowadays.
I am not interested in .NET, so I would not personally use Xamarin anyway, but I know that with Qt for instance you have to be careful with mobile UIs - it's best used for custom stuff and not native-looking apps.
- m_fayer 11y agoI use Xamarin regularly, and it's true the primary downside is frequent bugs and regressions along the entire toolchain, and in the Xamarin wrappers of native APIs. That said, it's improved by leaps and bounds in since last Summer. It's gone from "I'm about to dump this platform any day now" to "minor nuisance", and most of the time you can just get on with your work.
- dcveloper 11y agoI second the regression issue. Particularly if you use Xamarin.Forms. The Forms navigation stack is full of memory leaks as well.
- m_fayer 11y agoFor the record, I use Xamarin "classic" and not forms, and my comment was in reference to that. Given the age of X.Forms, what you say sounds par for the course.