I have many of the issues you have when working VS under Windows; VS under Mac (for iOS dev) a lot less. So because of path of least resistance, I first finish

I have many of the issues you have when working VS under Windows; VS under Mac (for iOS dev) a lot less. So because of path of least resistance, I first finish iOS apps on Mac and then compile / test on Android (which is far more of a pain, which I find for React Native as well tbh and for their native ObjC/iOS vs Java/Android as well; my opinion, not saying one is better than the others; probably just what I'm used to). I use Forms as a framework, not 'out of the box'; I have many of my own controls and tooling; I have a live XAML editing environment and a crippled but functional C# scripting implementation to not have to deal with IDE's so much. When Miguel Icaza did a blogpost about the interpreter environment[0] finally getting some love end last year, I was hopeful, but unfortunately it seems development is going so slow that I implemented my own which is buggy for others (let's say unworkable) but allows me to live program on iOS. I think it will make quite a difference; I know it does for me as I use it for everything, but within the confines of what I could implement in my free time. Wish Krueger [1] would open source his interpreter as his has many bugs but far far less than mine and it could be a good effort fixing bugs and getting a better project on the iPad at the same time. A propos ; Continuous is great for playing around with Forms and Xamarin iOS in a fast and responsive environment on an iPad Pro with keyboard. For just getting the screens perfect fast it is pretty good. Not sure why he doesn't have XAML support (or he has but I could not find it so I assumed not) as that is pretty trivial to implement. [0] https://www.mono-project.com/news/2017/11/13/mono-interpreter/ https://www.mono-project.com/news/2017/11/13/mono-interprete... [1] http://continuous.codes http://continuous.codes