Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/AppAndFlow/react-native-ease/llms.txt

Use this file to discover all available pages before exploring further.

By default, a single transition config applies to all animated properties. When you need finer control — for example, a snappy spring for movement but a quick fade for opacity — pass a TransitionMap instead of a single config. A TransitionMap maps property categories to individual transition configs: 
<EaseView
  animate={{ opacity: visible ? 1 : 0, translateY: visible ? 0 : 30 }}
  transition={{
    opacity: { type: 'timing', duration: 150, easing: 'easeOut' },
    transform: { type: 'spring', damping: 12, stiffness: 200 },
  }}
/>

​
Category keys

KeyProperties covered
defaultFallback for any category not explicitly listed in the map
transformtranslateX, translateY, scaleX, scaleY, rotate, rotateX, rotateY
opacityopacity
borderRadiusborderRadius
backgroundColorbackgroundColor

​
Using default as a fallback

When a category is not listed in the map, the library falls back to the default key. If no default key is present either, the library default (timing 300ms easeInOut) applies. 
<EaseView
  animate={{ opacity: 1, scale: 1.2, translateY: -20 }}
  transition={{
    default: { type: 'spring', damping: 15, stiffness: 120 },
    opacity: { type: 'timing', duration: 200, easing: 'easeOut' },
  }}
/>
In this example, scale and translateY (both in the transform category) use the spring defined under default. opacity uses its own timing config.

​
When to use per-property vs a single config

ScenarioRecommendation
All properties should move the same waySingle config
Opacity should fade faster than transforms springPer-property map
Background color needs timing while transforms springPer-property map
You want a global fallback with one overridedefault + specific key
On Android, backgroundColor is animated with ValueAnimator.ofArgb(), which only supports timing transitions. If you specify type: 'spring' for the backgroundColor key, it silently falls back to timing with a 300ms duration.

Build docs developers (and LLMs) love

Get started for freeTalk to us