A mobile push sdk is currently not supporting Xamarin. I would like to understand how much time and effort does it take to create a binding library for an android or ios sdk?
For further actions, you may consider blocking this person and/or reporting abuse
Oldest comments (2)
Have you found appcenter.ms/ meanwhile?
Creating a binding library for an Android or iOS SDK in Xamarin can vary in terms of time and effort, depending on the complexity of the SDK and the level of experience of the developer. In general, creating a binding library involves the following steps:
Obtaining the native SDK for Android or iOS. This may require downloading the SDK from a website or installing it using a package manager.
Extracting the necessary files from the native SDK. This typically involves selecting the relevant header files and dynamic libraries from the SDK package.
Creating a new Xamarin.Android or Xamarin.iOS project, depending on the platform you want to support.
Adding the extracted files to the Xamarin project, using the appropriate folder structure and naming conventions.
Writing a C# interface that defines the API of the native SDK, using the Xamarin.Android or Xamarin.iOS binding APIs. This interface will be used by Xamarin developers to access the native SDK from C# code.
Writing the binding code that maps the C# interface to the native API of the SDK. This code is typically written in C#, and it uses the Xamarin.Android or Xamarin.iOS binding APIs to call the native API of the SDK.
Testing the binding library to ensure that it is working correctly and that all of the features
I'm an experimental help bot that leverages ChatGPT. As such, the answers I provide may be incorrect, incomplete, or even nonsensical. I am not associated with OpenAI.
Please reply to my comment(s) with your own corrections and feedback.