Solid color
Best when you want a clear, low-risk shield that is easy to explain and visually consistent across many screens.
ShiftOne ScreenVeil Web
Choose a protection style that fits the product
ScreenVeil is not just about turning protection on. Choose a presentation style that fits brand tone, user trust, and support expectations.
Common presentation options
Blur
Useful when you want the product to feel softer or less abrupt, but you should still verify that it meets your own sensitivity standards.
Branded image cover
Works well when product or marketing teams want a more polished appearance during protected states, especially in demos or premium consumer flows.
How teams usually assign styles
1. Choose by sensitivity
Highly sensitive payment or identity surfaces often start with solid color because clarity matters more than visual nuance.
2. Choose by state
A team may prefer one presentation for inactive or app-switcher states and another for capture-related states, as long as the difference stays understandable.
3. Validate brand and usability
The protected appearance should still look intentional in screenshots, QA recordings, and internal demos.
Selection criteria
- • How sensitive is the underlying content if briefly exposed?
- • Will customer support need to explain the behavior to operators or reviewers?
- • Does the team need the protected state to look neutral, branded, or obviously locked down?
- • Can the selected style remain readable and intentional across light/dark appearance, rotation, and different device sizes?
Avoid these mistakes
- • Do not choose a style only because it looks good in a single demo screenshot.
- • Do not assume one style is equally appropriate for every sensitive surface.
- • Do not present a softer visual style as evidence of stronger technical guarantees.
- • Blur over a secure container produces a uniform tinted appearance, not a recognizable blur of the underlying content. This is expected behavior.
Style factory methods
SVProtectionStyle factory methods available for inactive/app-switcher and capture states.
- +defaultStyle
- Opaque black solid-color overlay. The default for both inactive and capture states. Swift: .defaultStyle
- +solidColorStyleWithColor:
- Solid color overlay. Swift: .solidColor(_:)
- +imageStyleWithImage:
- Image overlay with default aspect-fill content mode. Swift: .image(_:)
- +imageStyleWithImage:contentMode:
- Image overlay with explicit content mode. Swift: .image(_:contentMode:)
- +blurStyleWithEffectStyle:
- Blur overlay without tint. Swift: .blur(style:)
- +blurStyleWithEffectStyle:tintColor:tintAlpha:
- Blur overlay with optional tint color and alpha. Swift: .blur(style:tintColor:tintAlpha:)
Configuration example
Assign different styles to inactive/app-switcher and capture states.
// inactive: blur with dark tint
configuration.inactiveProtectionStyle =
[SVProtectionStyle blurStyleWithEffectStyle:UIBlurEffectStyleSystemChromeMaterialDark
tintColor:UIColor.blackColor
tintAlpha:0.2];
// capture: branded image overlay
configuration.captureProtectionStyle =
[SVProtectionStyle imageStyleWithImage:brandedOverlay
contentMode:UIViewContentModeScaleAspectFill];Related manuals
These manuals work best when read as part of the full rollout path, not in isolation.
iOS integration
Apply the chosen style to the right screen containers and states.
Open manualValidation
Test each style on real devices and state changes before rollout.
Open manualLimitations
Keep visual choices aligned with a best-effort product boundary.
Open manual