Connect, Brand, and Launch Your Seedly CRM Mobile Apps

Gather the three addresses and a login

Everything downstream is a copy-paste of these. Get them right once.

Prove the front door from a terminal

Ten seconds, no build, and it finds the Origin mistake before an app can.

SITE_URL=https://<name>.convex.site \
ORIGIN=https://crm.yourcompany.com \
EMAIL=you@yourcompany.com PASSWORD='…' TOTP=123456 \
ios/Scripts/contract-check.sh

Choose how to connect

One phone, a whole team, or a build machine. Same three addresses, three places to put them.

Scripts/connect.sh \
  https://<name>.convex.cloud \
  https://<name>.convex.site \
  https://crm.yourcompany.com \
  5.8.4

# then prove sign-in through the app's own code path
EMAIL=you@yourcompany.com PASSWORD='…' TOTP=123456 Scripts/connect.sh --check

Sign in and walk the app

Rebuild, install, and put the app through a real morning before anyone else does.

• Inbox shows real conversations, and a new inbound message appears without refreshing.
• An SMS sent from a thread arrives on the test phone you expect.
• Contacts, Deals and Today show your data. The location switcher lists every location you belong to.
• More shows only the tools the CRM answers for. "Not available on this CRM" is the app being honest about the CRM version, not a fault.
• Placing a call from a contact works if your location's dialer works on the web. If the dialer is off there, the app hands the call to the phone's own dialer.

If your CRM runs Seedly Dispatch

Nothing to configure in the app. It asks the CRM one question on sign-in and shows the field screens when the add-on answers.

• Every technician is a CRM user and on the Dispatch roster. A login without a roster entry sees "not on the roster yet", not an empty day.
• Technicians have dispatch_jobs; dispatchers have dispatch_schedule.
• Android builds carry a Google Maps key (MAPS_API_KEY). iPhone needs nothing. Without a key the Android screens still work as lists with "Open in Google Maps".
• For push on visit assignments, the outbox in the next station is set up on both sides.
• A technician has walked one real stop: On my way, Arrived, a photo, Finished.

Push notifications, and calls that ring a closed phone

Optional. Everything else works without it. Budget an hour the first time.

The CRM's push is built for browsers. Phones need Apple's and Google's push services, so the pack adds two small pieces, both yours: a relay on your own Cloudflare account that receives the CRM's signed webhooks and forwards them to phones, and a Seedly add-on installed into your CRM through its extension registries that answers "who should be told" from each person's own notification settings and quiet hours. The add-on is also the only way an inbound call can ring inside the app while it is closed.

Write it down

Two minutes now saves an afternoon when Seedly ships an update.

• CRM version and today's date added to the compatibility matrix in docs/PRODUCT-READINESS.md and the pin at the top of CONTRACT.md.
• Every tool that reported "not available on this CRM" listed, so nobody files it as a bug later.
• git status shows neither Deployment.json.
• The relay URL, if any, stored where the next person will find it, not in one engineer's shell history.

Two decisions before you spend a day on anything

Neither is technical. Both can stop a release.

Accounts and a domain

Start these first. Apple's takes about a week.

Make it yours

One theme file, one identifier you can never change, one icon script.

Privacy and legal

The privacy manifest is written. The pages and questionnaires need your company's details.

• ios/App/Resources/PrivacyInfo.xcprivacy re-read against today's dependency list. It declares no tracking and no collected data. An SDK that phones home makes it wrong, and a wrong manifest is a rejected upload.
• docs/templates/privacy-policy.md filled in and published at a stable URL on your domain.
• docs/templates/terms.md published, or Apple's standard licence left in place.
• Both store questionnaires answered from docs/templates/app-privacy-answers.md. The two stores mean different things by "collect"; the page explains which is which.
• A support page with the app's name, an email address and ideally a phone number. Reviewers open it.

Screenshots and listings

Capture, frame, caption. Then the one field that gets apps rejected.

ios/Scripts/capture-all.sh                                # every screen, light and dark
ios/Scripts/frame-screenshots.sh docs/screenshots/<date>    # store sizes on your brand tint
android/scripts/capture.sh emulator-5554 docs/screenshots/android-<date>

iPhone: archive, upload, TestFlight

One script. It refuses to start until it has what it needs and says what is missing.

export TEAM_ID=ABCDE12345                   # Apple Developer → Membership
export ASC_KEY_ID=X1Y2Z3W4V5                # App Store Connect → Users and Access → Integrations
export ASC_ISSUER_ID=69a6de70-…
export ASC_KEY_PATH=~/keys/AuthKey_X1Y2Z3W4V5.p8

ios/Scripts/release.sh --dry-run            # what it would do
ios/Scripts/release.sh                      # archive, export, validate, upload

Android: sign, bundle, Internal testing

Make one upload key, back it up like a deed, and always test the release-signed build first.

keytool -genkeypair -v -keystore ~/keys/yourcompany-upload.jks \
  -alias upload -keyalg RSA -keysize 4096 -validity 10000

export KEYSTORE_PATH=~/keys/yourcompany-upload.jks
export KEYSTORE_PASSWORD='…'
export KEY_ALIAS=upload

android/scripts/release.sh --dry-run
android/scripts/release.sh                  # → app/build/outputs/bundle/release/app-release.aab

A remote, a green CI run, then submit

A workflow that has never been green is not a workflow.

gh repo create yourcompany/yourapp --private --source=. --remote=origin
git push -u origin main

The pack's .github/workflows/ci.yml builds both apps, runs the unit tests, and runs the wall check that proves no CRM code has entered the repo. Protect main so it has to pass before anything merges. Watch the first run.