diff --git a/client-sdk-references/swift.mdx b/client-sdk-references/swift.mdx
index f1988981..0b06e9e6 100644
--- a/client-sdk-references/swift.mdx
+++ b/client-sdk-references/swift.mdx
@@ -1,5 +1,5 @@
---
-title: "Swift (Beta)"
+title: "Swift"
sidebarTitle: "Overview"
---
@@ -10,7 +10,7 @@ import SwiftInstallation from '/snippets/swift/installation.mdx';
Refer to the powersync-swift repo on GitHub.
-
+
A full API Reference for this SDK is not yet available. This is planned for the V1 release.
@@ -18,13 +18,9 @@ import SwiftInstallation from '/snippets/swift/installation.mdx';
-
- This SDK is currently in a [**beta** release](/resources/feature-status). It is suitable for production use provided you've tested your specific use cases.
-
-
## Kotlin Multiplatform -> Swift SDK
-The PowerSync Swift SDK currently makes use of the [PowerSync Kotlin Multiplatform SDK](https://github.com/powersync-ja/powersync-kotlin) with the API tool [SKIE](https://skie.touchlab.co/) and KMMBridge under the hood to help generate and publish a Swift package. As we move to V1, we are aiming to further reduce or even eliminate the Kotlin Multiplatform dependency, enabling us to fully leverage Swift's native features and libraries. Our ultimate goal is to deliver a Swift-centric experience for developers while maintaining compatibility with the APIs introduced in the Beta to avoid any breaking changes.
+The PowerSync Swift SDK currently makes use of the [PowerSync Kotlin Multiplatform SDK](https://github.com/powersync-ja/powersync-kotlin) with the API tool [SKIE](https://skie.touchlab.co/) and KMMBridge under the hood to help generate and publish a Swift package. The Swift SDK abstracts the Kotlin SDK behind pure Swift Protocols, enabling us to fully leverage Swift's native features and libraries. Our ultimate goal is to deliver a Swift-centric experience for developers.
### SDK Features
diff --git a/installation/client-side-setup.mdx b/installation/client-side-setup.mdx
index fa70fd71..598be1cc 100644
--- a/installation/client-side-setup.mdx
+++ b/installation/client-side-setup.mdx
@@ -26,7 +26,7 @@ The next step after configuring your database and connecting it to your PowerSyn
2. Write mutations to your backend
-PowerSync currently supports apps built in [Flutter](/client-sdk-references/flutter), [React Native & Expo](/client-sdk-references/react-native-and-expo), [JavaScript Web](/client-sdk-references/javascript-web), [Node.js](/client-sdk-references/node) (alpha), [Kotlin Multiplatform](/client-sdk-references/kotlin-multiplatform), [Swift](/client-sdk-references/swift) (beta), and [.NET](/client-sdk-references/dotnet) (alpha).
+PowerSync currently supports apps built in [Flutter](/client-sdk-references/flutter), [React Native & Expo](/client-sdk-references/react-native-and-expo), [JavaScript Web](/client-sdk-references/javascript-web), [Node.js](/client-sdk-references/node) (alpha), [Kotlin Multiplatform](/client-sdk-references/kotlin-multiplatform), [Swift](/client-sdk-references/swift), and [.NET](/client-sdk-references/dotnet) (alpha).
Please see the steps based on your app framework:
@@ -68,7 +68,7 @@ Please see the steps based on your app framework:
See the full SDK reference for further details and getting started instructions:
-
+
diff --git a/installation/quickstart-guide.mdx b/installation/quickstart-guide.mdx
index 88b864cd..f348656a 100644
--- a/installation/quickstart-guide.mdx
+++ b/installation/quickstart-guide.mdx
@@ -9,7 +9,7 @@ PowerSync is designed to be stack agnostic, and currently supports **Postgres**,
- [**JavaScript Web**](/client-sdk-references/javascript-web) (vanilla JS, React, Vue)
- [**Node.js**](/client-sdk-references/node) (alpha)
- [**Kotlin Multiplatform**](/client-sdk-references/kotlin-multiplatform)
-- [**Swift**](/client-sdk-references/swift) (beta)
+- [**Swift**](/client-sdk-references/swift)
- [**.NET**](/client-sdk-references/dotnet) (alpha)