docs: recommendations against standalone SDK usage (#291)

Author: andreas-karlsson

README.md

@@ -83,11 +83,10 @@ OpenFeature.setContext({
 
 try {
   await OpenFeature.setProviderAndWait(provider);
-} (error) {
+} catch (error) {
   console.error('Failed to initialize Confidence provider:', error);
 }
 
-
 const client = OpenFeature.getClient();
 const isEnabled = client.getBooleanValue('feature.enabled', false);
 ```
@@ -108,12 +107,18 @@ You can check out the example application, which is built with Next.js and uses
 
 # Direct SDK Usage
 
+> [!NOTE]
+> The standalone SDK is being phased out. For new integrations, we recommend using the OpenFeature APIs described above.
+
 The vanilla sdk can be used in cases where you want direct access to the Confidence SDK, including event tracking and custom context management.
 
 > **Learn more**: [SDK Documentation](./packages/sdk/README.md)
 
 ## React Integration
 
+> [!NOTE]
+> The standalone React SDK is being phased out. For new integrations, see the [OpenFeature React SDK](https://openfeature.dev/docs/reference/sdks/client/web/react/) section above, or consider server-side flag resolution for SSR applications.
+
 For React applications, use the dedicated React package that provides hooks and providers for seamless integration. This package is built on top of the direct SDK usage.
 
 > **Learn more**: [React Integration Documentation](./packages/react/README.md)

packages/react/README.md

@@ -2,6 +2,12 @@
 
 ![](https://img.shields.io/badge/lifecycle-beta-a0c3d2.svg)
 
+> [!NOTE]
+> This Confidence standalone React SDK is being phased out. For new integrations, we recommend using the OpenFeature APIs directly:
+>
+> - **Client SPA**: Use the [OpenFeature React SDK](https://openfeature.dev/docs/reference/sdks/client/web/react/) with our [@spotify-confidence/openfeature-web-provider](https://github.com/spotify/confidence-sdk-js/blob/main/packages/openfeature-web-provider/README.md)
+> - **SSR (e.g., Next.js)**: Resolve all flags server-side using [@spotify-confidence/openfeature-server-provider-local](https://github.com/spotify/confidence-resolver/tree/main/openfeature-provider/js/README.md) and propagate values to the client. This gives optimal performance, avoids the complexity of managing context across the client/server boundary, and keeps flag logic and sensitive context data securely private.
+
 This package contains helper functionality to make the Confidence SDK work well in a React environment. **Note:** This package is only relevant if you are using the Confidence SDK directly. If you are using OpenFeature, please use the [OpenFeature React SDK](https://github.com/open-feature/js-sdk/tree/main/packages/react-sdk) instead.
 
 # Usage

packages/sdk/README.md

@@ -2,6 +2,12 @@
 
 ![](https://img.shields.io/badge/lifecycle-beta-a0c3d2.svg)
 
+> [!NOTE]
+> This Confidence standalone SDK is being phased out. For new integrations, we recommend using the OpenFeature APIs directly:
+>
+> - **Client-based (SPA)**: Use [@spotify-confidence/openfeature-web-provider](https://github.com/spotify/confidence-sdk-js/blob/main/packages/openfeature-web-provider/README.md)
+> - **Server**: Use [@spotify-confidence/openfeature-server-provider-local](https://github.com/spotify/confidence-resolver/tree/main/openfeature-provider/js/README.md), which resolves flags in-process with close to zero latency
+
 JavaScript implementation of the Confidence SDK, enables event tracking and feature flagging capabilities in conjunction with the OpenFeature Web SDK.
 
 # Usage