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:
The client must share credentials or grant admin access to [email protected]
⚠️ 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.45sde64Updated:
com.deiraproject.franchisecom.deiraproject.drivercom.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:
🖼️ 3. Replace Default Images
Replace all default images with the project logo/assets.
🛠️ Image Size Generator Tool (Windows)
Use the following script to generate images in different sizes:
How to use it
Create a folder and place the image/logo inside it.
The image must be named:
logoPlace the executable named Generador de imagenes in the same folder.
Double-click the executable.
Wait for the tool to generate all required image sizes.
🛒 Customer / Marketplace App
Replace the images marked in the following references:
Additionally:
(1) The image named "Tutorial Image 4" must also be replaced.
The current image contains a non-Apple device, which may cause the app to be rejected during App Store review.
Use the following replacement image:
🚗 Driver App
Replace all marked images shown in:
Additionally:
Tutorial Image 5 must also be replaced.
Replace the text "Driver App" with the actual application name.
Reference image showing what must be edited:
Download and edit the following image:
🏪 Business App
Replace the marked images shown in:
🔑 4. Add API Keys
🍎 iOS Configuration
Fill in the following fields:
Team ID
API Key ID
API Key Issuer ID
Attach the .p8 file.
Reference:
After completing the fields, press Save.
🤖 Android Configuration
Fill in the following fields:
Key Alias:
orderingKey Password
Store Password
Attach the .jks file.
Reference:
After completing the fields, press Save.
🚀 5. Build & Test the Applications
Once all the required information has been completed, generate the builds for the application.
Generate both:
Build PRO
Build AAB PRO
Wait until the build process is completed successfully.
🧪 6. Test the Build
After the build is finished:
Download the generated application.
Install it on an emulator (or a physical device, if preferred).
Verify that the application launches correctly.
Navigate through the main screens to ensure everything is working as expected.
✅ Validation Checklist
Before proceeding, confirm that:
All replaced images are displayed correctly.
App name and branding are correct.
The application opens without errors.
Navigation works properly.
At least one store is displayed correctly.
No missing images, placeholders, or visual issues are present.
⚠️ Testing the application before publishing is mandatory. This helps identify branding issues, missing assets, or navigation problems before submitting the app to Google Play Store or the Apple App Store.