OnScreen

Use Cases

While Ingestion Services are designed to help us take in data, OnScreen as a product is designed to provide a seamless experience in retrieving data from our systems to be displayed in meaningful ways.

OnScreen is meant to act as an optional data interface that encompasses a number of specific user-functions when other embedded solutions are not possible.

Examples could include:

• a customer-facing tablet for customer onboarding.

• retrieving customer balances in situations where we do not support a POS.

Whenever possible, the goal should be to use OnScreen only as a last-resort when a POS plugin will not suffice, or for fulfilling a use-case that would be inappropriate to be attached to a POS.

Deployment and Installation

Similar to how we handle deployments for POS plugins, OnScreen would be made available as an alternative install from our Dashboard.

We would notify users in cases where we did not support their POS system, and would direct them to install OnScreen instead.

The installer would navigate through a similar set of steps, and would also include a unified configuration interface for all of the available OnScreen installations for a vendor.

OnScreen should also be made available as an Android and iOS application.

A rebranding of "OnScreen" may be in order to better align its role as a supplemental support application for the Spoonity platform.

User Interface

The OnScreen application would be presented in two different interface views:

• embedded

• standalone

The "embedded" view would allow OnScreen to function in as integrated a way as possible. In situations where the underlying point of sale software runs in fullscreen mode, "embedded" OnScreen would float above it, similar to how it operates today as an overlay.

In instances where it is supported, "embedded" mode could also operate on mobile devices (such as using Android's "bubbles" functionality).

In instances where this is not possible, or for other point of sale systems that do not operate in fullscreen mode, "standalone" would be acceptable.

In "standalone" mode, OnScreen would simply function like any other application, and users would toggle between its application window and the point of sale.