Jurnexus Reviews lets campaigns and journeys request the native iOS or Android review flow when current app posture and policy allow it. The platform records the request decision without pretending to know whether the store displayed a prompt or which rating followed.
The journey emits a governed mobile action to the bound installation. The native app validates the command and invokes the supported Apple or Google review API in the foreground.
Use meaningful product signals to decide when asking is appropriate. Store APIs may suppress the prompt and do not reveal the player rating, so Jurnexus records request and execution evidence only.
Configure application-specific policies, cooldowns, maximum attempts and emergency pause. Device and app-version posture prevents unsupported installations from receiving the action.
Yes. Scope can begin with one use case, environment, data source or channel while retaining the contracts and boundaries required to evolve.
Configuration passes through validation, immutable versions and permissions. External effects use explicit connections, current decisioning and auditable evidence.
No. Jurnexus is designed as a provider-neutral engagement layer connected through approved APIs, SDKs and contracts.
We can map its signal, app bridge, cooldown and evidence model without interfering with the existing application experience.