Status: Available Scope: Loop Messenger & OnDemand Platform Release: July2015
Purpose & Scope
Embed Loop directly into an existing App. Leverage the mobile web interfaces of Loop including the create and conversation flows. Smart metadata passing between App and Loop.
Provide convenience and a seamless Loop experience to existing users of the existing App. Save development time by leveraging Loop’s out-of-box, configurable and parameterized HTML5 user interfaces.
The Loop HTML5 app experience is embedded using an ‘App frame.’ Examples below:
The App must designate a frame into which the Loop page will be drawn (shown here as dotted outline). Branding and themes are fully configurable; configured to match the look and feel.
Loop supports URL-encoding of guest data, either via plain-text parameters (Example #1) or tokenized guest profile reference via slug (Example #2).
See Live Demo Example for specific fields and details.
If parameters are passed to Loop in the initial HTTPS page-load request, those parameters are captured and applied to the client-side mobile application. In the example below, a location (location ID ‘005’), guest loyalty program number, guest name, and guest room number are all passed to Loop initially. The Loop experience (right-center) and resulting Loop to the enterprise (right-most) reflect this additional information. The flow without parameters is shown for contrast (left-center):
Both standard field (e.g. location) and custom fields (e.g. loyalty number) are available in this integration scenario.
The Loop mobile UI is a self-contained, stateful HTML5 web application which does not require a ‘page re-load’ after initialization. All user actions within the Loop application do not require a page re-fetch, as depicted below:
User Profiles & App Sequence
Using the Loop RESTful Web Services API, an App or third party system (‘Other System’) may optionally create a user profile in Loop before loading the Loop interface. A pre-created user profile allows a more rich and convenient user experience for the guest.
In the figure above, the user account is optionally created by either system before fetching the Loop mobile web UI. Alternatives include a lookup of user record (versus create).