React & React Native

React and React Native are natural targets for future Wistfare widget packages, but the public production story today is still server-first rather than client-package-first.

React Web Today

For web applications today:

• Use your own React components for checkout, support, onboarding, or wallet flows.
• Let your backend call Wistfare with the TypeScript, Python, Go, Dart, Rust, Swift, Kotlin, or .NET SDK that matches your stack.
• Return only the browser-safe state your React app needs to render.

React Native Today

For React Native applications today:

• Treat the mobile app as a presentation layer.
• Route Wistfare business operations through your backend.
• Keep API keys and idempotency logic off the device.
• Use deep links or app navigation events to move users through your own support or payment experience.

Planned Package Direction

When public widget packages are available, the intended value will be:

• A reusable embedded UI instead of a custom-built client surface.
• Standard lifecycle events for analytics and workflow hooks.
• Shared visual customization options across web and mobile surfaces.
• A smaller setup path for teams that want Wistfare-managed UI primitives.

When to Wait for a Widget Package

Waiting for a widget package makes sense when:

• You want a host-managed embedded experience instead of building your own UI.
• Your team prefers standardized components over deep frontend customization.
• The integration is not blocking a current release.

When to Build Now

Build now with your own UI when:

• You need production reliability immediately.
• Your product already has a strong design system.
• You need fine-grained control over screens, permissions, and side effects.
• You want to expose only a subset of Wistfare functionality inside your app.