Customization

This section outlines the elements you can customize within the Selfie Capture module to match your brand while preserving Incode’s core UX. It clarifies which areas are flexible, such as text, illustrations, and brand colors and which elements remain fixed to ensure consistency, accessibility, and optimal capture performance across platforms.


Tutorial Screen

The Tutorial Screen prepares the user for the Selfie Capture step. It introduces the action, provides the necessary context, and sets expectations before the camera is activated.


Customizable Elements

AreaWhat can be customizedNotes
TextTitle, subtitle, body textFully localizable; tone can be adapted
IllustrationColors or full replacementMust remain clear and represent a face
Brand ColorsHeader, highlight elements, illustration ring, buttonUses brand tokens
ButtonsLabel, color, radiusMust follow platform guidelines
Footer“Verified by Incode” lineOptional but recommended

Fixed Elements

ElementWhy it is fixed
Layout structureEnsures consistency across modules
Silhouette styleMust remain consistent with global UX
Spacing & safe areasRequired for device compatibility
Text hierarchyOptimized for readability
Close icon positionStandardized for user familiarity
WCAG minimum contrastMandatory

Token Reference

UI ElementTokenValue
Brand namebrand 500#006AFF
Title texttext-body-primary#262831
Subtitle texttext-body-secondary#60667C
Illustration ringsurface-primary-50#E5F0FF
Illustration accentbrand 500#006AFF
Button backgroundsurface-primary-500#006AFF
Button textbutton-primary-text-default#FFFFFF
Backgroundsurface-neutral-light#FFFFFF
Close iconicon-primary#60667C

Design Notes

  • Keep copy short to minimize cognitive load.
  • The illustration uses brand 50 and brand 500 to reinforce brand identity without overwhelming the UI.
  • Ensure tap targets meet accessibility guidelines.
  • Maintain clear focus states for keyboard and screen reader users (Web).


Fake Permission Screen

The Fake Permission Screen is shown before the operating system displays its native camera permission modal. It prepares the user, explains why camera access is required, and significantly reduces the likelihood of users denying permission. This step increases trust and prevents interruptions during the selfie flow.


Customizable Elements

AreaWhat can be customizedNotes
TextTitle, subtitle, permission explanationFully localizable; tone should remain reassuring
ButtonsLabel (“Allow”, “Don’t allow”), color, radiusMust maintain primary/secondary hierarchy
Brand ColorsButton accents, icon color, text accentsUses brand tokens
Modal SurfaceBackground color, elevation, corner radiusMust remain high-contrast and readable
Link/Help Text“Learn more” or similar supportive textOptional; can adapt tone based on compliance needs

Fixed Elements

ElementWhy it is fixed
Background dim opacityIndicates OS-level permission flow; needed for clarity
Modal positionStandardized centered layout for all modules
Button hierarchyMirrors OS expectations; prevents accidental “Don’t allow” taps
Safety text hierarchyEnsures user comprehension before OS prompt
Spacing & safe areasRequired for device consistency
WCAG minimum contrastMandatory

Token Reference

UI ElementTokenValue
Dimmed backgroundsurface-neutral-900-80#14151A 80%
Modal backgroundsurface-neutral-light#FFFFFF
Title texttext-body-primary#262831
Subtitle texttext-body-secondary#60667C
Primary button (Allow)surface-primary-500#006AFF
Primary button textbutton-primary-text-default#FFFFFF
Secondary buttonbutton-secondary-border-default#006AFF
Secondary button texttext-brand-accent#006AFF
Header iconsicon-primary#60667C

Design Notes

  • The pre-permission modal reduces drop-off by providing context before the OS permission.
  • Maintain a clear hierarchy between primary (Allow) and secondary (Don’t allow) actions.
  • Keep the dim overlay consistent to align with OS modal expectations.
  • Ensure high contrast between modal, text, and background elements.
  • Avoid adding extra steps or interaction on this screen.


