Link Search Menu Expand Document

Mobile App Onboarding

To set up your apps, certain information and actions are required. The section below outlines the steps and information required. The details will be communicated upon actual onboarding.

  • Setup of Google Play Console account: A Google Play Console account must be created by the client. This is the platform the Android app will be release on. At least the following email addresses need to be added support@spaaza.com & bernard.wittgen@spaaza.com and give the “admin” role. Start here. After initial setup: configure privacy policy webpage and paste the URL, answer questions about what data your app collects (location, contacts, etc.), pick age rating by answering a questionnaire, choose which countries can download it, set price free.

  • Setup of Apple Developer / App Store Connect account: An App Store Connect account must be created by the client to release the iOS app. At least the following email addresses need to be added support@spaaza.com & bernard.wittgen@spaaza.com and give the “admin” role. Start here. After initial setup write privacy policy and add URL, answer data collection questions, complete age rating questionnaire, select distribution countries (if already possible), set pricing (none), add App Store keywords and descriptions (if already possible).

  • Access to staging version of mobile app: Spaaza will share a staging (testing) version of the mobile app for iOS and Android. There is not prior setup required. This initial version will not have everything configured yet. Along the way updates to the app will be provided up until a point we can start the user acceptance test (UAT)

  • Setup of Firebase Crashlytics account: Create a Firebase account to enable push notifications (FCM), crash reporting (Crashlytics), and Google Analytics for the app. Choose a plan (ask Spaaza if unsure). After registration, Spaaza will handle the setup and integration. A Spaaza developer must be added as an admin. At least for the following email addresses support@spaaza.com & bernard.wittgen@spaaza.com. This will be one of the later steps needing configuration.

  • Content inside of the app: The client will be the owner of the content inside of the app. During the process of setting up the app it is advised to upload your a few graphics the your content team has designed. The earlier this happens, the better you will be able to tweak the design along the process. It also will let you can experiment with layouts and styles in a more realistic way. When the app will be tested in the user acceptance test (UAT) the campaigns it is mandatory for the app to have content that is as close to the content you want to go live with. For more information on the styling guide see the Image asset guidelines section.

  • Hosting files for the password reset deep link: you will need to host a folder files that enable the link form a password reset email to open the mobile app during the password reset flow. These links needs to be directly accessible at the root of your domain (200 and no redirects). (https://example.com/.well-known/apple-app-site-association, https://example.com/.well-known/assetlinks.json)

  • Setup Google Wallet API & Google Cloud Account integration: you will be the owner Read docs step 1-4 (for step 3 please use “Generating Google Wallet REST API authentication credentials” option and share these details with us securely once created). On Google Pay & Wallet Console under “Users” please add/invite support@spaaza.com and bernard.wittgen@spaaza.com and give them admin rights (https://pay.google.com/business/console). Note: Step 3 will require you to create a Google Cloud project and generate a JSON key file from the service account that you have linked to the Google Wallet API. This JSON key needs to be shared securely.

  • Setup Apple Wallet: an Apple wallet wil be set up for the staging and production environment.

  • Styling: Color: Provide a primary color for theming as hex or RGB.

  • Styling: Font files: Provide the primary font file for the app. A secondary font is optional. Provide all required font style files separately (e.g., regular, bold, italic).

  • Styling: Assets: Provide other required design assets (logos, icons, etc.). Please see the design guide Image asset guidelines

  • Config: Whitelisting email domain: Provide us with the email address you want us to use to send your password reset emails from (e.g., noreply@yourdomain.com). On your side, update DNS settings with SPF, DKIM, and DMARC records to allow Spaaza’s servers (api0.spaaza.com and apistage0.spaaza.com) to send emails using this domain.

  • Config: Hosting identification file for password reset link (deep links): We will provide a file that needs to be hosted on your website to enable the password reset functionality. Please provide the URL from your site where this file can be hosted.

  • Config: Link to terms and conditions: Provide a hosted page URL from your website (e.g., https://example.com/terms-and-conditions)

  • Config: change names of core page: Please communicate to Spaaza if you would like to keep the default names for the restricted pages: Home, Rewards, and Deals, or if you would like their names to be changed.

  • Config: Link to FAQ: Provide a hosted page URL from your website (e.g., https://example.com/faq) (optional)

  • Config: Link to website: Provide a general hosted page URL for your website (optional)

  • Config: Store Icon Types:
    The store icons used on the store list views and map screen will be either one of the following:
    • A. All stores have the same icon that is displayed (needs to be provided by client).
    • B. Stores that have not yet joined the program but are planning to join can be displayed with a “non-participating” icon. Two icons required: participating store and non-participating store (needs to be provided by client).
    • C. Stores of various types that require unique icons to differentiate them in the app. A variety of icons will need to be provided for these stores (needs to be provided by client).

  • Config: required or non-required fields in onboarding flow: Stipulate which fields are required or optional in sign-up. Required fields should be justified to customers and be necessary for the app and program to function.

  • Config: removal of fields in onboarding flow: Stipulate which fields you want to remove entirely. Fields that can be removed are: “Receive deals by SMS”, “Receive direct mail”.

  • Config: member card login: Are you migrating systems and do you already have users that collected points through any physical cards. We can set the app up so that users can register with their member card and migrate their points. Please reach out to Spaaza if this is the case”.

When in doubt, please reach out to our team.