How to manage the dev and live environments with Batch?

Here are the best practices to manage both environments.

How to manage the dev and live environments with Batch?

A staging environment refers to a parallel server environment for testing websites and software applications in conditions as close as possible to the live environment, without compromising the organization's current data or interrupting its operations.

You should always integrate Batch in a development environment and then go into production mode after everything has been tested and validated.

For this matter, we strongly recommend:

1

Creating two applications per OS (Android, iOS, Web) on the dashboard: one for tests and one for production (e.g. MyApp and [DEV] MyApp).

2

These apps will then be grouped into two Omnichannel projects.

For instance:

Thereafter, DEV projects can only be displayed to developers so as not to disturb your operational teams on the dashboard (refer to the Project-level Permissions documentation for more details).

Avoid using the Dev API key on production projects. The Dev API key (its value starts with DEV) is meant for development and testing only. Using it in production has several drawbacks:

• Your stats will be inaccurate. Batch does not compute analytics for the Dev API key, so any campaign or traffic sent with it is ignored in your KPIs (delivery, open and click rates, etc.).
• Deliverability can suffer. Dev traffic is not treated as production traffic and can be rate-limited by push providers such as FCM or APNs, which may throttle or drop your notifications.
• It pollutes your production data. Mixing Dev installs and tokens into a production app makes your audiences and targeting unreliable.

Always ship your production app with the Live API key, and reserve the Dev API key for a dedicated development app or project.