Google Play Store Deployment Guide

Founders' technical manual for preparing, building, and publishing the MATCHEDIN mobile application to the Android ecosystem.

branding_watermark

App Identity

App Name

MATCHEDIN

Package Name

com.linkedup.mobile

terminal

Build & Upload Flow

Prepare Production Build

npm run build:android-release

Sign AAB (Android App Bundle)

Ensure `keystore.jks` is present in `/android/app`. Use release credentials.

Console Upload

Production > Create new release > Upload the generated .aab file.

image

Graphics Specifications

MANDATORY

Asset Type	Dimensions	Format	Context
App Icon	512 x 512 px	PNG (32-bit)	Must have 100% opacity. No rounded corners.
Feature Graphic	1024 x 500 px	JPG or PNG	Displayed at the top of your store listing.
Phone Screenshots	Min: 320px \| Max: 3840px	PNG/JPG (2:1 Ratio)	Min 2, Max 8 screenshots required.

description

Store Listing Copy

Short Description (80 chars)

The professional network for meaningful romantic connections.

Full Description (4000 chars)

MATCHEDIN is the premier networking-first dating platform designed for ambitious professionals. We go beyond the swiping culture by verifying professional identities and facilitating high-intent dates in the executive community. Join an exclusive circle of verified singles where your career trajectory and personal values align.

settings_ethernet

Environment Specs

BACKEND_URL: api.linkedup.io

FIREBASE_PKG: google-services.json

ENV: production

verified_user

App Signing

The Google Play App Signing key is managed by Google. Local signing is done via the linkedup-release-key.jks file stored in the secure vault.

security

Data Safety Form Answers

Does app collect user data? YES

Is data encrypted in transit? YES

Data deletion request provided? YES

Approximate Location collected? YES

Personal Info (Email/Name)? YES

Financial Info collected? NO