---
title: "Autify NoCode Mobile Stability Plan"
slug: "autify-for-mobile-stability-plan"
updated: 2025-12-24T05:58:49Z
published: 2025-12-24T05:58:49Z
canonical: "help.autify.com/autify-for-mobile-stability-plan"
---

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

# Autify NoCode Mobile Stability Plan

*※ Please note that parts of this page are machine translated.*

- This article contains information about features that were available before December 2023. This article contains information about beta features.

## Issues with tap assertions that we have provided

Until December 2023, Autify NoCode Mobile has provided tap assertion functionality using the following two methods of element identification.

- Page Source
  - Identifies elements based on source code information.
- Machine Learning (ML)
  - Machine Learning is used to analyze screenshots of the application and identify elements.
    - Machine Learning(ML) tap
    - [Machine Learning(ML) Assertion](/mobile/docs/ml-assertion)

However, the following problems occurred and needed to be improved

- Incorrect elements may be selected in both page source and ML.
- Updating element information or changing the way elements are identified requires re-recording the scenario, which takes time to correct.
- When improving machine learning, it is difficult to prevent adverse effects on existing scenarios, making speedy release of improvements difficult (problems related to ML taps and ML assertions; see below).

To address these issues, Autify NoCode Mobile plans to improvements to tap assertions. This page provides information on features that have been released and their corresponding usage methods.

## Release notes

### "Tap" and "Quick element update"

[In January 2024, we launched Tap and Quick Element Update features, which are new taps with a new element detection method.](/mobile/docs/en/tap-step) "Tap" allows users to select elements with higher precision than before, and "Quick Element Update" allows users to update element information without re-recording when elements are missing due to changes in appearance. In addition, XPath can be used to select an element in a way that is independent of its appearance, in cases where appearance is not suitable as a clue, such as when the appearance changes significantly.

### Prompt assertion

In October 2025, we launched Prompt Assertion (Beta), a feature that allows you to perform assertions on screen screenshots using free-form prompts. Please use this feature particularly when locating elements is difficult with Page Source or ML Assertion, or when assertion results are unstable. For usage instructions, please refer to [this page](/mobile/docs/en/release-notes-october-14-2025#%F0%9F%A4%96prompt-assertion). If you would like to use this feature enabled, please contact support.

## How to troubleshoot issues with tap and assertion steps

Please try the following methods for each feature. If the problem is not resolved, please contact chat support.

- Tap-related issues
  - Try using "Tap" and "Quick Element Update."
  - If you have any questions about the above or the issue is not resolved, please contact chat support.
- Assertion-related issues
  - Please consider using Prompt Assertion.
  - If you have concerns, such as Prompt Assertion not being suitable, please contact chat support.