App Store 4.2.7 rejection: Remote desktop clients

By The Draftbit team · Updated 22 September 2026
Sources checked 22 September 2026

This guide is for iPhone and iPad remote-desktop apps mirroring specific software or services rather than providing a generic mirror of a host device.

A remote-desktop rejection can turn on where the software runs and who owns the host. Guideline 4.2.7 sets conditions for clients mirroring specific software or services. We’d draw the host, client, and network connection before changing the interface.

4.2.7(a): host and network

The host must be the user’s own personal computer or dedicated game console, with host and client on a local LAN-based network. Verify the real connection route rather than only the setup description.

4.2.7(b): execution on the host

The software runs and renders on the host. The client can’t use platform capabilities beyond those needed for the remote stream.

4.2.7(c): account management

Initiate account creation and management from the host. Check onboarding and recovery links as well as the normal session.

4.2.7(d): the client interface

Avoid a store-like interface or browsing and purchasing software the user doesn’t already own or license. The clause distinguishes transactions processed on the mirrored host from client-side purchases.

4.2.7(e): cloud thin clients

Apple states that thin clients for cloud-based apps aren’t appropriate under this rule. Don’t describe a cloud host as the user’s local computer.

Verify the architecture

Test pairing, accounts, and a session with the supported host. Explain the host ownership, network, execution location, and review setup. If the product uses a different model, identify its applicable policy rather than assuming this exception covers it.