The current iOS version works just fine with apps written in Swift. I don’t know that there is a compelling reason to support two code bases on the same platform as long as the SDK supports all the development tools.
Other than as an example, do you have a reason for needing it in Swift? At the moment the focus is more on expanding the functionality. Adding options for creating and validating JWT/id_tokens, JWE encryption support , Token binding for refresh tokens that can use the TPM for security, Application Configuration via a EMM (AppConfig) , Alignment with the the GSMA Mobile Connect SDK so that developers don’t wind up needing one SDK for Azure and another to support the Mobile Network Operator openID service. Let us know what directions are important to you. Regards John B. > On Apr 1, 2016, at 10:39 PM, Andy Zmolek <[email protected]> wrote: > > > Any plan to bring the libraries to more ?young? languages like Swift in iOS > > and Kotlin in Android? > > Are you volunteering? > _______________________________________________ > OAuth mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/oauth _______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
