Storage Service
React Native SDK utilize native SDKs (iOS and Android) to manage feature flags and experimentation data efficiently. These SDKs use a bridge to communicate between the native and hybrid layers, ensuring seamless integration and performance.
#Purpose of of Storage
By default, the SDK uses storage to cache user decisions. As a result, repeated evaluation calls for the same user and feature return the cached decision instead of triggering a fresh evaluation.
To optimize performance and maintain consistency, the SDK provides both built-in storage. This allows you to persist feature flag decisions, mobile applications can quickly access necessary data without repeatedly querying the server.
#Storage Mechanisms by Platform
| Functionality | iOS Storage Mechanism | Android Storage Mechanism |
|---|---|---|
| Fast-access caching of feature flag decisions | UserDefaults | SharedPreferences |
| Persistent storage of offline event tracking data and when event batching configured | Core Data | SQLite |
Note: Although the underlying storage technologies differ between platforms, their functionality is consistent. Both platforms use fast-access key-value stores for caching feature flag decisions and robust databases for persisting offline event data until it can be synced.
#Key Benefits of Storage
- Improved Performance: Reduces network calls and latency by caching decisions locally
- Consistent User Experience: Ensures users get the same experience across app sessions
- Reduced Server Load: Minimizes the number of requests to Wingify servers
- Decision Stability: Once a decision is made for a user, it remains consistent even if campaign settings are modified in the Wingify Application
- Offline Functionality: Allows the SDK to function even when the device is offline