Capture Screens

During capture, the user aligns their face within the silhouette, and the system evaluates real-time conditions such as lighting, alignment, and distance. Once requirements are met, the photo is taken automatically. Colors and on-screen text can be customized to match your brand, while the silhouette itself is fixed, as it plays an essential role in helping users position their face correctly.


Customizable Elements

AreaWhat can be customizedNotes
TextInstruction text (“Align your face…”, “Get ready…”)Fully localizable
Brand ColorsProgress indicator, icon colors, header colorControl via tokens
IllustrationSilhouette outline colorColor only — shape cannot change
BackgroundNeutral/light surfacesMust maintain contrast
Footer“Verified by Incode” lineOptional

Fixed Elements

ElementWhy it is fixed
Silhouette shapeEssential for proper face alignment
Auto-capture behaviorEnsures consistency and accuracy across devices
Detection logicRequired for system-level validation (lighting, distance, etc.)
Layout & hierarchyPreserves visual consistency across modules
Minimum contrastMandatory to meet accessibility standards
Progress indicator arcBehavior and animation timing remain fixed

Token Reference

UI ElementTokenValue
Header brandbrand 500#006AFF
Instruction texttext-body-primary#262831
Secondary texttext-body-secondary#60667C
Silhouette ring (outer)surface-primary-50#E5F0FF
Silhouette arc progressbrand 500#006AFF
Backgroundsurface-neutral-light#FFFFFF
Footer text icontext-brand-accent#006AFF

Design Notes

  • The silhouette cannot be altered in shape, only color, as it ensures correct face alignment.
  • The progress arc represents detection readiness; its behavior should remain consistent to avoid confusing users.
  • Use brand colors subtly to avoid distracting from the user’s face.
  • Keep instruction text short and focused to reduce cognitive load.
  • Maintain clear focus states and large tap areas (for accessibility on Web).


Manual Capture

Manual capture is triggered after a period of inactivity (default: 30 seconds) when automatic detection conditions are not met. In this mode, the user aligns their face within the silhouette and presses the capture button manually. This ensures the user can still complete the verification even in low-light, complex backgrounds, or edge-case scenarios.


Customizable Elements

AreaWhat can be customizedNotes
TextInstructional text (“Align your face… and press the button…”)Fully localizable
ButtonLabel, color, radius, icon colorMust follow platform accessibility & tap-target rules
Brand ColorsHeader, accent rings, button background, icon accentsDriven by brand tokens
Silhouette ColorOuter ring color onlyShape/size cannot change
BackgroundLight/neutral backgroundsMust maintain contrast with silhouette
Footer“Verified by Incode” lineOptional

Fixed Elements

ElementWhy it is fixed
Silhouette shapeCore UX element ensuring proper face alignment
Camera button placementEnsures reachability and consistency across platforms
Detection logic fallbackManual mode must always follow auto mode
Layout spacing & safe areasRequired for compatibility across device sizes
Accessibility contrastMust meet WCAG AA requirements
Tap target size for buttonRequired for usability and accessibility

Token Reference

UI ElementTokenValue
Brand headerbrand 500#006AFF
Silhouette ringsurface-neutral-light#FFFFFF
Silhouette borderborder-neutral-100#EBECEF
Button iconicon-invert
Button backgroundsurface-neutral-800#262831
Instruction texttext-body-secondarygray 500 — #60667C
Backgroundsurface-neutral-light#FFFFFF
Button inner ringsurface-secondary-opacity-80#000000 80%
Footer text/linktext-brand-accent#006AFF

Design Notes

  • Manual mode provides a fail-safe capture method when automatic detection is not possible.
  • Ensure the camera button remains highly visible against any background.
  • Keep instructional text concise and actionable to reduce friction.
  • The silhouette must remain visible at all times; avoid color changes that reduce contrast.
  • Button must preserve accessible tap size (minimum 44×44 px on mobile).


