Hey all, you may have noticed the library is movin...

# supabase-kt

[Jan]

Hey all, you may have noticed the library is moving slow lately; this is because we are currently figuring out some internal stuff and the SDKs general direction. Once that is figured out, we will introduce a lot of new features and changes including built-in Native Auth and Passkey support.
I just released 3.7.0-beta-1, which includes binary broadcasts, passkey api support and custom oauth provider api support. Let me know if there are any issues.

Also, I wanted to ask what approach you'd prefer:
• A auth-kt library with everything built-in (OAuth, Native Auth, Passkeys, Deeplinking via Native (extra) libraries);
◦ upside: everything is in one place
◦ downside: You get all the dependencies for these native features, even if you don't need them, potentially harder to maintain
• A auth-kt library which only provides the API methods (sign in via password, sign out, sign up, passkey api methods, etc.) as well as session management and then a separate auth-native library which provides support for OAuth, Native Auth, Passkeys, etc. A proposal can be seen in https://github.com/supabase-community/supabase-kt/pull/1291
◦ upside: separate common vs native features, potentially easier to maintain
◦ downside: you need the extra module
I'd be grateful for feedback!