Testing & Release Cycle

Our development process follows a Continuous Delivery approach. We provide daily updates via “Nightly Builds” and ship stable releases to the App Stores on a monthly schedule.

1. Nightly Builds (Daily)

Every night, our system automatically builds a new version of the app if there have been code changes (merged features or bug fixes). This version contains the very latest state of development.

• Purpose: To preview new features immediately and verify bug fixes.
• Important: Everything in the Nightly Build is slated for the next monthly release. We recommend checking the Nightly regularly to ensure upcoming changes meet your expectations.

How to access Nightly Builds

We use Firebase App Distribution to deliver these test versions.

1. Invitation: Once your project is set up, we will provide a permanent Invite Link for your brand. Share this link with anyone on your team who needs test access.

2. Installation (iOS):

   • Open the link on your iPhone.
   • Follow the instructions to install the “Firebase App Tester” profile.
   • Crucial Step: You must trust the enterprise certificate in your iOS settings (Settings > General > VPN & Device Management).

3. Installation (Android):

   • Open the link on your Android device.
   • You may see a system warning that the app is “not from the Play Store”. Please accept/allow the installation from this source.

4. Google Account & Alerts:

   • When opening the App Tester for the first time, you must sign in with a Google Account.
   • Enable Updates: Accept the prompt to enable “New Build Alerts”. This ensures you get a notification when a new Nightly is ready.
   • Tip: After signing in, wait for the browser screen to close itself automatically. Closing it manually too early often fails the login process.

2. The Developer Test Menu

Exclusive to Nightly Builds, there is a hidden menu that allows you to configure the app for testing purposes.

How to access it

Long press on the brand logo in the top navigation bar (on the Storefront / Home screen) to open the menu.

Key Features

• Environment Switch: Toggle between Staging (test data) and Production (live data) backends.
  • Note: Switching environments usually requires an app restart. Hard close the app and open it again.
• CMS Revisions: Enter a specific Drupal Revision ID to preview draft content (as described in the CMS Guide).
• Session Info: See and copy your Session ID, Channel ID, etc., for test sessions on other tools.

Not in Live Apps

This menu is strictly removed from the Release Candidates and the Live App versions in the App Stores. You cannot access debug settings in the final version.

3. The Monthly Release Cycle

We operate on a reliable monthly rhythm. This ensures your app stays compatible with the latest iOS/Android versions and receives regular feature updates.

The Schedule

• Scope Cut-Off: Approx. 1 week before the handover. No new features are merged after this point; only bug fixes.
• Handover Date: Typically a Monday in the middle of the month. This is when we finalize the “Release Candidate”.
• Review Phase: In the week leading up to the handover, we may provide early Release Candidates for final verification.
• Upload: After the Handover Date, we upload the technical build to Apple App Store Connect and Google Play Console.

Hotfixes

Critical bugs (e.g., crashes, payment blockers) can be addressed via Hotfixes outside of this monthly cycle. These are deployed immediately upon resolution.

4. Where to find which version?

Depending on the stage of development, builds are distributed via different channels:

Version Type	iOS Platform	Android Platform	Audience
Nightly Build	Firebase App Distribution	Firebase App Distribution	QA, Developers, Brand Managers
Release Candidate	TestFlight	Google Play Console (Internal Test)	Final Approvers
Live App	App Store	Google Play Store	End Customers

5. Store Responsibility & Publishing

It is crucial to understand the division of responsibilities for the final release.

Our Responsibility (Technical Delivery)

We act as the technical provider.

• We ensure the app code is stable and performant.
• We upload the final binary files (IPAs/AABs) to your App Store Connect and Google Play Console accounts.
• We handle technical metadata (version numbers, build strings).

Your Responsibility (Store Presence, Compliance & Release)

As the brand owner (or your assigned agency), you are responsible for the App Store Appearance, Account Maintenance, Compliance, and the final “Go Live”.

• Store Metadata: Screenshots, App Descriptions, Keywords, and Promotional Text.
• Release Notes: Writing the “What’s New” text for the update.
• Submission: Clicking the “Submit for Review” button in Apple/Google portals.
• Publishing: Once Apple/Google approves the app, you decide when to release it to customers.

App Store Compliance

Both Apple and Google have strict design and content guidelines for store assets. It is your responsibility to provide compliant assets. Non-compliant assets, especially screenshots, are a leading cause for review rejections and can significantly delay your release.

Plan for Rejections!

App Store reviews can be subjective. It is common for screenshots or descriptions to be rejected on the first submission. Please plan for potential delays and have resources available to quickly adapt your assets if needed.

Key Guidelines & Official Links

Here are the official, always up-to-date resources. We strongly recommend your marketing or design team reviews them before creating any assets.

• Apple App Store Review Guidelines (The “Bible”):
  • App Store Review Guidelines (Full Text)
• Apple Specifics for Screenshots & Previews:
  • Screenshot Specifications
• Google Play Store Policies (The “Bible”):
  • Google Play Developer Policy Center
• Google Specifics for Store Assets:
  • Graphic Assets, Screenshots & Video

Account & License Management

Critical: Your Responsibility

You are solely responsible for maintaining your Apple Developer and Google Play accounts. We do not monitor your accounts for administrative tasks. Failure to manage your accounts can block new releases or even take your live app offline.

Pay close attention to emails and notifications from Apple and Google regarding:

• Pending Agreements: Apple and Google periodically update their terms and conditions. These must be accepted in App Store Connect / Play Console, otherwise all build uploads will be blocked.
• License Renewal: Your Apple Developer Program membership must be renewed annually. We strongly recommend activating auto-renewal. If your license expires, your app will be removed from the App Store.