Here’s what this tutorial walks you through: taking a configured MAM app and putting it in front of Apple and Google for the first time. That means filling in the handful of store-listing details the page asks for, clearing a readiness checklist, saving your settings, and clicking Publish for each platform. From there, MAM’s build pipeline — Fastlane — takes over, packaging and uploading the build on your behalf.

This is the hands-on version, start to finish. Want just a quick field-by-field reference instead? Skip to Related at the bottom.

What you’ll have at the end

• Your app name, description, and icon entered and saved on the Publish App page.
• The Apple and/or Google developer-account connection in place so MAM can publish on your behalf.
• An iOS build, an Android build, or both, submitted into the MAM Fastlane pipeline.
• A Publish status card on the page that shows each submission moving from “submission in progress” toward “live” in the store.

One thing this tutorial won’t give you: a live app. Once MAM uploads your build, Apple and Google each run their own review — that part is out of MAM’s hands, and it typically takes a few days. What you’ll walk away with is a submitted build and a clear idea of where to watch for the rest.

Prerequisites

Before you start, you should already have:

• Admin access to your WordPress site. The Publish App page requires the manage_options capability, so you must be a full administrator.
• A configured app. You’ve already set up your app’s navigation, content, and settings in Mobile App Mgr → App Navigation. Publishing sends whatever you’ve built; it doesn’t build it for you.
• Your required plugins purchased. If your app uses features that depend on paid MAM plugins, those need to be licensed. The page will tell you if anything is missing (see Step 2).
• An Apple Developer account, a Google Play developer account, or both. You keep ownership of these accounts; you invite MAM in so the team can publish for you. Apple Developer Program membership and a Google Play Console developer account are paid signups with Apple and Google, separate from MAM.

You do not need to know anything about bundle IDs, version numbers, signing certificates, or Fastlane — MAM generates and manages all of that, and it only ever shows up on the page as read-only reference values.

Steps

1. Open the Publish App page

In your WordPress admin, go to Mobile App Mgr → 🚀 Publish App (it’s at the bottom of the MAM menu, marked with a rocket).

The moment the page loads, MAM checks that your site is correctly connected to your account and quietly re-links it if the codes don’t match. All of that happens in the background, so there’s nothing for you to do. Worth remembering for later: if a publish attempt ever fails with an account-connection error, that’s a connection problem for support to sort out, not something a form field can fix.

Otherwise, you’ll land on a page built around a progress checklist near the top, with several settings panels below it.

2. Work through the readiness checklist

This checklist is your map for the rest of the page: a Setup incomplete / Setup complete progress bar up top, followed by items grouped into sections. Each one is either done (green check), waiting on something, or still open. Publishing won’t really work until the checklist clears, so this is where to start.

The checklist covers:

• Subscription & add-ons — confirms the plugins your app needs are purchased and active. If something is missing, the item gives you a Purchase on WP Mobile App Manager button that opens checkout pre-filled for your account.
• Developer accounts — whether your Apple and Google accounts are connected (covered in Step 3).
• App information — whether your app name, description, and icon are filled in (covered in Steps 4–6). Each unfinished item has a “Fill in below” / “Upload below” link that jumps you to the right panel.

Because items further down feed back into this checklist, bouncing back and forth between them is completely normal. Don’t chase a perfect checklist before moving on — just fill things in, save, and let it re-evaluate itself.

3. Connect your developer account(s)

Under Developer accounts, Apple and Google each show one of three states:

• Connected — nothing to do; you’re ready to publish to that store.
• Not started — you need to invite MAM into your developer account.
• Waiting on us — you’ve told MAM you sent the invite, and the team is verifying it (usually within one business day).

Ready to connect a platform that’s still “not started”? Here’s how:

1. Click Open App Store Connect (Apple) or Open Google Play Console (Google). The matching store console opens in a new tab.
2. In that console, invite the email address shown on the checklist as an admin or user on your developer account — there’s a Copy button right next to it so you don’t have to retype anything. This invite is what lets MAM publish on your behalf.
3. Back on the MAM page, click I Sent the Invite and the item flips to “waiting on us” — MAM notifies the team to verify and accept it.

Not sure how to send the invite? Each item links a setup tutorial — lean on it the first time through.

You only need to connect the platform you’re actually planning to publish to. If Google Play is the plan for right now, connect Google and leave Apple for later.

