Skip to main content

Doubao Assistant's Screen Automation Era Begins: What You Need to Know

Doubao Assistant's Screen Automation Era Begins: What You Need to Know

On October 14, Doubao Mobile Assistant closed the books on a 30-day public comment period for its Screen Automation Execution Protocol (SAEP). The protocol, which launched alongside the consumer version of Doubao Mobile Assistant on September 14, is now moving into a new phase: third-party applications will gradually gain access to screen automation operations.

For context, the Nubia NaviX Ultra—the first device to ship with this version—hit shelves on September 16, giving users an early taste of what automated screen interactions can do.

Image

What changes after the comment period?

During the comment period, Doubao Assistant played it safe. It only performed automated operations on system-built-in apps, ByteDance's own apps, and third-party apps that had explicitly agreed to join the protocol. Everyone else was left untouched by default.

Now that the comment period has ended, the assistant will start granting operation permissions to apps that neither responded to the email nor joined the protocol—but it's not a free-for-all. Permissions will be rolled out gradually, based on each app's risk level. Apps that clearly refused to participate will never be included in the operation scope. Developers can still declare refusal at any time, and the assistant will promptly disable the relevant operations. The current list of refused applications is available through official channels and will be updated regularly.

Why the gradual approach matters

Screen automation is a powerful capability. It lets an assistant interact with apps on your behalf—tapping, scrolling, and navigating—without you lifting a finger. But with great power comes great responsibility (yes, the cliché fits here). By rolling out permissions based on risk level, Doubao is trying to balance innovation with user safety. Apps that pose higher risks will presumably face more scrutiny before gaining automation access.

What about apps that refused?

If an app has explicitly said no, Doubao Assistant will respect that decision permanently. Developers retain the right to opt out at any time, and the assistant will immediately stop automating those apps. This gives developers control over how their apps are used and ensures users aren't surprised by unexpected automation.

Key Points

  • Public comment period ended: Doubao Mobile Assistant's SAEP finished its 30-day comment period on October 14.
  • Gradual rollout: Third-party apps that didn't respond or join will get automation permissions based on risk level.
  • Refusal is forever: Apps that explicitly refused will never be automated; developers can opt out anytime.
  • Transparency: The refusal list is publicly available and regularly updated.
  • Device debut: The Nubia NaviX Ultra was the first device to feature this version of Doubao Assistant.

As screen automation becomes more common, users will likely see more assistants offering similar features. Doubao's approach—cautious, transparent, and developer-friendly—could set a precedent for how these tools are rolled out in the future. For now, if you're a developer, you might want to check that refusal list and make your voice heard. And if you're a user, get ready for a future where your phone does more of the tapping for you.