- • An iOS app with a stable Bundle ID for the build you plan to evaluate.
- • A team decision about which screens and state transitions are considered sensitive.
- • At least one real device in the OS versions you actually support.
- • An internal owner for integration and a reviewer who can sign off on the validation result.
ShiftOne ScreenVeil Web
Getting started with ScreenVeil
Use this manual when you want the shortest reliable path from evaluation to an internal app build. It covers commercial policy, activation flow, and validation expectations in one place.
What you need before you begin
Recommended rollout order
1. Request a 7-day trial license
Submit the Bundle ID through the website. Trial licensing is the intended pre-purchase evaluation path.
2. Download the current package
Download the latest XCFramework from the download page and add it to the same app target you plan to validate. Download access alone does not grant production rights.
3. Protect one meaningful surface first
Start with a balance view, account panel, identity surface, or another container that represents a real-world use case.
4. Apply the license and verify activation
Make sure the app enters a licensed state before you depend on the shielding behavior in QA or demos.
5. Validate on devices and state changes you truly support
Test foreground use, app-switcher exposure, backgrounding, and capture-related visibility states on real devices before concluding the evaluation.
What success looks like
Operational success
Your team can explain where ScreenVeil is applied, how the protected surfaces behave, and what degraded behavior appears when activation fails.
Product success
Sensitive screens remain usable in normal app flow while protected presentation appears in the states your product team actually cares about.
Commercial success
The team is comfortable that trial evaluation covered the real use case well enough to justify moving into a commercial license.
Before you move from trial to production
- • Confirm the final production Bundle ID that will receive the commercial license.
- • Document which screens, flows, and states were validated and which were intentionally left out.
- • Keep a fallback experience for license or configuration failures instead of assuming activation can never fail.
- • Review the limitations manual with legal, security, or compliance reviewers if they need precise product scope details.
Quick activation snippet
The core call that applies a license and enables protection on a container view.
BOOL ok = [container sv_enableProtectionWithLicenseJSON:licenseJSON
configuration:configuration
error:&error];Related manuals
These manuals work best when read as part of the full rollout path, not in isolation.
iOS integration
Where to apply ScreenVeil in the host app and how to structure rollout.
Open manualLicense activation
How trial and commercial licenses are applied, checked, and renewed.
Open manualValidation
What to test before concluding that the integration is ready.
Open manual