Getting Started with MemberPress AppKit

MemberPress AppKit allows Mitgliedschaftsseite owners to create native iOS and Android mobile apps. These apps show membership content and let members view protected items from their phones and tablets.

This document provides an overview of the complete MemberPress AppKit setup process. It outlines each phase and explains the requirements. Users will learn the steps needed to publish working mobile apps for both platforms.

What MemberPress AppKit Does

MemberPress AppKit turns a MemberPress-powered website into a mobile app. The app links to the existing website and shows content to members based on their membership. It shows protected posts, pages, and Kurse while using existing MemberPress access rules.

The app pulls content directly from the website. Any content updates on the website show in the app right away.

Choosing a Registration Path

MemberPress AppKit supports two approaches for member registration. This decision must be made before starting the setup process.

Path A: Website Registration Only

Members register and purchase memberships only through the website. The app functions as a content access tool for existing members. This path offers simpler setup with no platform fees on membership sales. Phase 4 (In-App Purchases) can be skipped entirely.

Path B: In-App Purchases Enabled

Members can register and buy memberships right in the app using Apple Pay or Google Pay. This path needs more setup in both app stores. Apple and Google charge a fee on in-app purchases. Requiring in-app purchases during registration makes sure new members pick a membership plan.

Das ist wichtig: Choosing Path B requires completing Phase 4 of this guide. The in-app purchase configuration must be finished before building the app.

Tipp: For users who prefer professional assistance, MemberPress offers a Done for You setup service for an additional fee.

Process Overview

The complete MemberPress AppKit setup has seven phases. Each phase must be done in order to avoid problems and setup errors.

Phase	Beschreibung	Path A	Path B
Phase 1	Platform Account Setup	Erforderlich	Erforderlich
Phase 2	AppKit Installation and Configuration	Erforderlich	Erforderlich
Phase 3	Content and Access Rules Preparation	Erforderlich	Erforderlich
Phase 4	In-App Purchases Configuration	Überspringen	Erforderlich
Phase 5	App Testing	Erforderlich	Erforderlich
Phase 6	App Building and Publishing	Erforderlich	Erforderlich
Phase 7	Ongoing App Management	Erforderlich	Erforderlich

Phase 1: Platform Account Setup

This phase sets up the required developer accounts for publishing apps. Both platforms need paid developer accounts with identity checks.

Das ist wichtig: Start this phase first. Account approval can take several days. Other phases can move forward while waiting for approval.

Apple Developer Account Setup

Publishing an iOS app needs joining the Apple-Entwicklerprogramm ($99/year). This gives access to App Store Connect for app uploads. The Apple Developer account setup guide covers the steps in detail.

To join the Apple Developer Program:

1. Navigieren Sie zum Apple-Entwicklerprogramm enrollment page.

2. Klicken Sie auf Anmelden unter and sign in with an Apple ID.
3. Select the account type (Individual or Organization).

4. Complete the identity check and pay the $99 annual fee.
5. After approval, access App Store Connect.
6. Register a Bundle ID in the Apple Developer account (format: reverse domain notation, e.g., com.companyname.appname).
7. Create an app listing in App Store Connect, selecting the Bundle ID and adding an Artikelnummer for internal tracking.
8. Make the needed certificates and profiles.
9. Connect the Apple Developer account to AppKit.

Google Play Developer Account Setup

Publishing an Android app needs a Google Play Developer account ($25 one-time fee). This gives access to the Google Play Console for app uploads. The Google Play Developer account setup guide covers the steps in detail.

To create a Google Play Developer account:

1. Navigieren Sie zum Google Play-Konsole signup page.

2. Sign in with a Google account and accept the terms.
3. Pay the $25 registration fee and complete the identity check.
4. After the check is done, create an app listing placeholder.

5. Create an upload key for app signing.
6. Connect the Google Developer account to AppKit.

Phase 2: AppKit Installation and Configuration

This phase installs the MemberPress AppKit add-on and sets up basic app settings. This includes branding, colors, Typografie, and login options.

