Goal

Tidy up the list of screens in your app: change the order they appear in, rename a button so its label reads better, or delete a screen you no longer need. In MAM Suite, a “button” and the “screen” it opens are the same thing — so everything here happens by editing buttons on the Main Navigation or Left Menu tab of App Setup. None of it needs an App Store or Play Store rebuild; these changes ship as app content the next time you publish.

Before you start

• Where you work. You’ll do all three tasks in the WordPress admin under Mobile App Manager → App Setup — on the Main Navigation tab (the main grid and bottom tab bar) or the Left Menu tab (the slide-out drawer).
• You need admin rights. These actions are limited to users who can manage options — administrators. Editors and shop managers won’t see them, let alone be able to save changes.
• Buttons are per-role and per-placement. Buttons are stored separately for each managed user role, and separately again for Main Navigation versus the Left Menu. If your app uses roles, pick the right one from the Content for Role dropdown before you start — whatever you reorder, rename, or delete while that role and placement are selected only affects that role and that placement.
• Publishing makes it live. Reordering, renaming, and deleting update your saved layout right away in the admin, but app users won’t see any of it until you publish — so there’s no rush, and nothing goes live by accident. Preview first with the App Setup → Previewer App tab if you want a look before you commit.
• A note on naming. The UI labels below (tab names, the delete link, role names) are what you’ll see in a standard install. Your theme or version might word things slightly differently, but the flow is the same.

Reorder screens

Reordering is just about sequence: it decides what comes first — top to bottom in the Left Menu, and left-to-right / row by row on the Main Navigation grid and tab bar.

1. Go to Mobile App Manager → App Setup and open the placement you want to reorder (Main Navigation or Left Menu).
2. If your app uses roles, choose the role from the Content for Role dropdown so you’re editing the right layout.
3. On each button row, look for the move handle — the up/down arrows icon that acts as the reorder grip.
4. Drag a button by that handle to its new position in the list. The list re-sorts as you drop it, and the new order is saved automatically.
5. Repeat until the order is what you want, then publish when you’re ready for app users to see it.

Whatever order you set here is exactly what the app renders. On Main Navigation, that decides where each tile sits in the grid and bottom tab bar; in the Left Menu, it decides the row order of the drawer.

Rename a screen

A button’s name is just the label your users see — the caption under its tile on the home screen, or the row text in the left menu. Rename it and only that label changes; what the screen shows and where it points stay exactly the same.

1. In App Setup, open the placement and (if applicable) select the role, as above.
2. Find the button you want to rename. Its name is shown in the title field at the top of the button row.
3. Click into the title field and type the new name.
4. Click out of the field (or move to another button) to save. The new label is stored on that button.
5. Publish to push the new label to the app.

Renaming doesn’t touch the content type or content source — the button still opens the exact same screen, only its caption changes. If your app is translated with WPML, keep in mind the button name is registered as a translatable string, so a rename may need its translation updated too.

Delete a screen

Deleting a screen removes the button and the screen it opens from the current placement and role — nothing more. Your underlying WordPress content is safe: the page, posts, category, or directory the screen pointed at stays exactly where it is. All you’re removing is this one entry point into the app.

1. In App Setup, open the placement and select the role, as above — and make sure it’s the exact role and placement that has the screen you want gone, since deleting only affects the current role and placement.
2. Expand the button you want to remove so its options are showing.
3. Click the Delete Button link in the button’s options.
4. The button is removed from the list and the change is saved.
5. Publish to remove the screen from the live app.

This only removes the entry point for the selected role and placement. The same screen may still exist for another role, or in the other placement (Main Navigation vs. Left Menu) — worth checking there if a screen seems to “still be there” for some of your users.

Notes and gotchas

• A screen “disappeared” after you switched roles. Buttons live per role and per placement, so if one goes missing, check that you’re looking at the same Content for Role and the same tab (Main Navigation vs. Left Menu) you created it under.
• Order, rename, and delete all save on their own. There’s no form to submit for any of these — each action writes straight to the saved layout the moment you make it. The live app just won’t show it until you publish.
• Deleting is per-role and per-placement, not global. There’s no single “delete this screen everywhere” switch. To retire a screen for good, remove it from each role and from both placements where it appears.
• Renaming won’t fix a broken screen. If a button shows a “Not Installed!” style message, it means the plugin behind its content type isn’t active — and renaming won’t fix that. Re-activate the plugin, or switch the button to a different content type instead.

Related

• Building Your App: Add a new screen (button) to your app — placing a button, choosing its content type, and pointing it at content.
• Building Your App: Configure your app’s home screen — arranging the grid and tab bar.
• Building Your App: Set up the bottom tab bar — promoting screens into the tab bar.
• App Settings Reference — the per-screen settings (layouts, content sections) available for listing-style screens.

What’s next

Once your screen list looks right, the usual next moves are to set each screen’s layout and colors in its Layout Settings, confirm the Content for Role layouts match up across roles (grab Clone from Role if you want to copy one role’s layout as a starting point), then preview and publish.