# Appium Inspector

In the previous chapter we saw **UiAutomatorViewer** which comes bundled with Android SDK. Appium has built something like that which makes our work of finding locators very easy.

When you start the Appium app, you would notice the icons at the top (image below), I have highlighted the Apppium Inspector in red.

![](/files/-M4S6b8VIbaHGNwzZ4_i)

So if you notice that the appium server is running and the log shows that it's connected to the emulator running locally.When you click on the circled icon (Appium Inspector), it will launch a new UI as shown below with the application UI state captured.![](/files/-M4S6b8XDbcbhNM6_WD_)

The panel on the extreme right is clickable and you can click on the element you want to find details about. So if you see the panel with title "**Details**", there are bunch of attributes listed for the highlighted element.

![](/files/-M4S6b8ZWFR17o0YwkuC)

If you notice the attribute "**resource-id**", it's made of the package name "**com.flipkart.android**" and the value of id attribute.

This **package name** is present for all the elements and hence we can externalize it. So to construct an element identifier for automation, we are going to use it as shown below:

```
String app_package_name = "com.flipkart.android:id/";
By userId = By.id(app_package_name + "user_id");
```

So the code would look like:

```
driver.findElement(userId).sendKeys("someone@saikiranpro.com");
```

Also you can use other options like xpath, index etc. Below is the snapshot of all the options you have for identifying the element.

![](/files/-M4S6b8aihQQSFbFt7Qu)\\

Latest version in windows does not support for the appium inspector however the environment variables can be set.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://n-saikiran.gitbook.io/appium-mobile-automation/write-your-first-android-test/appium-inspectordeprecated.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.