ShaunSocial docs ShaunSocial mobile app guide
Version 1.5.6
  • 1.5.6 (this version)

ShaunSocial mobile app guide 1.5.6 / Your app

Build and brand your app

AdminDeveloper

This page takes the ShaunSocial app source you received and turns it into your own app in the stores: what to install, how to point the app at your site, your app's name, identifiers, icons and splash screen, signing, version numbers and the release files you upload. The site owner decides the names and owns the store accounts (Admin); the person who builds the app does the rest (Developer).

What you build, and who does what#

AdminDeveloper

Last updated: 2026-11-19 · v1.5.6

The ShaunSocial app is one Flutter project that builds both the Android and the iOS app. Your source package holds three folders: shaun_app (the app itself, where you work), shaun_lib (a shared library) and packages (libraries the app needs). App 1.5.6 is made for sites running ShaunSocial 1.5.6.

StepWho
Choose the app name, the package name and bundle ID, the icon and splash pictureAdmin
Open a Google Play developer account and an Apple Developer Program membership, and add the developer to bothAdmin
Install the tools, enter your site's address and key, rename and rebrand the appDeveloper
Set up Firebase, which the app needs to start (see Push notifications)Admin creates the project, Developer adds the files
Create the signing keys, build the release files and upload themDeveloper
Fill in the store listings and submit for reviewAdmin, with the Developer

The source package comes without a signing key and with empty Firebase files: you create your own of both. Never publish someone else's signing key or Firebase files with your app.

Read from the code; builds and store steps not run

This page was written from the code of the ShaunSocial app 1.5.6. The build commands, Xcode, Android Studio and the store consoles were not run for this guide, and those tools rename their menus from time to time: look for the same words if a menu is named a little differently.

What you need on your computer#

Developer

Last updated: 2026-11-19 · v1.5.6

ForWhat
Both appsFlutter 3.47.5 or later (the project refuses older versions when you fetch its libraries)
AndroidAndroid Studio with the Android SDK platform 36, Java 17, and the NDK version 28.2.13676358 (install it with the SDK Manager if the build asks for it). The app runs on Android 7.0 and later
iOSa Mac with Xcode and CocoaPods. The app runs on iOS 15.0 and later

Then fetch the app's libraries once, in the shaun_app folder:

cd shaun_app
flutter pub get

What you should see: the command ends without errors. "The current Flutter SDK version is …" means your Flutter is older than the project needs: update it with flutter upgrade.

Keep shaun_app, shaun_lib and packages side by side in the same folder: the app finds the other two by their place next to it.

Point the app at your site#

AdminDeveloper

Last updated: 2026-11-19 · v1.5.6

The values you change to make the app yours are collected in one file, shaun_app/lib/app/configs/application.dart:

ValueWhat to enter
kBaseUrlyour site's address as members open it in a browser, including the folder if the site is installed in one, for example https://example.com or https://example.com/community. Use https://
kApiCapchathe app's key. It must be the same as API Secret Key in AdminCP → Site Settings → General Configuration → General Settings; otherwise sign-up and other protected requests from the app are refused once reCAPTCHA is on (see If you also run the ShaunSocial mobile apps). Pick one random value and put it in both places
kDefaultLanguagethe language the app uses until a member picks one, for example en
appFolderGallerythe album name for photos and videos members save from the app
appSchemeDeeplinka short, unique word for links that open your app, for example examplecommunity. Enter the same word as app_scheme in shaun_app/android/app/src/main/res/values/string.xml and as the first CFBundleURLSchemes entry in shaun_app/ios/Runner/Info.plist

The same file also holds the ad unit IDs (see Ads and links to your site) and the order of the tabs in the app's bottom bar.

Decide the address before you publish

When a later version of the app has a different kBaseUrl host, every member is signed out once after updating.

App name, package name and bundle ID#

AdminDeveloper

Last updated: 2026-11-19 · v1.5.6

Every app in the stores has a fixed technical name: the package name on Android and the bundle ID on iOS, usually written like a reversed web address, for example com.example.community. The Admin chooses it once; it can never be changed after the app is published, and it cannot be one already used by another app. Both may be the same.

Android#

  • Package name: applicationId in shaun_app/android/app/build.gradle. Leave the namespace line above it as it is: it names the app's code, not the app.
  • App name under the icon: app_name in shaun_app/android/app/src/main/res/values/string.xml.

iOS#

The iOS app has a second part, the share extension, that lets members share photos and links from other apps into yours. Both parts and their shared storage (an "app group") carry the bundle ID, so change it in all these places:

  1. Open the iOS project in Xcode: in the shaun_app folder run xed ios (see Sign the iOS app). Select the Runner target → General and set Bundle Identifier to your bundle ID and Display Name to your app's name.
  2. Select the Share Extension target and set its Bundle Identifier to your bundle ID followed by .ext, for example com.example.community.ext.
  3. Set the app group to group. followed by your bundle ID, for example group.com.example.community, in Runner/Runner.entitlements, Share Extension/Share Extension.entitlements and as AppGroupId in Runner/Info.plist.
  4. In Runner/Info.plist, change the second URL scheme from SharingMedia- plus the old bundle ID to SharingMedia- plus yours.
  5. In Share Extension/ShareViewController.swift, set hostAppBundleIdentifier to your bundle ID.

Then the Admin enters both values in AdminCP → Mobile Application → General Configuration → General Settings (see Package name and bundle ID): your site needs them for in-app purchases and incoming calls.

Icon and splash screen#

Developer

Last updated: 2026-11-19 · v1.5.6

Replace the pictures in place, keeping the file names and sizes:

