Summers Pittman I can understand that there might be some cost with the initial setup. But over the long term, when there are new features are being added, and if you keep the long term cost of maintaining the code base in mind, do you still think it is not a good idea?

Also there are a lot of Xamarin components & libraries are released this way. If the binding idea is so bad, why those libraries continue with this approach?

Also for some of the dependencies we are going to use (like AppAuth), I think they are native libs using bindings anyway. Does it mean we will endup with some of the problems anyway even if our library doesn't use the bindings?

The bottom line is I am not suggesting it is the approach we are going to take. All I am suggesting is to give it a try and see if it's still very hard. We have to keep the cost of maintain the Xamarin code base in mind and even if there is some challenge short term to set it up, but if we can save time, effort in the long term, I think it worth trying.