SdksWidgets
Flutter Widget
How Flutter teams should approach Wistfare today, and what a future drop-in Flutter widget should cover.
Flutter teams often want a ready-made in-app surface for support, onboarding, or payment guidance. Wistfare is expected to support that through a dedicated Flutter widget package, but that package is still planned rather than published.
Use Dart on the backend today
The reliable path today is to keep business logic on your backend and use the Dart server SDK packages for shared tooling or server-side integration work.
What the Flutter Widget Should Eventually Cover
- A reusable conversation or support surface that fits inside an existing Flutter app.
- Theme hooks so the widget inherits your brand colors and typography direction.
- Event callbacks for open, close, transfer, or completion states.
- Optional real-time transport and voice support once the hosted widget stack is public.
What to Build Today
For production Flutter apps today, split responsibilities clearly:
- Build the customer-facing UI in Flutter.
- Send business operations through your own backend.
- Use Wistfare server SDKs or direct backend HTTP calls behind that backend layer.
- Keep API keys, idempotency logic, and retries out of the mobile client.
Good Flutter Use Cases for Wistfare Right Now
- Payment request creation from your admin or merchant backend.
- Wallet balance and transaction views powered by your own API.
- Business settings and staff workflows managed from a secure backend.
- Support or checkout flows where Flutter owns the UI and your backend owns the Wistfare integration.
Planning Checklist
If you expect to adopt a future Flutter widget package, decide early:
- Whether the widget should live in a page, sheet, or modal.
- Which signed-in user details can be passed into a widget session.
- Which events should map to app navigation or analytics.
- Whether your design system needs a full-screen or floating-entry treatment.