A Share This App button turns the people already using your app into your best promoters. Tap it, and the device’s native share sheet pops up with links to your app on the App Store and Google Play, ready to text, email, or post to a friend in a couple of taps.
It’s one of the highest-leverage buttons you can add. Word-of-mouth from people already using your app is about as close to a free install as you’ll get.
Here’s how it breaks down into two steps:
- Add the Share This App button to your app’s navigation — the button itself needs no settings.
- Set the store IDs — your Apple App Store ID and your Android package ID — since these are what the button actually shares.
The button itself has nothing to configure — everything it shares comes from two site-wide store ID values. Skip step 2, and the button will have nothing to share.
Before you start
| Requirement | Why |
|---|---|
| MAM Suite installed with MAM Main active | The Share This App button is a core content type provided by MAM Main. |
| Your app published (or in the process of publishing) to the stores | The store IDs only exist once your app has a record in App Store Connect and Google Play. You can add the button earlier, but it won’t share anything useful until the IDs are filled in. |
| Admin access to Mobile App Manager in WordPress | All steps happen in the WordPress admin. |
Step 1 — Add the Share This App button
Share This App is one of the ready-made building blocks in the no-code app builder, sitting alongside Login, Map, Web URL, Phone Call, and the rest of the content types.
- In WordPress, go to Mobile App Manager → App Setup.
- Choose where you want the button to live:
- On the tab bar at the bottom of the app, or
- In the left menu (the slide-out / hamburger menu).
- Add a new button to that location.
- For the button’s content type / content source, choose Share This App.
- Give the button a label (for example, “Share This App” or “Tell a Friend”) and, if your layout uses icons, pick a share-style icon.
- Save.
And that’s the whole button. Select Share This App, and the builder will show “No settings required” for the content source — that’s expected, not an error. The button has no options of its own, because what it shares is controlled centrally by the store IDs you’ll set in the next step.
Why no settings? Under the hood, the Share This App content type is a fixed handler — it always shares your app’s store links, and there’s nothing per-instance to configure. Add it to both the tab bar and the left menu, and both copies will behave identically.
Step 2 — Set the store IDs
Whatever the button shares comes down to two site-wide values:
| What it is | Where the value comes from |
|---|---|
| Apple App Store ID | The numeric ID Apple assigns your app (the long number in your App Store listing URL, e.g. the id123456789 portion of apps.apple.com/app/id123456789). |
| Android package ID | Your Android application/package name (e.g. com.yourcompany.yourapp), used to build the Google Play link. |
Here’s what happens on the app’s side: when it requests the Share This App button’s data, MAM Main reads these two values and hands them straight to the device.
- If the Apple App Store ID is set, an iOS share link is included.
- If the Android package ID is set, an Android share link is included.
- If a value is blank, that platform is simply left out of the share sheet.
That means a value set only for iOS still gives you a working Share button — it just won’t carry a Play Store link until you fill in the Android side too.
How these values get filled in
In most installations, you won’t need to lift a finger here — these store IDs are populated as part of publishing your app. Once TinyScreenLabs publishes your app to the App Store and Google Play, the resulting Apple App Store ID and Android package ID become available to your site, and the Share This App button starts working on its own.
You won’t type these two IDs in by hand — there is no dedicated admin field for them. The publishing process sets them for you, so don’t go looking for an “Apple App Store ID” or “Android package ID” box to edit in the admin; it isn’t there. If you’ve published but the Share button is still sharing nothing — or a shared link points at the wrong listing — reach out to TinyScreenLabs, and we’ll confirm the Apple App Store ID and Android package ID stored for your app are present and correct. A blank or wrong value here means the share sheet will either miss that platform or point at the wrong listing.
Note: Under the hood, the Share This App button reads two internal store-ID options,
local-app-apple-idandlocal-app-android-id(aliased tomam-apple-id/mam-android-idafter the 2026-05 option-key migration) — both populated by the publish flow, never entered on an admin screen. Don’t mix these up with the iTunes App URL / Android App URL fields on the push-notification settings page (mam_itunes_app_url,mam-android-app-url); those are full store URLs used for app-badge links and notification footers, a different thing entirely from the IDs the Share button uses.
Test it
- Make sure both store IDs are set (or at least the one platform you want to share).
- Open your app on a device (or in the preview, if your preview supports the native share sheet).
- Tap the Share This App button.
- Confirm the native share sheet opens and that the shared links point to the correct App Store and Google Play listings.
- Send the link to yourself and tap it — it should open your app’s store page, not a 404 or the wrong app.
Empty share sheet, no links, or only one platform when you expected both? That means the matching store ID is missing or blank — head back to Step 2.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Button appears but shares nothing | Both store IDs are blank | Confirm the Apple App Store ID and Android package ID are set (Step 2). |
| Only iOS (or only Android) link is shared | The other store ID is blank | Confirm that platform has been published; the missing store ID is filled in by the publish flow. |
| Shared link opens the wrong app or a 404 | Wrong store ID stored for your app | These IDs are set by publishing and aren’t admin-editable — contact TinyScreenLabs to correct the stored Apple App Store ID or Android package ID. |
| “No settings required” shown when adding the button | Expected behavior | The button has no per-button options; configure the store IDs centrally instead. |
| Button doesn’t appear in the builder’s content-type list | MAM Main not active | Confirm MAM Suite / MAM Main is installed and active. |
Related
- Building Your App — Add a Social Media button (links out to your social profiles)
- Building Your App — Add a Web URL button (open any page in an in-app browser)
- Plugin Reference — MAM Main content types (the full list of app building blocks)
- App Setting Reference — iTunes App URL / Android App URL (the store URL fields used for app badges and notifications, not the Share button)
Verification
This article was drafted against:
mam-main/includes/content-classes/local-app-share-this-app-class.php— the Share This App content class.get_data_for_app()includesiosfromlocal-app-apple-idandandroidfromlocal-app-android-id, each only when the option is set;get_content_type_form()returns"No settings required".mam-main/includes/content-classes/README.md— content-class registry and the no-code builder model.mam-main/mam-main.php— the 2026-05 option-key migration aliasinglocal-app-apple-id→mam-apple-idandlocal-app-android-id→mam-android-id.mam-main/includes/app-settings/push-notifications-manager.php— confirmsmam_itunes_app_url/mam-android-app-urlare separate store-URL fields, not the IDs the Share button uses.
Re-verify whenever the Share This App content class’s get_data_for_app() keys change, the local-app-apple-id / local-app-android-id option keys are renamed again, or an admin field for entering the store IDs is added or moved.
