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 iOS customisation.  To give the best user experience, you should make your CSS and SDK customisations consistently.  

To customise the native Android user interface, simply override the resources provided by the greenidsdk_resources module, in your application's /res/ folder.  Your build system will determine which resources are used in your app - resources that get included later in the build process will override earlier values. 

We recommend that you make any changes in your own application's /res/ folder, rather than changing the greenidsdk_resources module directly.  This makes it easier for you to update to later versions of the Android SDK without losing your local customisations.  

Warning: Before you start customising

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.  

2. Changing the camera permission messages

When 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 why the camera permission is needed. 

The wording on this dialog can be altered by adding values into a /res/values/strings.xml file in your app.  

There are several different wordings that can be changed, depending on whether the user has denied permission once, or always, and depending on whether the process can continue with or without the camera.  

You can look inside the  greenidsdk_resources module to see the default values in strings.xml.  

3. Changing the document capture UI

The colours, fonts and text of the document capture process can be changed by placing values into two files in your app.  Make sure you make changes to your own copy of these files in your app.  Don't directly change the files in the greenidsdk_resources module, or inside the catfish .aar files.  

You can look inside the  greenidsdk_resources module to get examples for these files and values.  

4. Changing the document review screen UI

The document review screen appears immediately after a document capture.  Some of the text on this screen can be customised by making changes in a /res/values/strings.xml file in your app.  Parts of the text on this screen are rewritten depending on the document type, and they cannot be customised at this point.   

The text strings for this screen can contain basic HTML to make words bolded.  

5. Changing the selfie capture UI

The colours, fonts and text of the selfie capture process can be changed by placing values into two files in your app.  Make sure you make changes to your own copy of these files in your app.  Don't directly change the files in the greenidsdk_resources module, or inside the catfish .aar files.  

You can look inside the  greenidsdk_resources module to get examples for these files and values.