Hello, vdimas, you wrote: V> Hello, Serginio1, you wrote: V>>> And can, there a problem not the technology roadmap, and what with any Xamarin initially rolled out the circuit XAML, having different interpretations with the circuit from WPF/Silverlight/WinRT-UWP? Perhaps the problem consists especially in standards on itself XAML? S>> Actually and UWP differs from WPF. V> it is not strong, and does not differ almost from a cervelat. There is enough. V>>> Such problem is not present. S>> Then in what. UWP now as a matter of fact anything from WPF that does not differ, and here that WPF is far. V> Kzamarin is a technology of visual editing of forms, first of all. V> it quitted more advanced, than the built in editors of Studio. V> I.e. here it is more in the technology of a CAD, than in specific , which at more than one. Yet really? The same Xamarin. Android and Xamarin. IOS as that live on , and it is primary Xamarin. Forms was without the editor. All program. Or it is necessary to use other studios https://habrahabr.ru/post/188130/Development UI For each platform Xamarin gives possibility to use means of development UI and user interface elements. For Android creation UI can happen immediately in the code or by means of the declarative approach to the interface description in XML. For iOS it also either the code, or usage interface design tools - separate xib-files or one big Storyboard. Editing of these files happens in customary XCode environment for the iOS-developer. And it means that it is required to you Mac. Yes, for development of iOS-appendices anyway it is required to you Mac for two reasons: At first, as I already told, for editing UI in the environment of XCode. Secondly, for debugging of applications the simulator iPhone/iPad which also is accessible only on Mac is required. And about Xamarin. Forms it and in soles is not necessary WPF. And, as to there it is used.Net Core which for . Xamarin left from PCL and passed on.Net Standard.