The WordPress Mobile App: What It Does Well, and What It Does Not

Decide what you want it for before you install it. The WordPress app is a good drafting, media and moderation tool. It is a poor site-administration tool, and people who download it expecting a phone-sized wp-admin usually delete it the same week.

The distinction that confuses everyone

Two different things share the name. WordPress.com is a hosted service run by Automattic. WordPress is the open-source software you install on your own hosting — what people mean by self-hosted, or WordPress.org.

The app is published by Automattic and serves both, which is why the sign-in screen offers two routes: sign in with a WordPress.com account, or enter your own site address.

• WordPress.com sites. Sign in with the account that owns them. Everything the plan includes is simply there.
• Self-hosted sites. Enter the site URL and authenticate against that site. Some capabilities are supplied by the Jetpack connection rather than by WordPress core, so a site without that connection gets the basics — writing, media, comments — and not much analytics.

That second point is the whole misunderstanding. Someone installs the app, connects a self-hosted site, finds a feature missing, and concludes the app is broken. It is not broken; the feature was never part of core WordPress.

One more thing worth knowing: Automattic has split and re-split functionality between the WordPress app and the separate Jetpack app over the years. Rather than trusting any feature list you read, including a year-old one, check which app currently carries the thing you need.

When the login fails but the password is right

Self-hosted connections have historically depended on XML-RPC, an old remote-publishing interface that many hosts and security plugins disable by default because it attracts brute-force traffic. If credentials that work in a browser are refused by the app, that is the first suspect.

The direction of travel is towards the REST API with application passwords — per-application credentials generated in your user profile and revocable individually, without changing your real password. If the app offers that route, take it.

The site must also be served over HTTPS with a valid certificate. A mixed-content or certificate warning that a desktop browser lets you click past will simply fail in an app.

What the app is genuinely good at

• Drafting. Capturing a post on a train and finishing it later is the app's best use by a distance.
• Small corrections. Fixing a typo or a wrong link without opening a laptop.
• Comment moderation. Approving, replying and spam-binning from a notification is faster than any desktop workflow.
• Media from the camera roll. Uploading photos straight from the device, though be aware modern phone photos are enormous — image optimisation matters more, not less, when publishing from a phone.
• Offline drafts. Written without signal and synced when the connection returns.

What it is not for

• Plugins and themes. Installing, updating and configuring them belongs in a browser.
• Page builders. Elementor, Divi and similar editors do not run in the app.
• Complex block layouts. Simple blocks are fine; anything with nested containers and precise spacing is not.
• Store administration. Order management is a different job with its own tooling.
• Anything structural. Files, database, configuration and debugging all need a real terminal or control panel.

The WordPress Android app in particular

The Android and iOS builds track each other closely, so most differences you will hit on WordPress Android are platform behaviours rather than WordPress ones.

The share sheet is the genuinely useful Android feature: share a link, an image or selected text from any other app and start a draft from it. It turns the phone into a capture device, which is what the app is best at.

Two Android settings cause most of the "it stopped notifying me" reports. Notification permission must be granted explicitly on recent versions, and aggressive battery optimisation — which several manufacturers apply by default beyond stock Android — will suspend background sync. If notifications dry up, check both before reinstalling.

None of this affects how your site looks to visitors. If the site itself renders badly on a phone, that is a theme and CSS problem, covered in mobile display issues, and no app setting will change it.

Treat the phone as a live admin session

A signed-in app is a standing connection to your site, sitting in a pocket, in a coffee shop, on a device you might leave in a taxi.

Sign in with an account that holds the smallest role that does the job. An Editor account can write, edit and moderate; it cannot install a plugin or add a user. Understanding the roles is worth ten minutes here. Use application passwords so a lost device can be revoked in isolation, and keep a device lock on.

The honest recommendation

Install it if you publish regularly and want to write or moderate away from a desk. Skip it if you are looking for remote site management — that need is better served by your host's control panel and a browser.

And if the app is your first contact with WordPress at all, start on a desktop instead, following how to build the site itself, then add the app once you know what it is standing in for.