> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mobileboost.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Interact with non-native elements

> Test web views, hybrid components, and other non-native UI elements

The MobileBoost SDK uses a visual, AI-powered approach that works regardless of the underlying UI technology. This means you can interact with elements that traditional test frameworks struggle with.

## Supported element types

* **Web views**: HTML content rendered inside a native app
* **Third-party components**: SDKs and libraries where you don't control the element identifiers
* **Graphical elements**: charts, maps, canvas-based UI, and other visual components
* **Cross-technology frameworks**: React Native, Flutter, and other hybrid frameworks

## How it works

The SDK executes your code-based test steps first. When a step targets a non-native element that can't be located through standard selectors, the SDK falls back to AI-powered visual execution. The AI interprets the screen visually and performs the intended action.

```java theme={null}
// Standard code execution handles native elements
driver.findElement(By.id("native-button")).click();

// AI command handles web views and non-accessible elements
driver.aiExecute("Tap the 'Accept cookies' button in the web view");
```

<Note>
  WebView automation through commands currently has limited support. We recommend using AI-powered natural language steps (`aiExecute`) for WebView interactions.
</Note>