Today, enterprise mobile apps usually compromise in two areas: performance and customization. Apps that are built using the native programming language of the device platform have greater performance, such as responding quickly to the user's touch, and have access to more device features. The downside is that native apps are typically more restrictive around customization, requiring app updates to make changes. Non-native apps, or apps built using web technology and simply packaged in an app container, get around this customization challenge, but they give up performance as a result.
Roobiq is different and offers the best of both app types.
Roobiq is a native app, but is built with a flexible architecture that allows for on-the-fly customization. At its core, the Roobiq app is powered by user- or organization-specific metadata, all of which is centrally managed by the Roobiq server. We call this the "Workflow Engine." The metadata that goes into the engine is broken up into three hierarchies of information: field layouts, actions, and workflows, with each layer building upon the preceding layer.
The lowest level in the metadata is the Field Layout information. Fields are mapped from Salesforce and all available field types are supported in Roobiq. How these fields are displayed on the device is setup by the field layout information in the metadata. When viewing a record, field layout information is used to adjust the ordering and display of fields. Less important fields for mobile users can be hidden or moved farther down the screen to simplify the experience.
Sitting on top of the field layout information are Actions, which are tied to objects in Salesforce. There are two main types of actions: create and update, allowing a user to create or update an object in Salesforce. Actions can be customized by adjusting the field layout information within them. For example, if a user only needs to update certain fields on an opportunity, the update action can be customized to show only the fields required. However, when the user needs to create an opportunity all of the required fields can be displayed. This customization allows for efficient use of the small screen in mobile devices.
The last level in the metadata hierarchy is Workflows. When designing Roobiq, we realized that users would often need to perform multiple actions together. On the desktop, this is easy to do given the screen real estate and the ability to navigate with a mouse. However, on a mobile device the small screen and more limited navigation capability mean performing multiple tasks in different areas of an app can be difficult. Roobiq simplifies this by allowing actions to be grouped together into workflows. For example, the app comes setup with a default workflow for logging a call. In the call log workflow, there is one required action: to create a completed task that includes the notes of the meeting. However, there are several optional actions, such as creating a follow-up task and updating the related objects to the call (i.e., the account, contact, or opportunity). By tying all of these actions together into one view, Roobiq shows users exactly what needs to be done and they can accomplish the follow-up faster. This improves user adoption and data capture.
Together all of these layers in the metadata give company administrators the power to customize Roobiq to match their sales process. Custom objects and fields are supported with a paid license and can be used in all layers of the metadata. Changes to the metadata will be synced to a user's device the next time the app connects to the server and immediately those changes will be available. This powerful and flexible architecture means companies don't have to sacrifice performance while maintaining the flexibility to adjust the capabilities provided to users.
Need more information?
Contact us and we can discuss how Roobiq's Workflow Engine can streamline your sales process