First let me translate for anyone visiting this forum (using Bing Translate):
I couldn't find such a Statement anywhere, why should I know that? I think it's a real shame why they hired Android and IOS Native, as there are also many Advantages with it. Do they know what was the Reason for this? Why do you do something like this where there is so much Potential?
Please read those two blog posts I've linked to, the decision was not taken lightly and the reasons why this decision was made was explained in those posts.
What you've highlighted in that screenshot are the Xamarin.
iOS and Xamarin.
APIs around the native controls, not the native controls themselves (you can't use it in Xcode or Android Studio
). These are required for us to use the control in Xamarin.Forms, but it also lets you use them in a non-Forms Xamarin application.
However, they are still wrapper APIs around the native control's features and functionalities. There are cases where the native controls needed to be updated to help support a Xamarin.Forms implementation. However, any new
development is going to be invested in the Xamarin.Forms APIs and controls suites.
We've take this approach because we believe that we can deliver the best cross platform value and functionality by using the cross platform APIs available through Xamarin. Examples of this are controls like BarCode
, and many more.
The best way to provide those controls to all three main plaforms is to develop it once in Xamarin.Forms. The alternative is to develop it 7
separate times (Android native, Xamarin.Android wrappers, iOS native, Xamarin.iOS wrappers, UWP native, UWP wrappers and finally the Xamarin.Forms platform renderers).
I hope I was able to help explain this, if you would like to see new features added to the native controls, please leave a Feature Request in the Feedback Portal
. The more interest we see in a useful feature, the higher the chance the development will add it to the furture development plans.
Lance | Technical Support Engineer, Principal
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items