setNativeProps is the React Native equivalent to setting properties directly on a DOM node.
Direct manipulation will not be a tool that you reach for frequently. You will typically only be using it for creating continuous animations to avoid the overhead of rendering the component hierarchy and reconciling many views.
setNativeProps is imperative and stores state in the native layer (DOM, UIView, etc.) and not within your React components, which makes your code more difficult to reason about.
Before you use it, try to solve your problem with setState and shouldComponentUpdate.
Forward setNativeProps to a child
Since thesetNativeProps method exists on any ref to a View component, it is enough to forward a ref on your custom component to one of the components that it renders. This means that a call to setNativeProps on the custom component will have the same effect as if you called setNativeProps on the wrapped View component itself.
MyButton inside of TouchableOpacity!
You may have noticed that we passed all of the props down to the child view using {...props}. The reason for this is that TouchableOpacity is actually a composite component, and so in addition to depending on setNativeProps on its child, it also requires that the child perform touch handling. To do this, it passes on various props that call back to the TouchableOpacity component. TouchableHighlight, in contrast, is backed by a native view and only requires that we implement setNativeProps.
setNativeProps to edit TextInput value
Another very common use case ofsetNativeProps is to edit the value of the TextInput. The controlled prop of TextInput can sometimes drop characters when the bufferDelay is low and the user types very quickly. Some developers prefer to skip this prop entirely and instead use setNativeProps to directly manipulate the TextInput value when necessary. For example, the following code demonstrates editing the input when you tap a button:
clear method to clear the TextInput which clears the current input text using the same approach.
Avoiding conflicts with the render function
If you update a property that is also managed by the render function, you might end up with some unpredictable and confusing bugs because anytime the component re-renders and that property changes, whatever value was previously set fromsetNativeProps will be completely ignored and overridden.
measureLayout(relativeToNativeComponentRef, onSuccess, onFail)
Likemeasure(), but measures the view relative to an ancestor, specified with relativeToNativeComponentRef reference. This means that the returned coordinates are relative to the origin x, y of the ancestor view.
focus()
Requests focus for the given input or view. The exact behavior triggered will depend on the platform and type of view.blur()
Removes focus from an input or view. This is the opposite offocus().

