Overview
Your configuration choices allow us to tailor your Audiorista white-label app to your needs.
Branding
To allow your brand to really come through, many parts of the app can be customized to your needs. The more admin-related of these (URL of your terms-of-service etc.) can be found in the Order Form you fill out when ordering Audiorista white-label apps. Below are the design options you can adjust.
Colors
All colors must be supplied as HEX codes (ex. #ffffff).
Name | Values | Description |
style | Required: light / dark | |
corner radius | Required: number | How many points of rounding to apply to Track/Playlist images in the apps (0 for sharp corners) |
default_background_color | Required | |
default_primary_color | Required | |
default_muted_color | Required | |
default_accent_color | Required | |
background_color | Optional, default: default_background_color | |
bar_color | Optional, default: default_background_color | |
launch_background_color | Optional, default: default_background_color | |
label_color | Optional, default: default_primary_color | |
secondary_label_color | Optional, default: default_primary_color | |
secondary_tint_color | Optional, default: default_primary_color | |
text_color | Optional, default: default_primary_color | |
tint_color | Optional, default: default_primary_color | |
separator_color | Optional, default: default_muted_color | |
unselected_tint_color | Optional, default: default_muted_color | |
alert_color | Optional, default: default_accent_color |
Images
For a guide to Artwork in Audiorista apps, see What are the dimensions of the different graphical resources?
Add-ons
When configuring your apps, several integrations with third-party services can/must be decided by you. An explanation of these can be found below.
Authentication
- Options:
- None
- Firebase (default)
- Custom SSO
Audiorista’s default login/signup solution is Firebase, which supports the classic email & password authentication. If you have an existing Firebase setup, we’re happy to use that. Should you have an existing authentication flow for your users (Wordpress, for example), we can adapt our Web auth backend to use that.
Permissions
- Options:
- None
- Synced with authentication backend
Should you want to restrict content in the apps based on information in your authentication backend (Firebase or other), that’s possible using our Permissions feature.
Paywall
- Options:
- None
- In-app subscriptions
- In-app subscriptions + Stripe Billing
Audiorista apps come pre-configured with an optional paywall that can be hooked up to both in-app purchases and Stripe Billing.
Facebook SDK
- Optional
- Requires: Facebook App ID
Our apps integrate with the Facebook SDK, allowing you to track the success of your Facebook campaigns.
Apple Car Play/Android Auto
- Optional
- Requires: additional review from Apple/Google
Audiorista’s apps integrate with both Apple Car Play and Android Auto, for a great listening experience while driving.
Dynamic Links
- Optional
- Requires: setup in Firebase
See Sharing
Tabs
The main navigation component of the apps is the Tab-bar. It is fixed to the bottom of the screen on all tabs accessible through it. The number of items in the tab bar is variable and based on the configuration you choose, but more than 5 are probably bad for usability.
The following Tabs are available:
Tab | Description | Optional features |
Feed | Prominent feed of a specific Playlist | Quick-actions: Search, Settings |
Layout | Customizable list of Playlists. See App-layouts | Quick-actions: Search, Settings; History-carousel |
Multi-layout | Multiple Layouts in one Tab | Children: Layout |
Queue | The customer's current play-queue | |
Downloads | The customer's downloaded Tracks | |
Favorites | The customer's favorited Tracks | |
History | The Tracks a customer has listened to | |
Library | Multiple features in one Tab | Possible children: Queue, Downloads, Favorites, History |
Settings | Subscription status, logout | |
Search | Track-search |
Other
Several minor aspects of the apps can also be configured to your preference:
Tab | Values | Description |
Enable signup | Yes / No | When using Firebase for authentication, whether or not creating a new account should be possible |
Auto-open player | Yes / No | When a customer clicks a play-button, should the player open or should the customer continue browsing |
Track-click action | Play / Show details | When a customer clicks a Track in the apps, should it start playing or show the Track's details-screen |
History-carousel limit | Number | On Layout-tabs with the History-carousel enabled, how many Tracks should be displayed |