Go>Sign OEM Distribution & Branding
Go>Sign - OEM Distribution & Branding page is intended for Ascertia’s clients who wants to update the branding of the mobile apps or they want Ascertia to publish mobile apps for them.
Overview
This page identifies the areas which are brandable in Go>Sign Mobile Apps. The following elements are brandable and can be changed according to the theme of the organisation and business:
Colours
Images
Product logos
Product name
Language strings
Any element of the user interface which is not mentioned in this document is not brandable.
For OEM distributions, this page covers the basic requirements of Ascertia that a client needs to fulfil.
Branding
The following are the components of the mobile applications that are brandable:
Colours
Following is the list of the colour levels that Go>Sign Mobile uses, with the explanation of where they are used and what are the default values.
Level 1 colour (Ascertia brand = Black) - # 232323
This colour is used in:
Top bar background
Level 2 colour (Call to action, Ascertia brand = Green) #55cf31
Colour that is used only for important items/buttons/content in the overall UI. This colour is used in:
Buttons background
Level 3 colour (Ascertia brand = Red) # e03500
This colour is used in:
Alert error icons
Level 5 colour (text only, Ascertia brand = White) #ffffff
This colour is used in:
Button text
Headings in top bar
Main menu icons on the dashboard
Main menu heading labels
Level 6 colour (line only, Ascertia brand = Tint 1 of level 1 colour) #797979
This colour is used in:
Dashboard counter separator
Level 10 colour (Ascertia brand = Light black) #2f2f2f
This colour is used in:
Dashboard screen background colour
Product logo
The following logo is brandable, so it is required for branding.
Product Logo
OEM distribution
Ascertia provides mobile application customisation and separate distribution of customised applications for clients’ businesses. Businesses can provide their own branding along with other necessary details related to application deployment, allowing Ascertia to compile the application with all customised resources and submit it to the app stores on behalf of the client. The following customisations are available in Go>Sign mobile applications, in addition to branding.
Application default configuration
Certain configurations must be defined before the application can be compiled and submitted to the app stores. Clients are required to provide the following details:
Base URL to APIs
Example: https://adss.ascertia.com/adss/service/ras
Application name
A new application name is required; this name will appear on mobile devices, along with an associated application icon.
Example: Go>Sign Mobile
Application icon
An application icon is required to compile the application with a new icon. This icon appears on the mobile device’s home screen (springboard) and helps the application stand out from other apps.
Example:
Splash screen
A splash screen appears in mobile applications and remains visible until the necessary resources are loaded in the background, after which the application's first screen is displayed. Typically, the splash screen is an image provided by the client and may include introductory content to engage users while the application loads.
Example:
Checklist
The following table provides a checklist and the required information for both platforms (Android and iOS).
Checklist and Required Information
Application Name
Example: Go>Sign Mobile. The name should be up to 50 characters in length.
Subtitle/Short Description
Example: Premier Signing Solution. The length should be up to 30 characters.
API URL
Google Account Credentials
Required for configuring push notifications through Firebase services and managing crash reports via Crashlytics.
Customers can either:
Grant Ascertia temporary Admin rights on the Firebase Console to create and configure the required project, or
Share their existing Firebase project credentials with Ascertia. If neither option is preferred, please follow the process outlined in the "Push Notification (by Client)" section below.
Apple Developer Account Credentials
Required to create development and production certificates for submitting the application to the Apple App Store.
Play Store Developer Account Credentials
Required to create development and distribution environments on the Google Play Store.
Application Description
An example screenshot is provided below:
iOS-Specific Requirements
Application Icon
Size: 512 px × 512 px (PNG format).
Splash Screen
Apple guidelines recommend providing multiple images for different orientations and resolutions.
App Store Icon
Size: 1024 px × 1024 px (PNG format).
Support URL
Apple displays this link on the store page for users to submit queries related to the application.
Marketing URL (Website)
If users want to know more about the application, they can follow this link.
Contact Information
Provide the name, email address, and phone number of a contact person.
General Information
An example screenshot is provided below:
Privacy Policy URL
Required so that users can review the privacy policy before downloading the application. Apple will redirect users to this link from the store page.
App Review Information
Apple requires one set of test account credentials for the provided API URL. This account is used by Apple to verify the application. A screenshot from the store is shown below:
Android-Specific Requirements
Application Icon
Must be provided in two layers:
Background (Non-Transparent): 432 px × 432 px
Foreground (Transparent with Logo): 432 px × 432 px
Maximum drawable area: 288 px × 288 px.
For more details, see Google’s Adaptive Icon guidelines.
Legacy Icons
Must be provided in the following size with sharp corners: 192 px × 192 px.
Splash Screen Image
Size: 1280 px × 1920 px.
Home Screen Icon
Size: 1280 px × 1920 px.
Play Store App Icon
Size: 512 px × 512 px, shape: full square.
For more details, see Google Play’s App Icon guidelines.
Play Store Feature Graphic
Size: 1024 px × 500 px.
Push notification (Configured by client)
If the client chooses to manage Firebase independently, they must create their own Firebase project and connector, then provide the following files to Ascertia:
google-services.json (for Android)
GoogleService-Info.plist (for iOS)
These files will be integrated into the brandable apps before upload.
Accounts
This section explains the account invitation requirements for app release on the Google Play Store and Apple App Store. It also includes information regarding the Firebase account needed to enable features such as push notifications.
Apple:
Name: Mobile Brandings
Email: [email protected]
Role: Admin/App Manager
Developer Resources: Checkmark (Access to certificates, identifiers & profiles)
Google:
Email: [email protected]
Account Permission: App Access, Releases, and Store Presence
Firebase:
Email: [email protected]
Role: Editor
Apps submitted by clients
If the client submits the applications to the stores themselves, the "Checklist" section is not applicable. However, additional information is required to create a signed build for both iOS and Android platforms.
iOS
Bundle ID (e.g., com.company.appid)
Production Certificate (.p12 file)
Provisional Profile
Firebase Plist file (GoogleService-Info.plist)
Android
Application ID (e.g., com.example.app)
google-services.json file from Firebase
Keystore (.jks file) and credentials (storePassword, keyPassword, keyAlias) to sign the app
Last updated
Was this helpful?