Before starting, ensure an active MemberPress license (Launch, Growth, or Scale plan). The Lizenzschlüssel must be activated. An SSL-Zertifikat is required, REST API must be enabled, and compatible hosting is needed.

AppKit Installation

MemberPress AppKit is a separate add-on that requires its own yearly subscription. The AppKit connection guide shows how to install and activate it.

1. Navigieren Sie zum MemberPress AppKit page and purchase the AppKit subscription.
2. Download the AppKit plugin from Account > Downloads auf der MemberPress-Website.
3. Install the plugin über Dashboard > Plugins > Add New Plugin > Upload Plugin.
4. Get the AppKit license key from Account > Downloads auf der MemberPress-Website.
5. Navigieren Sie zu Dashboard > MP AppKit > Connect and enter the license key.
6. Check that the green “Active” status shows to confirm the link works.

App-Einstellungen

Die Einstellungen page has nine sub-options for setting up app behavior.

1. Navigieren Sie zu Dashboard > MP AppKit > Settings.

2. Set up options as needed:
   • Allgemein – signup, privacy, and login;
   • Rückmeldung – user feedback and app rating features;
   • Smart Banner – website banner promoting the app;
   • Blog-Beiträge – bookmarking, sharing, and related posts;
   • Push-Benachrichtigungen – notification types and automation;
   • Zugangskontrollen – restricted content messaging;
   • Compatibility – external link handling;
   • API-Caching – speed boost;
   • API CDN – content delivery network.
3. Klicken Sie auf Änderungen speichern after setting up each option.

AppKit Components

MemberPress AppKit has several parts that can be turned on or off based on your needs. The App-Seiten part is required and cannot be turned off.

1. Navigieren Sie zu Dashboard > MP AppKit > Komponenten.

2. Review the available components:
   • Push-Benachrichtigungen – lets you send push messages to app users;
   • In-App-Käufe – lets users buy memberships in the app;
   • Zugangskontrollen – controls who can see content based on membership;
   • API-Leistung – turns on caching for faster loading.
3. All components are enabled by default except In-App-Käufe.
4. Enable or disable components as needed and click Änderungen speichern.

Das ist wichtig: Path B users must enable the In-App-Käufe component before moving to Phase 4.

Platform Connection

The platform connection settings link AppKit to the app store listings. Each platform requires specific identifiers and certificates to build and publish apps.

1. Navigieren Sie zu Dashboard > MP AppKit > Configureund klicken Sie auf die Schaltfläche iOS Settings Menü.

2. Follow the iOS Settings configuration guide to set up Bundle IDs, Signing Certificates, Provisioning Profiles, and App Information.
3. Aktivieren Sie Universelle Links for deep linking.
4. Klicken Sie auf Änderungen speichern.
5. Next, connect the app you created in your Google Play Console. Click the Android Settings Menü.

6. Follow the Android Settings configuration guide to set up Application ID and KeyStore Information.
7. Aktivieren Sie Android App Links for deep linking.
8. Klicken Sie auf Änderungen speichern.
9. Klicken Sie auf die Google Firebase sub-menu and follow the Google Firebase setup guide to enable push notifications.

Anmerkung: Google Firebase requires uploading configuration files for both iOS (.plist) and Android (.json) apps. Separate files are needed for Release and Test app builds.

Phase 3: Content and Navigation Setup

This phase sets up app content and navigation menus. Posts and MemberPress Courses sync from the website on their own. App Pages show custom content only in the app. The app homepage setup sets the first screen users see. Text translations let you translate app text into other languages.

Before starting, ensure at least one Mitgliedschaft exists and MemberPress-Regeln are set up.

App-Seiten

App Pages are custom screens shown only in the mobile app. These pages are built using the Gutenberg-Editor with a width made for mobile screens.

1. Navigieren Sie zu Dashboard > MP AppKit > App Pages.

2. Klicken Sie auf Neue App-Seite hinzufügen to create a new page.
3. Add content using Gutenberg blocks, including MemberPress AppKit blocks und die Courses block.
4. Klicken Sie auf veröffentlichen. um die Seite zu speichern.

