Definitely not the response that I was hoping for, but it is better than silence. The only hopeful point was that they solicited feedback from the community which leaves a glimmer of hope on Esri releasing the bindings.
I believe some of the concerns that were brought up in that blog post are not concerns for most Xamarin developers. Without bindings developers have a few of choices on how to proceed:
1. Develop their own bindings
2. Implement the map in a web view and take advantage of the JavaScript ArcGIS APIs
3. Build apps in Xamarin and do not include ArcGIS technologies
4. Develop mobile apps natively which requires a much larger undertaking compared to developing using Xamarin and being able to have some portions of the app using a shared code base for both iOS and Android
If I cannot develop of have issues with the Xamarin bindings then I am going to have to drop Xamarin for developing this app and build the app natively using the platform's toolkit. This introduces quite a few complications to the process of our app development.