Please share with the community what you think needs improvement with Xamarin Platform.
What are its weaknesses? What would you like to see changed in a future version?
We need to think about partnering with IBM because there is a need for a big data partner; someone who has machine learning and can help us connect the app to big data.
There is limited support for UX widgets. Also, there are compatibility issues between versions of various Xamarin components.
* It needs offline sync capabilities to store data on devices persistently. * Security features and data analytics need to be improved.
Xamarin's profiling tools are only available for the highest tier of MSDN subscription and compatibility with platform-native profiling tools is rather lacking. This causes friction when working on performance-related issues.
The most common issues involved are with the IDE and build process. The worst build issue concerns are the caching process MSBuild uses to reduce the build time. It is unnecessarily complex (internally) and will sometimes leave cached files which should have been removed, even when a full solution clean is performed. The work around involves closing the solution and deleting some project folders. Occasionally, IntelliSense loses sync with the code and provides visual error indicators when no error exists. Xamarin.Forms does have some short comings, especially surrounding performance. Launch time on Android is a particular issue because Xamarin.Forms loads all the external assemblies during initialization. Support for lazy loading or merging of assembles would significantly reduce this, but Microsoft is still committed to a solution. Support of platform specific behavior could also still be improved. However, I believe strongly that Xamarin.Forms is the future of cross-platform native mobile development.
They need to improve performance, especially for the Android platform. Also, some controls are missing in the Xamarin framework when compared to native controls; for example, the checkbox control.
* The android application compilation time needs to be reduced. * The deployment package sizes need to be looked into.
It would be great to have some quirks of Xamarin.Forms solved. However, the number of community developed libraries and components are growing rapidly, so this should be another advantage soon. Nowadays, it is common to find a problem that you would need to develop from the start since there are no third-party components to reuse.
I feel that the Android AppCompat library creates a lot of issues. A lot of development time is often wasted solving these issues.
They need to take a step towards independence from the UI platform. It takes a lot of time to adapt the native controls.
The performance needs improvement, especially the dev tools, and also the ultimate output of the mobile applications.
For those who use only XAML to design the UI, it would be better if there was a better XAML previewer or designer.
I would like to see hot reload, similar to what Flutter has out-of-the-box. There is "Live Reload" but it’s still in preview and was only recently announced.
Needs to improve the customization of its screens.
I would say that every technology has room for improvement, Xamarin Platform is no exception. All Xamarin library issues which need to be taken care of should be top priority. Sometimes it becomes clumsy when there are a lot of things going on in your project or solution and you need to take care of business logic in parallel. On top of everything, providing only wrapper classes does not make a developer’s life easy. So yes, there are improvements going on and they will need to continue to improve in the future as well.