Knowledgebase

Branding and Customizing the App

 

Branding

You can brand the codeREADr app with your logo. Why do we offer that? Well, to the app user we are the ‘code reader’ and you are the solution provider. Although very sophisticated, we are a ‘layer’ within your solution – we enable the collection and validation of data. However, you offer your clients the ability to use that data. That’s a critical distinction – and one that’s creating a new opportunities for forward-thinking businesspeople, IT managers and developers. Branding instructions 

On your codeREADr.com Account page you can also change the email address for the 'Contact Us' email within the app's settings and redirect the in-app 'Help' page to your own URL. 

Adding Custom Functionality In-App using Contextual Variables

We’ve enabled clients to add custom functionality within the codeREADr app. Examples include presenting: 

-        Status dashboard

-        Tickets sold, tickets remaining, capacity, etc.

-        Last order quantity, order status, special offers, etc.

-        Asset images, asset status, etc.

-        Student/member/employee images

-        Specific instructions for actions (e.g. safety checks, maintenance, etc.)

-        And much more.

Anyone can put URL(s) in the Response Text when creating their database or in the Service Description when creating a Service. However, to use contextual variables or Webify, a Web developer is typically needed to deploy this feature effectively.

A. Simple - Plain text URLs in the Scan Response Text or Service Description

When creating your barcode database, put a plain text URL in the Response Text or Service Description along with any other text associated to that barcode value. After the app user scans a barcode, they will be able to tap the URL to launch in-app viewing of that Web page and any links embedded within that page.

B. Developer - Context Variables added to plain text URLs in the Scan Response Text or Service Description

When adding a plain text URL to the Response Text or Service Description, you can give it context and direct the app user to a specific URL by using one of these variables appended to the URL:

SCAN_VALUE = $(SCAN_VALUE) [This variable is available only in Response Text]

USER_NAME = $(USER_NAME)

USER_ID = $(USER_ID)

SERVICE_ID = $(SERVICE_ID)

In this way the scan the app user will see and engage with Web content in a context relative to that variable. The URL must be a plain text URL. Here’s a format example: http://www.google.com/#q=$(SCAN_VALUE)

C. Webify - Web Content as a Service

In addition to the typical recording and validation Services offered, you can also create a Web-View-Only Service with our Webify feature (see link below for instructions). Webify will present to the app user an image (such as your logo) or Web page or, if using contextual variables, a specific image or Web page. Any of these contextual variables can be used:

USER_NAME = $(USER_NAME)

USER_ID = $(USER_ID)

SERVICE_ID = $(SERVICE_ID)

D. Webify - Web Content as Response Text or Service Description

Web content within Response Text or Service Descriptions can be generic or contextual using our Webify feature. Any of these contextual variables can be used:

SCAN_VALUE = $(SCAN_VALUE) [This is available only for the Response Text]

USER_NAME = $(USER_NAME)

USER_ID = $(USER_ID)

SERVICE_ID = $(SERVICE_ID)

E. Webify Benefits

The benefits of Webify over plain text URLs include: a) the URL can use anchor text for a better UI; and, b) the content is immediately displayed without requiring the app use to tap a URL.  The purpose is to enable simple and immediate contextual engagement with the app user. Webify instructions.



Related entries:


Contact Us