Anmerkung: Posts and MemberPress Courses from the website sync to the app on their own. Content updates do not need a new app version. Blog pages show website posts in the app. Deep linking lets users go directly to specific app content from outside the app.

Menü Konfiguration

The Menus settings control app navigation. Three menu areas are available: Registerkarte Bar (bottom navigation), Kopfleiste (top navigation), and More Menu (extra items). Custom menu icons und multiple menu versions offer more ways to set up navigation.

1. Navigieren Sie zu Dashboard > MP AppKit > Menüs.

2. Richten Sie die Registerkarte Bar with main navigation items (up to 4 tabs plus More).
3. Richten Sie die Kopfleiste with top navigation buttons.
4. Richten Sie die Mehr Menü with extra navigation items.

5. Klicken Sie auf Menü speichern after setting up each menu.

Zugangskontrollen

The app uses access rules from MemberPress. The Access Controls page lets you add rules for specific content. Access groups help organize content access by membership level. The default restricted message shows when users try to view protected content.

1. Navigieren Sie zu Dashboard > MemberPress > Regeln and review existing rules.
2. Create additional rules falls erforderlich.
3. Navigieren Sie zu Dashboard > MP AppKit > Access Controls.

4. Auf der Allgemein tab, find the Zugang einschränken Abschnitt.
5. Aktivieren Sie “Restrict who can login to the MemberPress App” to limit app access to specific access groups.
6. To make the app fully private, enable the Private App setting unter Dashboard > MP AppKit > Settings > General > Privacy.
7. Klicken Sie auf die App-Seiten, Seiten, oder Beiträge tab to add rules to specific content.

8. On these pages, you can add item-specific rules. Click Regel hinzufügen next to any item to restrict that content to logged-in members or specific access groups.
9. Klicken Sie auf Änderungen speichern.

Phase 4: In-App Purchases Configuration

This phase is required only for Path B users. Path A users should skip to Phase 5. The In-App Purchases setup guide shows all the setup steps.

Before starting this phase, ensure the In-App-Käufe component is enabled at Dashboard > MP AppKit > Komponenten.

Both app stores require in-app purchase products to be created before the app can sell memberships. Each MemberPress membership needs a matching product in both stores. Subscription groups organize related membership products for upgrade and downgrade options.

App Store Product Setup

1. Unter App Store Connect, select the app and click Abonnements in der Seitenleiste.
2. Create products matching each membership. Select Automatisch verlängerbares Abonnement for recurring memberships. The iOS In-App Products guide explains product setup and types.

Anmerkung: iOS products must reach “Ready to Submit” status before they appear in AppKit sync options.

3. Unter Google Play-Konsolenavigieren Sie zu Monetize with Play.

Anmerkung: A Google Payments merchant account is needed before seeing subscription settings. Click Los geht's über die “To monetize this app, set up a merchant account” banner to finish merchant account setup.

4. After merchant account setup, navigate to Monetarisieren > Produkte > Abonnements.
5. Create matching products using the same Product IDs for easier tracking. The Android In-App Purchases guide shows the setup steps.

Connecting Products to MemberPress

After creating products in both app stores, link them to MemberPress memberships:

1. Navigieren Sie zu Dashboard > MP AppKit > In-App-Käufe > Produkte.
2. Klicken Sie auf Neu hinzufügen ein Produkt zu entwickeln.
3. Eingabe einer Produktname, optional Tagline, Beschreibungund Vorteile.
4. Siehe Anzeige auf dem Produktbildschirm und wählen Sie Bezahlt als Produkttyp.
5. Unter iOS Store, prüfen Aktivieren Sie und klicken Sie Mit Apple synchronisieren um verfügbare Produkte abzurufen.
6. Select the matching App Store Connect product from the list.
7. Unter Android-Store, prüfen Aktivieren Sie und klicken Sie Mit Google synchronisieren um verfügbare Produkte abzurufen.
8. Select the matching Google Play product from the list.
9. Unter Integrationstypauswählen Mitgliedschaft and choose the membership plan to link.
10. Klicken Sie auf veröffentlichen. to save the product.
11. Repeat for each membership that needs in-app purchase access.