WhatAndroid (in shaun_app/android/app/src/main/res/)iOS (in shaun_app/ios/Runner/Assets.xcassets/)
App iconic_launcher.png in each of the five mipmap-… foldersAppIcon.appiconset (open it in Xcode and drop your icon onto each size)
Splash pictureic_splash.png in the mipmap-… foldersLaunchImage.imageset
Splash background colourlauncher_background_color in values/colors.xmlprimary.colorset

Android Studio (New → Image Asset) and Xcode can make every icon size from one large picture. The small icon shown with notifications on Android is separate: see The notification icon on Android.

Sign the Android app#

Developer

Last updated: 2026-11-19 · v1.5.6

Google Play accepts only signed apps. You sign with a keystore: a file holding your private key, protected by passwords you choose. You create it once and use it for every update.

  1. Create the keystore with Java's keytool (the name, alias and validity are examples; it asks for the passwords and your details):
    keytool -genkey -v -keystore my-release-key.keystore -alias my-key -keyalg RSA -keysize 2048 -validity 10000
  2. Open shaun_app/android/app/build.gradle. In signingConfigs → release, set storeFile to where your keystore is, and keyAlias, keyPassword and storePassword to yours. As shipped, storeFile points at a keystore in the folder that holds shaun_app.
  3. Build once (see Build the Android release file) to check the key is found.

The project signs test builds (flutter run) with the same key, so they need the keystore too.

Keep the keystore and its passwords safe

Back them up outside your computer and never send them to anyone you would not trust with your app. Do not put the keystore or its passwords in a public code repository. With Play App Signing, which Play Console offers when you upload your first release, your keystore is only an upload key and Google can reset it if you lose it; without it, a lost keystore means you can never update the app again.

Sign the iOS app#

AdminDeveloper

Last updated: 2026-11-19 · v1.5.6

Apple signs apps with a certificate and a provisioning profile that belong to an Apple Developer Program membership. The Admin owns the membership and adds the Developer to the team (App Store Connect → Users and Access); Xcode then creates the certificates and profiles by itself.

  1. In the shaun_app folder run xed ios. It opens the Runner project in Xcode together with its CocoaPods libraries; opening Runner.xcodeproj on its own leaves those out and the build fails (if Xcode reports missing pods, run pod install in shaun_app/ios first). Sign in under Xcode → Settings → Accounts.
  2. For the Runner target and again for the Share Extension target: Signing & Capabilities → tick Automatically manage signing and choose your team.

    What you should see: no red errors under Signing. Xcode registers both bundle IDs with Apple, with the capabilities the project uses: Push Notifications, Sign in with Apple, App Groups and Background Modes.

  3. The Admin creates the app in App Store Connect (Apps → + → New App) with the same bundle ID.

If Xcode reports that the app group is not available, register group. plus your bundle ID under Certificates, Identifiers & Profiles → Identifiers → App Groups on the Apple Developer website, and try again.

Version numbers#

Developer

Last updated: 2026-11-19 · v1.5.6

Each store upload needs a higher build number than the one before. In this project the two apps take their numbers from different places:

Version members seeBuild number (raise it for every upload)
AndroidversionName in shaun_app/android/app/build.gradleversionCode in the same file
iOSVersion of the Runner target in Xcode (General)the --build-number you give flutter build ipa (see Build the iOS release file)

Because the Android numbers are written in build.gradle, the version line of pubspec.yaml and the build flags do not change them.

Build the Android release file#

Developer

Last updated: 2026-11-19 · v1.5.6

Google Play takes an Android App Bundle (.aab). In the shaun_app folder:

flutter build appbundle --release

What you should see: the file build/app/outputs/bundle/release/app-release.aab. Upload it in Play Console (see Publish in the stores).

To install the app on a phone without Google Play, for example to show it around, build an APK instead with flutter build apk --release (file build/app/outputs/flutter-apk/app-release.apk). In-app purchases do not work in such a copy (see Prepare an Android test phone).

If the build stops with a message that it cannot tree-shake icon fonts, add --no-tree-shake-icons to the command.

Build the iOS release file#

Developer

Last updated: 2026-11-19 · v1.5.6

On the Mac, in the shaun_app folder (use a build number higher than your last upload):

flutter build ipa --release --build-number 2

What you should see: an .ipa file in build/ios/ipa/, and an archive in build/ios/archive/.

Upload it with Apple's Transporter app, or open the archive in Xcode (Window → Organizer) and click Distribute App → App Store Connect. After Apple has processed it, the build appears under TestFlight in App Store Connect, where you and your testers can install it.

If the build complains about CocoaPods, run pod install --repo-update in shaun_app/ios and build again.

Publish in the stores#

AdminDeveloper

Last updated: 2026-11-19 · v1.5.6

Google Play#

  1. The Admin creates the app in Play Console (Create app) and fills in the store listing, the content rating, the data safety form and the other items Play Console lists under Set up your app.
  2. The Developer uploads the .aab to internal testing first (see Android: upload a build to internal testing), tests it, then promotes it to production.

App Store#

  1. The Admin fills in the app's page in App Store Connect: screenshots, description, privacy details and a demo member account for the reviewers.
  2. The Developer uploads the build and tests it with TestFlight.
  3. The version is submitted for review. If your app sells eWallet credits, follow iOS: submit the first version with in-app purchases.

Before the first review, also set up push notifications (see Push notifications) and, if you sell credits in the app, the in-app purchases (see In-app purchases).

Change log#

Last updated: 2026-11-19 · v1.5.6

Date (GMT+7)SectionWhat changed
2026-11-19allFirst version for the ShaunSocial app 1.5.6, written from the 1.5.6 code. The builds and the store steps were not run for this guide.
2026-11-19build-android, store-uploadLinks updated after the In-app purchases page was split by platform: Android and iOS have their own pages.