View

The most fundamental component for building a UI, View is a container that supports layout with flexbox, style, some touch handling, and accessibility controls. View maps directly to the native view equivalent on whatever platform React Native is running on, whether that is a UIView, <div>, android.view, etc.

View is designed to be nested inside other views and can have 0 to many children of any type.

This example creates a View that wraps two boxes with color and a text component in a row with padding.

import React from 'react';
import {View, Text} from 'react-native';

const ViewBoxesWithColorAndText = () => {
  return (
    <View
      style={{
        flexDirection: 'row',
        height: 100,
        padding: 20,
      }}>
      <View style={{backgroundColor: 'blue', flex: 0.3}} />
      <View style={{backgroundColor: 'red', flex: 0.5}} />
      <Text>Hello World!</Text>
    </View>
  );
};

export default ViewBoxesWithColorAndText;

Views are designed to be used with StyleSheet for clarity and performance, although inline styles are also supported.

Synthetic Touch Events

For View responder props (e.g., onResponderMove), the synthetic touch event passed to them are in form of PressEvent.

Reference

Props

accessibilityActions

Accessibility actions allow an assistive technology to programmatically invoke the actions of a component. The accessibilityActions property should contain a list of action objects. Each action object should contain the field name and label.

See the Accessibility guide for more information.

accessibilityElementsHidden

A value indicating whether the accessibility elements contained within this accessibility element are hidden. Default is false.

accessibilityHint

An accessibility hint helps users understand what will happen when they perform an action on the accessibility element when that result is not clear from the accessibility label.

accessibilityLabel

Overrides the text that's read by the screen reader when the user interacts with the element. By default, the label is constructed by traversing all the children and accumulating all the Text nodes separated by space.

accessibilityLiveRegion

Indicates to accessibility services whether the user should be notified when this view changes. Works for Kepler and Android API >= 19 only. Possible values:

• 'none' - Accessibility services should not announce changes to this view.
• 'polite'- Accessibility services should announce changes to this view.
• 'assertive' - Accessibility services should interrupt ongoing speech to immediately announce changes to this view.

accessibilityRole

accessibilityRole communicates the purpose of a component to the user of an assistive technology.

accessibilityRole can be one of the following:

• adjustable Used when an element can be "adjusted" (e.g. a slider).
• alert Used when an element contains important text to be presented to the user.
• button Used when the element should be treated as a button.
• checkbox Used when an element represents a checkbox which can be checked, unchecked, or have mixed checked state.
• combobox Used when an element represents a combo box, which allows the user to select among several choices.
• header Used when an element acts as a header for a content section (e.g. the title of a navigation bar).
• image Used when the element should be treated as an image. Can be combined with button or link, for example.
• imagebutton Used when the element should be treated as a button and is also an image.
• keyboardkey Used when the element acts as a keyboard key.
• link Used when the element should be treated as a link.
• menu Used when the component is a menu of choices.
• menubar Used when a component is a container of multiple menus.
• menuitem Used to represent an item within a menu.
• none Used when the element has no role.
• progressbar Used to represent a component which indicates progress of a task.
• radio Used to represent a radio button.
• radiogroup Used to represent a group of radio buttons.
• scrollbar Used to represent a scroll bar.
• search Used when the text field element should also be treated as a search field.
• spinbutton Used to represent a button which opens a list of choices.
• summary Used when an element can be used to provide a quick summary of current conditions in the app when the app first launches.
• switch Used to represent a switch which can be turned on and off.
• tab Used to represent a tab.
• tablist Used to represent a list of tabs.
• text Used when the element should be treated as static text that cannot change.
• timer Used to represent a timer.
• togglebutton Used to represent a toggle button. Should be used with accessibilityState checked to indicate if the button is toggled on or off.
• toolbar Used to represent a tool bar (a container of action buttons or components).
• grid Used with ScrollView, VirtualizedList, FlatList, or SectionList to represent a grid.

accessibilityState

Describes the current state of a component to the user of an assistive technology.

