Flutter SDK Update Timeline Request
Hi Kinde team,
My team and I have been using KindeSDK for authentication across our company's Flutter-based products, and we're really looking forward to the next release.
The last pub.dev update was 9 months ago - We're particularly excited about official web support for authentication, I noticed PR #28 was approved two weeks ago, which introduces web support along with several important fixes.
Could you provide an estimated timeline for the next SDK release? We're eager to integrate the web authentication features into our production apps (currently we are using a forked version with our own implementation).
Are there any plans to add WebAssembly (WASM) support? This would help us fully leverage Flutter's web capabilities and improve performance for our web applications.
We really appreciate all the work you're putting into the SDK. Having reliable authentication across all our Flutter platforms (mobile + web) would be a huge win for our development workflow. Thanks for any updates you can share!
Related: PR #28 - Web support implementation:
https://github.com/kinde-oss/kinde-flutter-sdk/pull/28
GitHub
* Simplified the web OAuth flow by separating the completion of web...
Simplified the web OAuth flow by separating the completion of web login into its own method. Web login no longer relies on callbacks and now uses asynchronous methods instead.
Removed flutter_custo...
8 Replies
Hi Bolly,
Thank you for your detailed message and for sharing your enthusiasm about the Flutter SDK updates.
You're eager to know when the next release will be published on pub.dev, especially since it includes the web support implementation from PR #28. You can monitor the latest Kinde roadmap and feature information here: Kinde Feature Release Hub.
You're curious if there are plans to add WASM support to the Flutter SDK to help fully leverage Flutter’s web capabilities. Regarding WASM support, while it's not currently on our immediate roadmap, it's a great idea that we'd love to explore further. To help prioritize this feature, I encourage you to submit it as a formal feature request via our feedback form. Thank you for reaching out and for your continued support. Please let me know if there's anything else I can assist with or clarify
You're curious if there are plans to add WASM support to the Flutter SDK to help fully leverage Flutter’s web capabilities. Regarding WASM support, while it's not currently on our immediate roadmap, it's a great idea that we'd love to explore further. To help prioritize this feature, I encourage you to submit it as a formal feature request via our feedback form. Thank you for reaching out and for your continued support. Please let me know if there's anything else I can assist with or clarify
If I could speak with a human who can give me definitive answers that would be great. Thank you
Hi @Bolly, Ages is a human just uses an external tool to reply to support requests.
An engineer is currently working on preparing the next release of flutter, I will seek to get an update. Could you add an issue to the Flutter repo requesting it, this will help visibility.
Personally I am not familiar with flutters WASM implementation, is there something specific you're hoping to get our of its use in our SDK?
Hi @thebolly_,
Sorry if my last response seemed a bit too robotic, I’m definitely a real human here to help.
As Daniel mentioned, we’re actively working on preparing the next release of the Flutter SDK, which will include the updates from PR #28 (including web support and some important fixes). I don’t have an exact ETA just yet, but I can confirm that it’s currently a priority for us. As soon as I have a more precise timeline, I’ll share it here.
Regarding WASM support: it’s not on the immediate roadmap, but we really appreciate your interest in this feature. To help us prioritize it, could you please file a feature request as Daniel suggested? That would give us better visibility and help us weigh it against other roadmap items.
Let me know if there’s anything else you’re curious about
Thank you both for your responses. It'll be great to hear when the next release of the Flutter SDK will be ready - I'll check back here and keep an eye on the GitHub ticket as well.
Regarding WASM support, the main goal would be to migrate to compatible JS interop libraries. As quoted from the Flutter documentation: "package:web, which replaces dart:html (and other web libraries)" and "dart:js_interop, which replaces package:js and dart:js."
When the next release comes out, my team and I will likely fork it and update the code to enable these features. We'd be happy to submit a PR if you're open to contributions, or I can submit this as a feature request.
WASM support is important because when a package isn't compatible with WASM, it can halt entire projects from moving forward. Teams won't be able to compile their projects unless deprecated packages like dart:html are migrated to the newer alternatives
As a quick win in the current PR #28 you could migrate the current hive package to use https://pub.dev/packages/hive_ce. This would be a switch and replace as it's the community edition that includes wasm support.
Hi Bolly,
Thanks for your update. I’ll discuss your last update regarding migrating the
hive package to hive_ce and your ideas around WASM support with my internal team and will get back to you as soon as I have more information.
In the meantime, feel free to reach out if you have any other questions or thoughts. Thanks again for your insights and support
Hi Bolly,
We're very happy to welcome any PRs or enhancements raised on our Flutter SDK repo, and we’ll gladly review and respond there. Contributions from the community are always appreciated and help us prioritize what matters most to developers like you.
If you’d like to go ahead with a PR for the hive_ce migration, we’d love to take a look. In parallel, we’re also reviewing our roadmap around Flutter web and WASM support, and this definitely aligns with those longer-term goals.
Looking forward to your contribution or any other feedback you might haveHi thank you for the replies.
We will keep an eye on the release - Once the next release comes out we will push to migrate away from our current fork of the project and take the time to include these changes so we can all benefit from them 🙂
Hi Bolly,
It's great to hear that you're planning to adopt the upcoming release and contribute enhancements like the Hive-to-
hive_ce migration. Your proactive approach and thoughtful feedback around WebAssembly and interop compatibility are really valuable, and it’s exciting to see developers like you shaping the direction of the SDK.
We’ll keep you updated here as soon as the next release is published. In the meantime, feel free to reach out if any questions or ideas come up, we’re always happy to collaborate.