Custom App Hosting

Decide whether Reach or your team hosts and releases the web and mobile front ends.

Overview

Custom App Hosting defines who owns and operates the customer-facing web and mobile front ends.

Reach still owns and operates the backend services and core platform.

Default: unless explicitly agreed otherwise, brands launch under a Reach-hosted model.

Hosting models

• Reach-hosted (default): Reach deploys and operates the front end. Releases follow the shared platform release process.

• Brand-hosted (by exception): Your team deploys and operates the front end. Your team owns uptime, monitoring, and releases.

When teams choose this

• You want the fastest path to launch with managed releases.

• You have an existing app/web platform and want to own the UI layer.

• You need a different release cadence than the shared platform cadence.

What Reach delivers (scope)

• What is included:

  • Defining a hosting and release ownership model for web and mobile front ends.

  • Documented responsibilities and operational handoffs between your team and Reach.

• What is excluded:

  • Backend ownership changes.

  • Net-new custom front-end builds (scoped separately).

Mobile app (Reach-hosted): brand-specific app instance + store submission

Reach can create and publish a brand-specific instance of the standard mobile app.

This keeps the same core app functionality and stability. It enables brand-specific configuration and visual customization only.

1

Create the brand app instance

Reach creates a dedicated app instance from the shared application framework.

2

Apply in-app branding

Reach updates the app’s branding elements (logo, colors, banners, and supported visual components).

The brand provides final assets and any brand guidelines.

3

Decide app store ownership

Confirm whether the listing is published under:

• Reach’s developer account, or

• the brand’s developer account.

4

Prepare store listing assets

Finalize app icon, screenshots, feature graphics, and store descriptions.

This can be a shared effort between brand and Reach (design + content).

5

Confirm marketing + comms readiness

Prepare go-live communications, including placeholders for app store links (email and/or API-driven comms).

6

Submit to app stores

Reach submits the app for review once branding and assets are approved.

Typical store review: 4–7 business days (platform dependent).

If you need functional changes in the mobile app (not just branding/config), scope that separately. This bolt-on covers hosting + release ownership, not net-new app features.

Brand inputs

• Preferred ownership model (Reach-hosted vs brand-hosted) and the reason.

• Which surfaces are in scope (web, iOS, Android).

• Target launch date and desired release cadence.

• Your team’s operational readiness (support, monitoring, incident response, on-call contacts) if brand-hosted.

• Any constraints on domains, app store ownership, or release approvals.

• An approval owner for the operating model.

Requesting this bolt-on

For the standard request process, commercial notes, and support, see Bolt-ons catalog.

Technical details

For the implementation-specific setup details, visit: App set-up technical details

Questions or clarification? Reach out to your respective account manager or email at [email protected]