There are a number of pieces of the UI that can be customised in the SDK. This should be done in conjunction with CSS customisation and Android customisation. To give the best user experience, you should make your CSS and SDK customisations consistently.
To customise the native iOS user interface, you will need to change various files inside the GIDresources.bundle
, inside the IDMetrics
frameworks, and sometimes in your app.
Where possible, we recommend that you make any changes in your own app, rather than changing the GIDresources.bundle
directly. This makes it easier for you to update to later versions of the iOS SDK without losing your local customisations.
Warning: Before you start customising
Warning |
---|
When you are customising the SDK UI, there is potential for mistakes to be made. If you find that your app is inoperable, we may ask you to revert to the original SDK files as a first step in diagnosing any issues, and to remove any customised UI settings. |
Warning |
---|
Some customisations on iOS SDK require you to open the IDMetrics frameworks, and change files inside the frameworks. This means that with each new SDK release, you will need to re-apply your customisations. We are working with our third party providers to work out a more maintainable method for these customisations. |
Note |
---|
We will be able to provide advice on customising the UI in the SDK, but there are limitations to what you can change in the UI. |
Info |
---|
SDK version 1.21.0 introduced new capabilities to use customisations in your app, rather than requiring changes inside the |
width | 50 |
---|
1. Changing the loading screen
The 'Loading' screen will appear throughout the greenID workflow, usually as a cover screen while new parts of the process start or finish. The text may say "Loading" by default, or sometimes "We're uploading your images".
Most of the loading screens are part of the native SDK, and can be modified as below.
Note that some of the loading screens are part of the web view, and as such can be modified using CSS changes. You should make sure your CSS and native changes are consistent.
Column | ||
---|---|---|
| ||
|
Loading screen - Fonts and colours
From version 1.13.8, the GIDResources bundle includes a settings file called GIDsettings.plist
. This file can be used to configure the colours and font used on the 'Loading' and 'Uploading' progress screens.
From version 1.21.0, you can include a customised copy of the GIDsettings.plist
file in your own app. Rather than editing the file inside the GIDResouces.bundle
, you can put a copy in your own app, and the SDK will use values in that file instead of the defaults. Copy the default file from the bundle, and place your copy in your own project. Make sure that the new file is included in your build target, so that it gets included in your app build.
Edit the plist file to change the following:
gid_loadingFontFamily
Loading screen - Loading image
The loading screen image is an animated gif file. The default image is provided in the GIDResources.bundle
. To change this images in your app, replace it with an image of the same name, and rebuild your project.
From version 1.21.0, you can alternatively add the images directly in your own app project - note that the names are slightly different, to avoid name clashes with any other images you may use in your app. Make sure that images are added to your project target, so that they will be included when you build your app. This is the preferred method, so that your changes do not get overwritten with a new SDK release.
Loading screen - Text values
To change the text values on the loading screens, add these key/values to a Localizable.strings
file in your app. If you have not set up a Localizable.strings
file before, there is more information at the end of this document. An example localizable.strings file is available on the greenID Mobile release website.
loading_view_title
upload_progress_message
Column | ||
---|---|---|
| ||
2. Changing the camera permission messagesWhen a user first starts the greenID process, their phone will prompt them for permission to use the camera. If they deny permission, they will see a dialog explaining that the process cannot continue without permission. The wording on this dialog can be altered by adding key/values into a An example localizable.strings file is available on the greenID Mobile release website. |
width | 50 |
---|
Camera permissions messages
camera_access_denied_title
We can't access your camera
camera_access_denied_message
Completing this process successfully requires that you allow access to the camera on your device via Settings.
camera_access_denied_button_title
Go to Settings
Column | ||
---|---|---|
| ||
3. Changing the document capture UIThe colours, fonts and text of the document capture process can be changed by placing values into two files in your app: The |
width | 50 |
---|
Document capture UI