See the Accessibility guide for more information.

accessibilityValue

Represents the current value of a component. It can be a textual description of a component's value, or for range-based components, such as sliders and progress bars, it contains range information (minimum, current, and maximum).

See the Accessibility guide for more information.

accessible

When true, indicates that the view is an accessibility element. By default, all the touchable elements are accessible.

aria-busy

Indicates an element is being modified. Assistive technologies may want to wait until the changes are complete before informing the user about the update.

aria-checked

Indicates the state of a checkable element. This field can either take a boolean or the "mixed" string to represent mixed checkboxes.

aria-disabled

Indicates that the element is perceivable but disabled, so it is not editable or otherwise operable.

aria-expanded

Indicates whether an expandable element is currently expanded or collapsed.

aria-hidden

Indicates whether the accessibility elements contained within this accessibility element are hidden.

For example, in a window that contains sibling views A and B, setting aria-hidden to true on view B causes VoiceOver to ignore the elements in the view B.

aria-label

Defines a string value that labels an interactive element.

aria-labelledby

Identifies the element that labels the element it is applied to. Note: If the value of aria-labelledby doesn't match the nativeID value of the related element the element won't be labled.

<View>
  <Text nativeID="formLabel">Label for Input Field</Text>
  <TextInput aria-label="input" aria-labelledby="formLabel" />
</View>

aria-live

Indicates that an element will be updated, and describes the types of updates the user agents, assistive technologies, and user can expect from the live region.

• off Accessibility services should not announce changes to this view.
• polite Accessibility services should announce changes to this view.
• assertive Accessibility services should interrupt ongoing speech to immediately announce changes to this view.

aria-selected

Indicates whether a selectable element is currently selected or not.

aria-valuemax

Represents the maximum value for range-based components, such as sliders and progress bars. Has precedence over the max value in the accessibilityValue prop.

aria-valuemin

Represents the minimum value for range-based components, such as sliders and progress bars. Has precedence over the min value in the accessibilityValue prop.

aria-valuenow

Represents the current value for range-based components, such as sliders and progress bars. Has precedence over the now value in the accessibilityValue prop.

aria-valuetext

Represents the textual description of the component. Has precedence over the text value in the accessibilityValue prop.

collapsable

Views that are only used to layout their children or otherwise don't draw anything may be automatically removed from the native hierarchy as an optimization. Set this property to false to disable this optimization and ensure that this View exists in the native view hierarchy.

focusable

Whether this View should be focusable with a non-touch input device, eg. receive focus with a hardware keyboard.

hitSlop

This defines how far a touch event can start away from the view. Typical interface guidelines recommend touch targets that are at least 30 - 40 points/density-independent pixels.

For example, if a touchable view has a height of 20 the touchable height can be extended to 40 with hitSlop={{top: 10, bottom: 10, left: 0, right: 0}}

The touch area never extends past the parent view bounds and the Z-index of sibling views always takes precedence if a touch hits two overlapping views.

id

Used to locate this view from native classes. Has precedence over nativeID prop.

This disables the 'layout-only view removal' optimization for this view!

keplerAltLabels - Kepler Only

The value for keplerAltLabels refers to the list of alternate names for the item.

Note: This property replaces keplerAtlLabels. keplerAtlLabels is deprecated and will be removed in a future release.

This prop is required if the app wants to allow user to perform voice selection on the same item with different names.

nativeID

Used to locate this view from native classes.

This disables the 'layout-only view removal' optimization for this view!

needsOffscreenAlphaCompositing

Whether this View needs to rendered offscreen and composited with an alpha in order to preserve 100% correct colors and blending behavior. The default (false) falls back to drawing the component and its children with an alpha applied to the paint used to draw each element instead of rendering the full component offscreen and compositing it back with an alpha value. This default may be noticeable and undesired in the case where the View you are setting an opacity on has multiple overlapping elements (e.g. multiple overlapping Views, or text and a background).