4. Enter your App Store information

Scroll to the App Store Information panel and fill in:

• App Name — the name shown on your App Store and Google Play listings.
• App Description — what your app does, who it’s for, and why it’s useful. One description covers both Apple and Google, so write it with both audiences in mind.

These two fields are required for both platforms.

5. Set your iOS permission descriptions

Open the iOS Permission Descriptions panel and you’ll find a short message waiting for each protected feature your app can use — camera, location, photos, contacts, and so on. Apple requires these: the first time iOS asks a user for one of these permissions, whatever you’ve written here is the explanation shown in that prompt.

MAM starts you off with reasonable defaults, but they’re worth a look — adjust the wording so each one actually explains why your app needs that permission. Vague or empty messages are a common reason App Store review bounces a submission. And since these messages only apply to iOS, you can skip this whole panel if Google Play is your only target.

6. Upload your app icon and set the launch screen

Head to the App Icon panel, click the picker, and choose a square 1024×1024 PNG from your media library — this one image gets used by both stores and resized automatically for every device. You can also set a Background Color, which matters if your icon has any transparency: MAM flattens it onto that color, because Apple rejects icons with a transparent (alpha) channel.

In the Launch Screen panel, decide how you want your loading screen built:

• Auto-generate from app icon and background color (default) — MAM builds a splash screen from your icon and a background color you pick. This is the simplest option and updates automatically when you change your icon.
• Upload a custom splash screen — pick your own image (a tall portrait PNG/JPG) if you want full control over the loading screen.

You might also spot an App Identifiers & Versions panel listing bundle IDs, team ID, and version/build numbers — MAM manages all of that automatically, so it’s there for reference only, nothing for you to edit.

7. Save your app settings

Click Save App Settings at the bottom of the page, and it’ll reload showing App settings saved. Saving is doing real work behind the scenes too — regenerating your auto-generated launch screen and flattening your icon if you changed either — so make it a habit to save before you publish.

Take a look at the checklist up top — it should now read Setup complete, or at minimum show no outstanding items for the platform you’re about to publish to. If something’s still incomplete, the checklist will tell you exactly what’s left; finish it up and save again.

8. Publish to each store

When a platform is ready, the Publish status card shows a row for it with a publish button:

• Publish to App Store for iOS.
• Publish to Google Play for Android.

Click the button for whichever platform you’re ready to submit. That sends a publish request into the MAM pipeline, and the row switches to submission in progress, showing when you submitted and roughly how long the wait should be.

A few things worth knowing right now:

• Publishing runs in the background. You’re free to close the page and go about your day. Builds run on a schedule (typically Monday–Friday, business hours, US Central time), and the initial upload usually finishes within about 20–30 minutes once a build slot picks it up.
• Publish each platform separately. iOS and Android each get their own button and their own submission.
• If a publish request can’t go through, the page shows a Publish request failed error along with a reason. Re-check your account connection and try again — if it keeps failing, contact support.

9. Watch the submission progress

Whenever you’re curious, refresh the Publish App page to see the latest state in the Publish status card. As MAM and the stores work through your build, the row moves through states such as:

• iOS: uploaded to TestFlight, submitted to Apple for review, then live in the App Store.
• Android: pushed to Closed Testing, submitted to Google Play for review, then live on Google Play.

Once a platform goes live, that same row offers Publish another update — and that’s the button you’ll use to ship every future version.

What’s next

• Wait for store review. Once MAM uploads your build, Apple and Google each review it on their own clock (commonly 1–3 days) — you’ll usually get an email from the store too when there’s news. Approval, and going “live,” happens on the store’s side, not in MAM.
• Test before it’s public. Your build usually lands in TestFlight (iOS) and Closed Testing (Android) first — a chance for you and your testers to install and try the real app before it ever reaches the public store.
• Publish updates later. Whenever you change your app, come back to this page, save, and click Publish another update for each platform — MAM takes care of incrementing version and build numbers.

Related

• Recipe: Publish your app to iOS and Android — a field-by-field reference for the same page, aimed at admins who want the underlying option keys and behavior.
• Hook: mam_fastlane_settings — for developers extending the build payload with extra configuration.
• The Apple and Google “developer account” setup tutorials linked from the checklist’s Developer accounts section.