...
Walk their IT staff through setting up an app store accounts
What is a “Branding” at code level?
TBD, but assume some defined set of files, to include
logo
app name
any replacement text
defined set of languages supported.
Ideally we would have a repository of brandings, under version control.
Plus a pipeline that takes a new Safe Paths build, and for each branding under version control, creates branded versions of the App (APK / IPA files), ready for use in testing.
TBD whether this repository & pipeline belongs as part of the Safe Paths repo, or is external to that maintained & PM’d bey a different team. Probably makes sense for repo structure to match org structure - which I thinks points to this being external to the App.
However there are likely synergies, but also possibly tensions, with how we manage translations for text in the App, particularly when a partner wants to modify substantial parts of the text in the App and do so in multiple languages - this may point to tighter coupling with the main App codebase.
Testing
There are 2 key concerns for Test
Are the branding process & pipelines fit for purpose? Is it well-documented, usable etc.?
Actually testing the branded versions of the apps, ahead of use by a customer.
It is likely that as we get comfortable with the process, we will get a sense of where the key risks lie in Branding, and be able to tailorr the testing under 2 to just focus on these risk areas, rather than having to retest the whole app. In the short term, while we are still developing this understanding, we should expect to perform a pretty comprehensive test of the first few branded apps.
Operationalizing the Pipeline
...