Teams encountering DoveRunner and the older AppSealing name should first establish product and documentation continuity. Verify current integration, platform and licensing scope in current official documentation.
Evaluation approach
DoveRunner offers mobile application security and content security as distinct solutions. Compare Android and iOS protection coverage using current documentation.
Application example
If using an older AppSealing integration guide, verify the current release's packaging, console and support processes.
Limits and considerations
Content DRM and Mobile RASP are different capabilities. A shared brand does not make them equivalent.
Matching older documentation to the current service
Technical content using an old brand name can remain searchable long after a change. Verify the current support channel, version and platform scope of the SDK or packaging service. Match the contractual product to the component in the application.
Prepare separate acceptance scenarios for application protection, media licensing and key distribution. A working older integration does not independently establish its current support status.
Checks and decisions
- Use current documentation
- Ask about platform differences
- Review older integrations
Assess a rebrand alongside the technical scope of the deployed component and contract.
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.