background-state

To save webview plugin state during background transitions, you identify mutable variables like counters or selections and register a JSON-serializable snapshot via the setBackgroundState hook at module initialization. The skill guides you to export this state so it survives the app entering the background.

To restore plugin state after returning to the foreground, you apply the onBackgroundRestore hook to merge the saved snapshot back into your live state. The skill instruments this with nullish fallbacks to ensure safe recovery of your runtime data without crashing on missing values.

Runtime data such as counters, user selections, and small buffers should persist across background transitions. The skill targets mutable plugin state that would reset if not explicitly captured, ensuring consistent behavior after foreground return instead of losing user progress.

Background-state persistence works directly with the even_hub_sdk by requiring you to import setBackgroundState and onBackgroundRestore from it. You register these hooks at module init using a stable key to manage your plugin's lifecycle data effectively.

Plugin state resets when the app goes to the background because the host clears the webview runtime memory. This skill solves the problem by automatically capturing and restoring your JSON-serializable snapshot via background lifecycle hooks to prevent data loss.

You need to serialize plugin state to JSON for background persistence because the exported snapshot must be JSON-serializable. The skill requires this format along with nullish fallbacks in the restorer to safely handle missing data during state recovery.