Integration planning guide. The snippet is an application-level pattern, not a verified Rive SDK example. Connect it through the API supported by your actual file and installed runtime.
Check the native runtime first
A web example is not a drop-in native implementation. Check the current official React Native package, supported architecture and platform requirements. Pin the version you validate and record it with the delivered file.
Drive motion from product state
Keep request, navigation and account logic in the application. Convert them to a small visual state contract. Decide what should happen when a screen blurs or the application returns from the background.
Test both platform builds
Run the same event sequence on supported iOS and Android devices. Review layout, memory, failure states and accessibility settings separately; success on one platform is not evidence for the other.
A small starting point
// Platform-independent handoff example; no SDK calls.
const visualStates = {
disconnected: "rest",
awaitingResponse: "thinking",
playingResponse: "speaking",
responseFailed: "recover"
};Before calling it done
- Record the exact runtime version and exported asset used in validation.
- Test the normal sequence, an interruption, a failed load and screen re-entry.
- Confirm the same information remains readable with reduced motion or no animation.
Use the official Rive runtime documentation for current APIs and feature support.