Rendering offscreen to preserve correct alpha behavior is extremely expensive and hard to debug for non-native developers, which is why it is not turned on by default. If you do need to enable this property for an animation, consider combining it with renderToHardwareTextureAndroid if the view contents are static (i.e. it doesn't need to be redrawn each frame). If that property is enabled, this View will be rendered off-screen once, saved in a hardware texture, and then composited onto the screen with an alpha each frame without having to switch rendering targets on the GPU.

### nextFocusDown

Designates the next view to receive focus when the user navigates down.

nextFocusForward

Designates the next view to receive focus when the user navigates forward.

nextFocusLeft

Designates the next view to receive focus when the user navigates left.

`nextFocusRight

Designates the next view to receive focus when the user navigates right.

`nextFocusUp

Designates the next view to receive focus when the user navigates up.

onAccessibilityAction

Invoked when the user performs the accessibility actions. The only argument to this function is an event containing the name of the action to perform.

See the Accessibility guide for more information.

onAccessibilityTap

When accessible is true, the system will try to invoke this function when the user performs accessibility tap gesture.

onLayout

Invoked on mount and on layout changes.

This event is fired immediately once the layout has been calculated, but the new layout may not yet be reflected on the screen at the time the event is received, especially if a layout animation is in progress.

onStartShouldSetResponder

Does this view want to become responder on the start of a touch?

onStartShouldSetResponder

Does this view want to become responder on the start of a touch?

onMoveShouldSetResponderCapture

If a parent View wants to prevent a child View from becoming responder on a move, it should have this handler which returns true.

onResponderGrant

The View is now responding for touch events. This is the time to highlight and show the user what is happening.

On Android, return true from this callback to prevent any other native components from becoming responder until this responder terminates.

onResponderMove

The user is moving their finger.

onResponderReject

Another responder is already active and will not release it to that View asking to be the responder.

onResponderRelease

Fired at the end of the touch.

onResponderTerminate

The responder has been taken from the View. Might be taken by other views after a call to onResponderTerminationRequest, or might be taken by the OS without asking.

onResponderTerminationRequest

Some other View wants to become responder and is asking this View to release its responder. Returning true allows its release.

onStartShouldSetResponder

Does this view want to become responder on the start of a touch?

onStartShouldSetResponderCapture

If a parent View wants to prevent a child View from becoming responder on a touch start, it should have this handler which returns true.

pointerEvents

Controls whether the View can be the target of touch events.

• 'auto': The View can be the target of touch events.
• 'none': The View is never the target of touch events.
• 'box-none': The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:

.box-none {
     pointer-events: none;
}
.box-none * {
     pointer-events: auto;
}

• 'box-only': The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:

.box-only {
     pointer-events: auto;
}
.box-only * {
     pointer-events: none;
}

removeClippedSubviews

This is a reserved performance property exposed by RCTView and is useful for scrolling content when there are many subviews, most of which are offscreen. For this property to be effective, it must be applied to a view that contains many subviews that extend outside its bound. The subviews must also have overflow: hidden, as should the containing view (or one of its superviews).

role

role communicates the purpose of a component to the user of an assistive technology. Has precedence over the accessibilityRole prop.

hasTVPreferredFocus

Set to true to force the TV focus engine to move focus to this view. See the Documentation.

onBlur

Invoked when the item loses focus.

onFocus

Invoked when the item receives focus.

enableSynchronousFocusEventsKepler

When set to true, onFocus and onBlur events are dispatched synchronously. UI Thread will be blocked until the execution of onFocus or onBlur from JavaScript has completed.

style

tabIndex

Whether this View should be focusable with a non-touch input device, e.g. receive focus with a hardware keyboard. Supports the following values:

• 0 - View is focusable
• -1 - View is not focusable

testID

Used to locate this view in end-to-end tests.

This disables the 'layout-only view removal' optimization for this view!

Methods

.requestTVFocus()

requestTVFocus();

Requests focus for the specified input or view. The exact behavior triggered depends on the platform and the type of view.

Last updated: Sep 30, 2025