# Key Differences Between Web and Mobile Strategy Editors in Leapwork

In this article, you will learn about the key differences between working with **web** and **mobile automation strategies** in **Leapwork**, specifically when editing captured elements in the Strategy Editor. If you’ve ever wondered why the **XPath works perfectly for web** **elements** but fails when testing on **mobile**, or why you can’t add custom attributes to mobile elements like you do on the web, this happens often.

These differences can lead to confusion and unexpected behavior when building or troubleshooting automation flows. The good news is that once you understand platform-specific behaviors, you can work around them more efficiently.

## Let’s understand the key differences:

### Web vs. Mobile Strategy Editors: Key Differences

|     |     |
| --- | --- |
| **Web Strategy Editor** | **Mobile Strategy Editor** |
| When you click **"Show XPath"**, the XPath shown is **successfully validated across all strategies** listed in the strategy editor. | When you click **"Show XPath"**, the XPath is **validated only for strategies named "Mobile."** Validation fails for all other strategy types. |
| You can **add attributes** to a web element strategy by clicking the **"+"** button in the strategy editor. | The **"+"** button is currently not visible, so you cannot add custom attributes to Mobile Element Strategies. |

While web and mobile strategy editors may look similar, they behave differently. Knowing these key differences helps you avoid common issues and build more reliable automation flows.

If you have any questions, please contact [Priority Support](mailto:prioritysupport@leapwork.com).