- For Producers
- For Artists
- Help & Support
- About Us
- Contact Us
- Flex App Framework
- Flex Overview
- Quick Start Guide
- CMS Plugins
- Themer Guide
- Developer Guide
- Support Group
- Legacy MP3 Players
- Seller Guidebook
- Beat Brokerz Introduction
- Producer Account Setup
- Music Administration
- Seller Dashboard
- Beat Inventory
- Customer Orders
- Sales Reports
- Music Statistics
- Custom Licenses
- Discounts & Codes
- Payout History
- Music Licensing Concepts
- Promotions & Marketing
- Buyer Handbook
Many configurations for how your application looks, loads, and behaves when integrated with your website can be made directly from your flex app settings on Beat Brokerz. Some or all of these settings can be overridden by custom programming on your site or by custom widgets you are using, however, these settings define the default behavior of your application when not specifically overridden elsewhere.
To learn how to override features and settings of your flex app on-the-fly for specific web pages, have a look at our developer documentation.
Fullscreen Mode / Mobile App
Every flex app has a built in fullscreen mode which doubles as a mobile app for mobile devices. It is a fully self-contained interface that can be used to browse, listen, and purchase music from your flex store. The fullscreen mode can be opened and closed on demand from any page which has your flex app integrated. As mentioned, the fullscreen mode when viewed on mobile devices (such as phones and tablets), automatically adapts to look and function like a native mobile app for the device it's being viewed on. Therefore, it is effectively an on-demand mobile app for your music store.
Since the fullscreen mode can be opened and closed on-demand, and it also doubles as a mobile app, there are a number of different ways in which you may want to leverage its functionality for the benefit of your website visitors:
Closed initially on all devices, can still be opened:
This is the default display mode. In this mode, the fullscreen interface will only be shown when specifically opened via a widget or other custom programmed element on the page. All of the resources needed to display the fullscreen mode are loaded when the page is loaded, but the fullscreen mode will lay dormant until opened.
Closed initially for desktops and tablets, open initially for mobile phones:
This option allows you to take advantage of the fullscreen mode in the mobile app format and provide a touch optimized interface to your mobile phone users by default. With this option selected, the webpage hosting your flex app will load and show briefly, and then (for mobile phones) immediately display a message that the fullscreen mode is loading just before the fullscreen mode is opened. This allows your mobile phone users to jump straight into the mobile app while users on all other devices still interact with your webpage as the primary interface.
Closed initially for desktops, open initially for tablets and phones:
This option is essentially the same as the option listed above, with the difference being that the fullscreen mode is opened by default for both phone and tablet users, while desktop and laptop users are still going to get your primary webpage interface first, and need to manually open the fullscreen mode to interact with it.
Open initially on all devices, can still be closed:
This option is another extension of the two previous options listed above. In this mode, the fullscreen mode is loaded and opened by default for all devices and browsers viewing the webpage which hosts your flex app. The fullscreen mode can still be closed by the user which will leave them interacting with the underlying webpage.
Open initially on all devices and cannot be closed:
In this mode, the fullscreen mode is the only interface that can be used on the webpage which is hosting your flex app. This mode essentially mimics a native app because the user will not have the option to close the interface, or to access the underlying webpage which is hosting it.
Disabled on all devices and cannot be opened:
This mode bypasses the loading of resources required to display the fullscreen mode / mobile app interface completely. The user will not be able to open the fullscreen mode manually, nor will widgets or other programming on the page. With this option selected, there will be a slight improvement in performance (load time) of the webpage hosting your flex app, since the resources needed to display the fullscreen mode will not need to be loaded. Other widgets and custom flex app elements on your page will however still function normally.
You can upload a custom background to replace the default background shown on your fullscreen mode home page. The custom background is only shown on the home page of your fullscreen mode, since the rest of the screens in your fullscreen mode have a native background designed to maximize readability of the content on those screens.
When you upload a custom app background, you should keep in mind that it can be viewed on a variety of devices with a multitude of screen dimensions and orientations. For this reason, it is best practice to upload a background image that is at least twice as tall as it is wide, and has a minimum width dimension of 1200 pixels.
One-Click Setup Features
To make your flex app integration as easy to use as possible "out of the box", there are a few different built-in widgets which can be loaded and displayed universally on the pages which host your flex app. When you choose these one-click features in your flex app settings, they are loaded and displayed automatically on any page which hosts your flex app without the need for you to add any extra code or elements to your pages. They are designed to provide a standard interface to your music and playlists that will look clean on most sites "as-is" without any significant customization.
These widgets can also be displayed on a case-by-case basis using shortcodes or htmlcodes. To do this, you wouldn't choose them as a "one-click setup" feature, but rather add them as a custom widget to the widget autoloader (described below) and then selectively decide which pages they should show on by using shortcodes or htmlcodes.
Widgets can be used to add all sorts of different pre-fabricated interface elements and features to your web pages (which interface directly with your flex app music store). You can learn more about them on our widgets page.
In order to use a flex widget on one of your pages, you first need to include the widget script itself. The widget autoloader provides you a convenient way of adding the widget script to your webpage without touching any of your html source code. Widget scripts that you autoload will be loaded on every page that the flex app is installed to.
Note: If you want to selectively load a widget script on just specific pages (and not every page that hosts your flex app), you would just reference the widget script (using a script tag) in the html source of your webpage rather than including it with the built-in widget loader in your flex app settings. If you use a lot of widgets, this method can improve the performance (load time) of your webpages by not loading every widget you use on every page.
To add a widget script to your autoloader, paste the full url to the widget script itself in the text field. The script can be hosted on your own domain or another domain, both ways will work.