Understanding Propagation of App Configurations. Making hot and fast changes to your app without redeployment.
Hot Reload/Configs
Raven implements hot configurations to bypass the need to redeploy apps for review and avoids delays when small changes need to be made. App theme changes are a hot config that also propagates on live apps, making critical theme changes near-instant.
Hot configurations happen without the user having to reload, reset, or update the app.
Which Hot Configurations can I make?
You can make hot configs (near-instant, no reload changes) for:
Flavours
Flavour Settings
Theme Colors
Icon Styles
Navigation Styles
What are Live Reload/Configs?
Live configurations are similar to hot configurations except that the change is only observed when the app reloads/resets. These configurations require the user to reload/reset the app as these settings must be initialised at the app's start.
Which Live Configurations can I make?
You can make live configs (changes requiring app reload) for:
Chat/Forums
Sign In Options
Blueprint Options
Subtitle/Payoff line
What are At-Build-Time Configs?
At-build-time configurations require a re-deployment as these settings are applied when the app is built. These are typically deployed assets and build settings.
Which Configurations are set At-Build-Time?
Configurations that are not instant and require app redeployment / rebuild, include:
Fonts
Icons
SSO settings
App Name
Although icons and app names are an At-Build-Time configuration, these changes will propagate on the backend/middleware as they are updated. It is recommended to redeploy an app to production shortly after making icon or app name changes.
App Hot Config FAQ
What is the difference between live and preview deployment?
Preview deployments are meant to be used to preview new features and bug fixes in new blueprint versions.
How can I preview changes in hot/live configurations?
These settings can't be previewed or isolated in preview deployments due to the benefit of providing flexibility without deployment. However, you can do either of the following:
Use a demo/alternative app to preview the changes.
Deploying to the web happens in minutes, so changes can be rapidly applied before deploying to production for native apps.