Capture Complete (Uploading & Success)

Once the selfie is captured, either automatically or manually, the user transitions into the Uploading and Success states. These screens reassure the user that the capture is being processed and provide a clear confirmation when the image is accepted. Both the loading ring and the confirmation colors can be branded to match your product’s identity.


Customizable Elements

AreaWhat can be customizedNotes
Text“Uploading…”, “Success!”, body textFully localizable
Brand ColorsProgress ring, outline, success colorsShould follow brand tokens
SurfacesBackground, circular surfaceMust ensure contrast and clarity
Footer“Verified by Incode”Optional
AnimationProgress ring color transitionsOnly color; timing/behavior is fixed

Fixed Elements

ElementWhy it is fixed
Progress ring behaviorEnsures consistent feedback cadence across all modules
Success timingUser feedback consistency / prevents premature transitions
Layout structureStandardized for readability and predictability
Minimum contrastRequired for WCAG AA compliance
Loading animation arcBehavior cannot be modified to maintain UX continuity

Token Reference

UI ElementTokenValue
Brand headerbrand 500#006AFF
Loading ring (outer)border-status-positive#189F60
Loading ring (inner)border-neutral-100#EBECEF
Text (“Uploading…”)text-body-primary#262831
Success ringpositive 600#189F60
Backgroundsurface-neutral-light#FFFFFF
Footer texttext-brand-accent#006AFF

Design Notes

  • Keep messaging short and neutral, users should feel reassured, not overwhelmed.
  • The green ring color communicates a positive state; ensure it remains accessible and high-contrast.
  • Background should remain clean and unobtrusive to keep focus on the processing state.
  • Avoid adding interaction in these screens; the user should not be able to interrupt this step.
  • Maintain consistent ring thickness and spacing to preserve visual rhythm across modules.


Error Screens

Error screens appear when an issue occurs during capture, such as face misalignment, incorrect lighting, occlusions, or when all attempts have been exhausted. These screens help guide users back into the flow by providing corrective instructions or informing them that manual review will be needed. While text and styling can be branded, error types cannot be removed, as they correspond to specific detection events within the experience.


Customizable Elements

AreaWhat can be customizedNotes
TextError title, description, remaining attempts labelFully localizable
ButtonsCTA labels (“Try again”, “Continue”), button color, radiusMust keep primary/secondary hierarchy
Brand ColorsHeader, accent colors, button colorsFollows brand token system
IconsIcon color (warning, error)Only color, not shape
BackgroundNeutral/light surfacesMust maintain strong contrast with text + icon

Fixed Elements

ElementWhy it is fixed
Error event typesLinked to detection logic; cannot be removed or reordered
Error icon shapesEnsures immediate recognition and consistency across modules
Error screen layoutPreserves visual predictability
“Attempts remaining” logicRequired for accuracy and flow integrity
Final error behaviorMust proceed to next step with manual review
Accessibility contrastRequired to meet WCAG AA

Token Reference

UI ElementTokenValue
Brand headerbrand 500#006AFF
Title texttext-body-primary#262831
Description texttext-body-secondary#60667C
Icon (warning)icon-warning / neutral token(varies by state)
Icon (error)icon-negative#E71111
Backgroundsurface-neutral-light#FFFFFF
CTA backgroundsurface-primary-500#006AFF
CTA textbutton-primary-text-default#FFFFFF
Footer texttext-brand-accent#006AFF
Dividers / spacersborder-neutral-100#EBECEF

Design Notes

  • Error messaging should remain clear, direct, and action-oriented.
  • Use meaningful icon colors (yellow for warnings, red for errors).
  • Maintain consistent spacing and visual hierarchy for readability.
  • “Try again” should always feel like the primary action when applicable.
  • Final error screens should not offer a retry, only a “Continue” action guiding users into manual review logic.
  • Avoid long or overly technical messages; users should understand the issue at a glance.