Skip to main content

Internal Guide – App Publishing

This process covers the steps required to review and validate requests for publishing applications. All approved apps will be prepared and submitted to production environments in both stores.

Written by Deira Alanis

Parte 1 - Ticket Reception

📩 1. Ticket Reception

Review the ticket carefully once received.

✅ 2. Initial Validation Checklist

🔐 Developer Accounts

The client must have:

  • Active Google Play Console account

  • Active Apple App Store Connect account

Additionally:

⚠️ If accounts are missing or access has not been granted, contact the requester and ask them to provide it before proceeding.

🖼️ Assets

The ticket must include:

  • App logo (working link)

  • Screenshots/images (if available)

⚠️ Make sure links are accessible.

🏪 Project Setup

  • The project must include at least one real store

  • Demo-only projects are not allowed

⚠️ Apps with no real content may be rejected by Apple/Google.

📄 Required Information

Confirm the ticket includes:

  • Requester name & email

  • Project name

  • App name(s)

  • Type of apps (e.g., Driver, Business, Franchise)

  • Developer account access (if needed)

  • Tracking link (e.g., Asana)

📌 3. Example Ticket

New app Request, take a look at the information.

Requester Name: Deira
Email: [email protected]
Project: deiraproject

App Logo: https://...

App(s) Name(s):
- Pet Zone
- Driver App
- Business app

Apps we are creating this time: Franchise App, Driver App, Business App

Developer Account Access:
Asana Link: https://app.asana.com/

🚦 4. Validation Outcome

✔️ Complete

Proceed to the next step.

Incomplete

Request missing information (including developer accounts and access) before moving forward.


Parte 2 - App Setup & Build Configuration

🎯 Objective

Configure the app information correctly in the user’s dashboard before generating builds.


🧭 1. Access User Dashboard

Log in to the user's dashboard and locate the applications to be configured.

⚙️ 2. Update App Information

For each app, update the following fields:

  • App Name
    Set according to the request.

  • Package Name
    Use the project base and update the suffix based on the app type.

    Example:

    • Base: com.deiraproject.45sde64

    • Updated:

      • com.deiraproject.franchise

      • com.deiraproject.driver

      • com.deiraproject.business

  • Description
    You can use the app name as a default description.

  • Version
    Set to: 1.0.0

Use the following image as a guide:

Annotation on 2026-05-04 at 23-02-30.png
Did this answer your question?