Skip to main content
All CollectionsGetting StartedOrderingPlus for Advanced Marketplace Operations
Documentation for Building Apps from the Ordering Dashboard
Documentation for Building Apps from the Ordering Dashboard

Create your Apps directly from your dashboard, build, test, upload, and launch.

Mauricio avatar
Written by Mauricio
Updated over a week ago

Prerequisites

Before you start, ensure you have configured your Apple Store and Play Store accounts. For iOS, refer to this iOS guide or ask the support team for assistance.

Be sure that you have your identifiers added in your Apple account

Note: Be sure that you have the same bundle available for Play store and Apple store

Like with the our old apps, is required to create 2 identifiers and 3 groups for each app

Example with customer app

First 2 identifiers, 1 only with your package and other with your package+OneSignalNotificationServiceExtension

Ex:

Identifier 1: com.orderingplus.app

Identifier 2: com.orderingplus.app.OneSignalNotificationServiceExtension

For this app, don’t forget to mark the groups, merchant, push notifications capabilities in each one

Now, the 3 required groups. One with your package, other with your package+.onesignal and the last one with your package+OneSignalNotificationServiceExtension

Ex:

Group 1: group.com.orderingplus.app

Group 2: group.com.orderingplus.app.onesignal

Group 3: group.com.orderingplus.app.OneSignalNotificationServiceExtension

Then, if your first 2 identifiers, add the 3 groups created in the groups capabilities

NOTE: Don’t forget to add to the identifiers the next required capabilities for each app

For customer app:

  • Access wifi-information

  • App groups

  • Apple pay payment processing

  • Associated domains

  • Maps

  • Push notifications

  • Sign in with google

For driver/business app:

  • Access wifi-information

  • App groups

  • Associated domains

  • Maps

  • Push notifications

If you don’t enable this capabilities in the identifiers, the app will fail

NOTE: Sometimes, the dashboard will show a build error without showing a “certificate error” or “Provisional profile error” as usual. So if you search this text; “The requested URL returned error: 502” this means that there’s a problem with the servers, so you need to press build again.

Required fields to Build Your App

1. Accessing the Dashboard

Log in to the dashboard and click "My Products" in the left sidebar.

2. Add App Basic Settings

Configure the basic settings of your app:

  • Name

  • Package

  • Version

  • Description

3. Add Constants

Provide the following constants:

  • Merchant ID (available from Play Store or Apple Store) ex: merchant.com.ordering.app

  • Google Maps API Key(Optional but important for maps)

  • Facebook ID(Optional)

  • Google Reverse Client ID (Optional)

  • Intercom App ID(Optional)

  • Intercom App Key(Optional)

These constants are optional for building the app, but it is recommended to configure the Google Maps API Key for proper functionality.

The Facebook ID and Google Reverse Client ID are needed for Facebook login and Google login, respectively.

Intercom credentials are necessary only if you require Intercom integration in your apps.

All optional marked above, can be skipped and added later

4. Add Images for the App

Upload the images that will be displayed in your app:

  • Home Hero

  • Logotype

  • Empty Active Orders Section

  • Search Not Found Result

  • Empty Past Orders Section

  • Tutorial Images (6 images)

  • Store List Banner

  • Order Type Images:

    • Curbside

    • Delivery

    • Drive-thru

    • Eat-in

    • Pickup

    • Catering Delivery

    • Catering Pickup

  • All Categories Result Image

  • Long Logo

  • No Internet Image

  • Dummy Product Image

5. Configure Theme Colors

Add theme colors by entering a color code or selecting a color from the palette.

6. Add Google Services for Android and iOS

Upload the necessary Google services files (.json and .plist) in the "Files" section.

This step is optional or required only if you use Google login.

For instructions on obtaining these files, refer to this guide.

7. Build Settings

Differently as how the apps used to be builded, in the dashboard is not required a user, password and 2FA, now it will be required to create a file where the user info will be stored.

Please follow the next instructions

To build iOS app, a .p8 file is required;

To obtain this file, please follow steps below:

  1. Create a new App Store Connect API Key in the Users page

    1. For more info, go to the App Store Connect API Docs

    2. Select the “Keys/integrations” tab

Reference:

  1. Give your API Key an appropriate role for the task at hand. You can read more about roles in Permissions in App Store Connect in this case, admin

  1. Note the Issuer ID as you will need it for the configuration steps below

  1. Download the newly created API Key file (.p8)

    1. This file cannot be downloaded again after the page has been refreshed, please consider this before to continue

After download the .p8 file, add it in this API key file section:

Required Information:

  • Team ID

  • ITC Team ID (optional, only if an account is connected to another)

  • API Key ID

  • API Key Issuer ID

  • API Key Issuer ID File (.p8, .txt)

For Android:

Required Information:

  • Key Alias

  • Key Password

  • Store File (.jks)

  • Store Password

  • Play Store Credential File (.json) (optional)

8. Build Resources

Upload images for the Apple and Android stores, such as

  • app icons

  • notification icons for Android

  • splash screens for both stores

9. Build Your App

Depending on your requirements, you can build your app in different modes:

  • Build Test: If you need the .ipa or .apk for testing

  • Build PRO: If you need the app to be signed for distribution

The Android .AAB file is the file you will use to distribute your app.

10. Done!

This guide will help you build and configure your apps from the Ordering dashboard. For any further assistance, please refer to the respective images provided for each step or contact the support team.

Did this answer your question?