Notes for App Review

Two of the most common rejections for a community app are “we were unable to sign in” and “we could not locate the features described”. Neither is a problem with the app. Both are a problem with what the reviewer was told.

Because you build your app by dragging features into navigation zones, Memberside already knows the exact taps that reach every screen. Generate from navigation on the Store submission page writes them out.

What it produces

Plain text, ready to paste — neither store’s notes field renders formatting:

ABOUT THIS APP

Northwind Community is the mobile app for https://northwind.example, a
membership community running on WordPress.

Members sign in with the account they already have on that site. Every
screen listed below is drawn natively — the app reads the community's
data over a REST API rather than displaying the website in a web view.

The app opens on "Feed".

SIGNING IN

Please use this account:

  Username: [email protected]
  Password: ••••••••

HOW TO REACH EVERY SCREEN

 1. Feed (News Feed)
    Tap "Feed" in the bottom tab bar.

 2. Community (Directory)
    Tap "Community" in the bottom tab bar.
    Visible only after signing in with the account above.

 3. Groups
    Tap "Menu" in the bottom tab bar to open the navigation drawer, then tap "Groups".
    Restricted to the "editor" role.

SCREENS OPENED BY TAPPING CONTENT

These have no tab of their own — they open from a list:

  - Single Post — tap an item in "News Feed".

What makes it accurate

Three things it gets right that a hand-written note usually does not.

It uses the name printed on the tab

If you renamed Groups to Communities in Appearance, the notes say Communities. A reviewer following directions that name a feature rather than a button gives up and rejects.

It knows which screens need signing in

Every screen you restricted to logged-in members is marked as needing the demo account, and every screen restricted to a role names the role. That is exactly what a reviewer needs, and exactly what is missing from the notes that get apps rejected as unusable.

It knows what is a screen and what is a button

A Menu opens a drawer, a Dark Mode switch flips the theme, a group header expands a list. None of them is a destination, so none is numbered among the screens — they are listed separately as controls. Numbering them sends a reviewer looking for a page that does not exist.

Screens with no tab of their own

A single post, a page, an activity thread — these open by tapping a row rather than from the navigation. They are described by what opens them, because there is no tap path to give.

It answers the questions review always asks

Below the screen list, the notes answer the three things App Review raises on almost every community app — before it has to ask:

MODERATION AND ACCOUNT CONTROL

In "Community Feed", members report a post or a comment from the ⋯ menu beside it.
Reports go to the moderators of the community's own site.

In "My Account", members delete their own account from the Delete tab. Deletion is
confirmed with the member's password and removes the account permanently.

[ Tell review what you sell: say that everything in the shop is shipped
  physically, or name any digital content and how it is bought. ]

Each sentence is written from what you actually placed, naming the screen the way you named it. An app with no reporting gets no sentence claiming it has any.

Square brackets are yours to fill in

Some things the app cannot know — whether your shop sells memberships or downloads is one. Those arrive as a bracketed prompt, and the checklist blocks on the notes while one is still there. Replace the text with your answer and remove the brackets.

Editing them

The generated notes are a starting point. Edit them freely — you know things about your community that the navigation does not, and anything the checklist raised about moderation, account deletion or what you sell is worth answering here before review asks.

Generating fills the box; Save keeps it. It is a drafting action like any other edit on the page, so you can generate, adjust a line, and save once. Until you save, nothing has changed.

If the box already holds something different, generating asks before replacing it — it will not quietly discard a rewrite.

When it does not work

Symptom	Cause	Fix
A screen is missing from the list	It is not placed in any navigation zone	Place it in the builder, then generate again
The notes name a feature you renamed	The rename was not saved	Save the tab’s Appearance settings, then generate again
A drawer’s screens are missing	Nothing in the app opens that drawer	The checklist flags this as blocking — add a Sidebar Trigger or enable the Upper Nav
It says a demo account is required and missing	Some screens are members-only and no account is filled in	Add one under Store details; it appears in the notes
Generating seems to do nothing	The box already held different text	It asks before replacing — confirm on the prompt
The new notes vanished	They were generated but never saved	Generating is a draft; press Save

Next

• Submitting your app