ASO03 Aug 2026 · 6 min read · how-to

Write App Titles, Subtitles, and Descriptions

How to write App Store titles, subtitles, keyword-aware short descriptions, and Play long copy for UAE bilingual listings—fintech and marketplace examples without keyword stuffing.

Metadata is the sales script users skim before screenshots finish loading. In the UAE, that script must work in English and Arabic, respect character limits, and sound like a product people trust with money, addresses, and family orders—not a growth-hack experiment.

Character limits and roles (memorize these)

Apple App Store

Name: ~30 characters visible (stay concise).
Subtitle: ~30 characters; permanent billboard under the name.
Keyword field: 100 characters, invisible, ranking-oriented.
Description: conversion and policy clarity; weak rank signal.

Google Play

Title: up to 30 characters.
Short description: 80 characters; huge CVR lever.
Full description: up to 4000 characters; indexed—write real prose.

Always verify live console limits; platforms adjust. Design for the tightest common case.

Title formulas that fit UAE categories

Avoid Brand - Best Amazing #1 App. Prefer:

Brand + category: Lumen — UAE Digital Banking
Brand + job: Qista: Send Money Home
Brand + differentiator: Souqlet — Same-Day Dubai

For marketplaces and delivery, speed and coverage beat adjectives. For fintech, clarity and regulated tone beat hype. Never imply a banking license you do not hold.

Arabic titles

Arabic titles need native craft: character width differs, and RTL display changes what feels balanced. Do not machine-translate the English title if the Arabic brand strategy uses a different spoken name. Keep brand Latin if that is how users search; add Arabic category words when they aid discovery.

Subtitles and short descriptions

These lines answer: why install instead of the next result?

Weak: “Fast, secure, easy.” Stronger (EN examples of shape, not claims to copy blindly): “Track orders across Dubai” / “Budget in AED with goals” / “Groceries delivered tonight.”

On Play, the short description must stand alone in search ads and listing headers. Front-load the primary keyword naturally: “UAE multi-currency account for residents” reads better than “Account multi currency UAE residents best.”

Long description structure (Play-first, Apple still needs quality)

Use a scannable spine:

Opening paragraph — who it is for + primary outcome.
Proof — licenses, partner banks, cities covered, review themes (truthful).
Feature blocks — short headings + bullets.
Trust & safety — data, support hours, UAE contact norms.
Get started — what happens after install (Emirates ID KYC? guest browse?).

Write Arabic long descriptions as original marketing copy. Clunky MSA pasted from English is a conversion leak for local users who feel the product is not for them.

Fintech example pattern (structure only)

Title: brand + “UAE” or product type if space.
Subtitle: salary, savings, or transfers—pick one primary job.
Body: eligibility (residents, free-zone employees), fee transparency language, security, and support. Avoid guaranteed returns or unlicensed investment promises.

Marketplace example pattern

Title: brand + category (fashion resale, electronics, services).
Subtitle: delivery promise or trust mechanic (buyer protection) you actually offer.
Body: seller quality, return windows, payment methods common in UAE, city coverage honesty (Dubai-first is fine if true).

Keyword integration without stuffing

One primary phrase in title or subtitle—not both awkwardly.
Secondary phrases in Play body as complete sentences.
Apple unique terms reserved for keyword field.
No repeating the same word five times; algorithms and humans punish it.

Localization QA checklist

EN and AR titles approved by brand + legal (fintech)
Numerals and AED formatting consistent
No leftover US dollars or “Zip code” language
Support email/URL correct per store policy
Feature claims match current build
What’s New notes localized for major releases

Testing order

Fix factual errors and compliance risk.
Test subtitle / short description against a control (Play experiment or paid split to CPP).
Only then touch titles—title changes can reset psychological brand recognition.
Refresh long description when product narrative shifts, not weekly.

Copy anti-patterns common in GCC listings

All-caps energy and emoji spam in titles.
“#1 in UAE” without substantiation (review risk).
English description + Arabic that clearly came from an unedited MT engine.
Paragraphs about company history before the product benefit.
Keyword lists at the bottom of Play descriptions.

Collaboration model

Product marketing drafts; native Arabic copywriter revises; compliance reviews fintech claims; ASO lead packs Apple keywords; design ensures screenshot captions do not contradict metadata.

When metadata is sharp, screenshots and previews take over conversion. That is the next craft to invest in—words open the door; visuals close the install.

Side-by-side drafting method

Write English and Arabic in parallel columns, not English-first then “send to translate.” Parallel drafting forces you to notice when an English pun has no Arabic twin, or when an Arabic benefit line is stronger and should lead strategy.

Agree the single job-to-be-done for this release train.
Draft three EN title/subtitle pairs and three AR pairs.
Legal/compliance strike anything risky (fintech especially).
ASO lead checks character counts and keyword coverage.
Pick one pair per language for ship; park alternates for experiments.

Microcopy library for UAE storefronts

Maintain approved phrases for recurring ideas: fee clarity, delivery timing, eligibility (residents, free zone, business), support hours in Gulf time, security and biometrics, and payment methods you truly support. When seasonal campaigns need new subtitles, writers assemble from approved bricks plus one new tested line—faster and safer than free-form hype each time.

What’s New as an ASO surface

Release notes are underrated conversion and trust assets. Users open them when deciding to update or when sceptical after a review mention. Write What’s New in EN and AR with user benefit first, fix honesty without dumping git commits, and feature names that match in-app strings. Avoid keyword stuffing release notes; it reads desperate and rarely helps ranking meaningfully on Apple.

Voice differences by category

Fintech: calm, specific, adult. Short sentences. Numbers over adjectives. Delivery: energetic but operationally honest. Time and coverage beat cleverness. Marketplace: trade-off clarity (fees, authenticity, returns). B2B: operator vocabulary; modules; security; integration.

If your brand guidelines only cover Instagram, extend them with a one-page “store voice” addendum so freelancers stop inventing a fourth personality in App Store Connect.

QA beyond spellcheck

Read titles aloud—awkward rhythm loses trust. Check truncation on device. Verify every URL in the description. Confirm price mentions match IAP or web pricing rules for each store. Ensure Arabic digits and punctuation follow brand standard. Ship metadata with the same ceremony as a landing page hero—because that is what it is inside the store client.

Part of the Dubai Marketing Playbook by Shabang — practical marketing for UAE businesses.