You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use Uno Platform for our mobile app development and would love to use Superwall if there were a .net SDK. Please consider adding one (or creating some documentation on creating new SDKs so that we can provide one as a community)
The text was updated successfully, but these errors were encountered:
Hey @trydalch! Unfortunately I don't think we have the bandwidth to tackle this ourselves currently. However, I don't think it's actually a huge life to build out bindings for .NET. You can take a look at https://github.com/superwall/react-native-superwall and https://github.com/superwall/Superwall-Flutter. They are both pretty small wrappers around the iOS and Android SDKs. Would you mind taking a look and seeing what you think?
Hi @anglinb I'll take a look. I don't think it would be too difficult to put a .net binding project together for each of those and publish on nuget. The biggest question I have right now is around testing. Looking at both of those libraries, it looks like neither one has tests implemented.
Any guidance on that?
I may have some time to begin working on a .net SDK soon.
Hey @trydalch! Yes, there aren't automated tests for the client wrappers. Since it's really just a shim over the platform libraries, we just run through a manual process when making changes. It's really hard to isolate just the wrapper.
Sweet, would love for you to take a stab at it! I think the most important APIs you'd need to setup bindings for are configure, setUserAttributes and register. Other than that if you're letting Superwall handle the purchase you might be good enough to get going!
We use Uno Platform for our mobile app development and would love to use Superwall if there were a .net SDK. Please consider adding one (or creating some documentation on creating new SDKs so that we can provide one as a community)
The text was updated successfully, but these errors were encountered: