Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Please note that this document is a draft and still not finalized.

This page describes the premium-base implementation in Mobility web and mobile applications.

Premium and Base Differentiation

In a field stacked with competitors, based on the Mobility business model, two product variations have been introduced as ‘Premium’ and ‘Base’.

Premium and Base Features on Web

Premium Features

Base Features

  • Create Subscription Payment Certificates

  • List & view Receipts & Purchases

  • List, view & pay Invoices

  • Entrances (Entry Tickets)

  • Tracking

  • Classes

  • Subscriptions

  • Services

  • Value cards

  • My pages

  • Events

Premium and Base Features on Mobile App

Premium Features

Base Features

  • Create Subscription Payment Certificates

  • List & view Receipts & Purchases

  • List, view & pay Invoices

  • Tracking

  • Classes

  • Subscriptions

  • Services

  • Value cards

  • My pages

  • Events

  • Bluetooth Entrance

Settings

The appPremiumFeaturesActive setting can be configured from the back office on the feature level. If this setting holds True , then that means the corresponding feature is a ‘Premium' one and if it is False , it means that the feature is a 'Base’ one.

To manage premium -base features on the app level, for both mobility mobile application and web application, either addonAppBaseFeaturesActive setting or addonAppPremiumFeaturesActive setting must be enabled.

In order to get all features, both above settings must be enabled. The base toggle functionality is not a part of the premium toggle setting.

  • No labels