General reference, Migrations and Deprecations

CSS Customization to Incode Studio

For accounts on UXv2, Studio replaces the CSS Customization tab and any other custom CSS work needed to style the verification experience. The result is close to your current experience, but not identical. This page explains what carries over, what does not, and what to do about the difference.

Why it changed

UXv1 accepted a stylesheet. You wrote CSS, Incode served it, and you could change anything the browser could style.

UXv2 is token-based. The experience reads a set of named values, such as colors, a corner radius, and a logo, and renders from them. This is what lets one configuration work the same way on Web, iOS, and Android. Native apps cannot run a stylesheet, so a stylesheet cannot be the shared contract.

The tradeoff is deliberate: you give up arbitrary CSS, and in return, you stop maintaining a stylesheet against every SDK release, and your branding reaches three platforms from one place.

What carries over

What you styled in CSS In Studio
Brand color on buttons, links, and active states Colors > Brand: One scale, applied across the flow
Success, warning, and error colors Colors > Positive, Warning, and Negative
Surfaces, body text, and borders Colors > Gray
Button corner radius Button corner radius: One setting, buttons only
Logo Logo: One file for light backgrounds and one for dark backgrounds
Footer branding Verified by Incode tag: Shown or hidden

What does not carry over

Currently, Studio does not support customization for the following:

  • Typography: Font family, size, and weight are not currently customizable.
  • Layout and spacing: Element positions, alignment, and padding come from the experience.
  • Illustrations and imagery: You cannot replace the illustrations in the flow.
  • Copy: Text overrides and translations are not part of Studio.
  • Per-element rules: CSS let you target one element on one screen. Tokens apply by role across the experience, so there is no equivalent for "this button on this screen only."
  • Elements the tokens do not reach: Some elements do not follow a color setting. Use the Token Glossary in Studio to see which elements each color group controls.

Migrate to Studio

Incode turns on Studio for your account. Contact your Incode representative to confirm that Studio is available to you before you start.

  1. List the CSS rules your account uses today.
  2. Compare each rule with the table above to see whether Studio covers it.
  3. In Dashboard, open Studio and set the matching controls.
  4. Preview the result on each platform and in both display modes.
  5. Click Launch and choose how your customization reaches your users. See Launch your customization.

If your case does not fit

Some CSS customizations cannot be reproduced with tokens. Send the specific screens and the specific differences to your Incode representative.

Do not keep a parallel CSS stylesheet alongside Studio. When Studio is active on a UXv2 account, it replaces the CSS Customization tab, and maintaining both produces styling that conflicts.