Anmerkung: Die In-App Purchases setup guide provides full details on product configuration and testing.

Phase 5: App Testing

This phase tests how the app works before sending it in. Both Apple and Google reject apps with clear bugs or broken features.

Device Testing

Test App builds allow testing the app on real devices before submission. Test with many user accounts to check that access rules work right.

1. Navigieren Sie zu Dashboard > MP AppKit > Erstellen und klicken Sie Erstellen anfordern.
2. Select the platform (iOS oder Android), then select Test-App als Build-Typ.
3. After the build completes, it appears in the Entstehungsgeschichte list.

For iOS Test Apps, first register test devices unter Dashboard > MP AppKit > Configure > iOS Devices. Then click the Auf iOS-Gerät installieren button to install via QR code or download the IPA file. The iOS test builds guide shows the full steps.

For Android Test Apps, click the Auf Android-Gerät installieren button to install via QR code or download the APK file. The Android test builds guide shows the full steps. Android Test Apps do not need device registration.

Anmerkung: Test Apps install directly via QR code for quick testing. Release Apps are needed for TestFlight (iOS) or Google Play testing tracks (Android).

Path B users must also test in-app purchases using iOS sandbox accounts and Android license testers. Before App Store submission, select an iOS review version for Apple's review team.

Phase 6: App Building and Publishing

This phase creates final app builds and sends them to the app stores. Both platforms review apps before they go live. The app build generation guide covers building apps for both platforms.

Prepare app store listing assets (screenshots, descriptions) and ensure the privacy policy URL is reachable. The MemberPress App Publishing Service offers help with the submission process.

iOS App Submission

1. Navigieren Sie zu Dashboard > MP AppKit > Erstellen und klicken Sie Erstellen anfordern.
2. Wählen Sie iOS as the platform, then App veröffentlichen as the build type. The iOS release app generation guide shows the steps.
3. After the build completes, click the Submit for Publishing Taste auf der Baukarte.
4. Klicken Sie auf Upload to App Store Connect to upload directly from AppKit. The uploading iOS builds guide shows the steps.
5. Unter App Store Connect, complete App-Informationen, upload screenshots, select the build, and click Zur Überprüfung einreichen. Die App Store publishing checklist lists all needed items.

Android App Submission

1. Navigieren Sie zu Dashboard > MP AppKit > Erstellen und klicken Sie Erstellen anfordern.
2. Wählen Sie Android as the platform, then App veröffentlichen as the build type. The Android release app generation guide shows the steps.
3. After the build completes, click the Submit for Publishing Taste auf der Baukarte.
4. Klicken Sie auf In die Google Play Console hochladen to upload directly, or click AAB-Datei herunterladen for manual upload.
5. Unter Google Play-Konsolenavigieren Sie zu Freigabe > Tests > Abgeschlossene Tests and upload the AAB file. For staged rollouts, use closed testing before production.
6. Vollständig Store Listing, upload screenshots, complete Bewertung des Inhaltsund klicken Sie auf Start Rollout. Die Google Play publishing checklist lists all needed items.

Phase 7: Ongoing App Management

Published apps need regular care. Plan updates for bug fixes and to work with new OS versions. The iOS app update und Android app update guides show the steps for new versions. Maintenance mode lets you briefly limit app access during big updates.

Check App Store Reviews and Google Play Reviews, and reply to user feedback quickly. Track crash reports and watch API performance to keep the app running well.

Zusammenfassung

MemberPress AppKit lets you build native mobile apps for membership sites through seven steps in order.

Before starting Phase 1:

1. Check website needs (HTTPS, PHP 7.4+, WordPress 5.8+).
2. Make sure an active MemberPress plan is in place (Launch, Growth, or Scale plan).
3. Decide between Path A (website registration) or Path B (in-app purchases).
4. Gather visual assets (app icon, splash screen, screenshots).
5. Prepare credit card information for developer account fees.

Start Phase 1 by creating an Apple Developer account and a Google Play Developer account.