Attendee App Branding Requirements

This document lists every asset and piece of copy required to brand a native mobile Attendee App (iOS and Android). The same assets are used for iPad and Android tablets; the app store and OS will re-layout to match each device's screen size and hardware.

In this article

Before getting started

Submit your app at least two weeks before your target launch date so there is time for app store review.

All listing text, graphics, and theme must be finalized before submission. Once submitted, no changes can be made until the app store approves the build.

After the app is live, you can resubmit updates at any time. Content inside the app (agenda, speakers, etc.) updates in real time and does not require resubmission.

To publish the app under your own brand, you must enroll in the Apple Developer Program as an organization (requires a D-U-N-S number) and have a Google Play Console account.

Basic requirements

App store listing text

  • App full name: 30 chars max (incl. spaces). Title shown in the app stores; 15–20 chars typical.
  • App short name: 20 chars max, 11–14 recommended. Label under the home-screen icon. No special characters (@  , +  , etc.); truncates past ~14 chars.
  • Preview description (Google Play short description): 80 chars max. Google Play one-line teaser shown above the full description.
  • Promotional text (Apple only): 170 chars max. Short snippet shown above the full description on the App Store product page. Can be updated without resubmitting the app.
  • Full description: 4,000 chars max. Long-form description shown on the store page; must describe current functionality.
  • Keywords (Apple only): 100 chars max, comma-separated with no spaces between terms (Apple counts spaces as characters). Google Play derives keywords from the full description.

App graphics

  • App icon: 1024 × 1024 px, PNG or JPEG. Square. Do not round corners; the OS does that.
  • Adaptive app icon (Android): 1024 × 1024 px, PNG. Transparent background required; pair with a background color.
  • Feature/promotional image (Google Play): 1024 × 500 px exactly, PNG (24-bit, no alpha) or JPEG. Banner on the Google Play store listing. Google rejects images that are even one pixel off.

In-app graphics

  • Splash screen: 2048 × 2732 px canvas with a 1150 × 2732 px safe area, PNG or JPEG. Background fills the full canvas; keep logos and text inside the safe area to avoid cropping on wide aspect ratios.
  • App header background: 1024 × 400 px, PNG or JPEG. Sits behind the header inside the app. Resized to fit each device, so images without a distinct focal point (textures, gradients, abstract backgrounds) work best. Should complement the chosen theme.
  • App logo: max 520 × 200 px, PNG (transparent background recommended). The app/event logo displayed in the header. Resized to fit, so keep clear space around the mark so it doesn't crowd the edge.

App store listing text

App full name (30 chars max)

The title displayed on each app store listing. Shorter is better; think about how a user would search. Examples: ABC Corp Events  , ABC Summit  .

The name that appears under the icon on a device's home screen. Special characters (@  , +  , etc.) are not permitted. While 20 is the technical limit, anything longer than ~14 characters will be truncated by the OS (e.g. Example Short Name   becomes ExampleSho…  ).

Preview description / Google Play short description (80 chars max)

Google Play requires a short teaser shown above the full description. Example: The official app for XYZ's annual conference.  

Promotional text (Apple only, 170 chars max)

Apple offers an optional promotional text field that appears at the top of your App Store product page, above the long description. Unlike the description, this field can be edited at any time without resubmitting the app, which makes it useful for date-specific messaging (e.g. "Doors open Monday at 8am, see you there!"). Plain text only; no bullets, bold, italics, or line breaks.

Full description (4,000 chars max)

Shown on each store's product page. Should describe the app's purpose, the audience, and the features available at the time of submission. Include relevant keywords, because Google Play uses the description text to rank the app in search results.

Keywords (Apple only, 100 chars max)

Comma-separated keywords used by the Apple App Store. Apple recommends commas with no spaces between terms, since spaces count toward the 100-character limit and don't help discoverability.

Example: XYZUniversity,XYZCampusEvents,XYZMascot,XYZStudentLife  . If you want phrase keywords, use spaces inside a phrase but not after the comma: XYZ University,XYZ Campus Events,XYZ Mascot,XYZ Student Life  .

Google Play ignores this field, so bake those terms into the full description instead.

App graphics

App icon

The icon representing the app on the home screen.

  • Square aspect ratio
  • 1024 × 1024 px
  • PNG or JPEG
  • Do not round the corners; both stores apply their own corner radius

Adaptive app icon (Android only)

Adaptive icons let Android render the icon in different shapes (square, circle, squircle, etc.) and apply motion/visual effects when the user interacts with the home screen.

  • Square aspect ratio, 1024 × 1024 px
  • PNG with a transparent background
  • Paired with a separate background color picker

Adaptive icons are configured separately from the standard app icon. The standard icon (with its background baked in) is used on iOS; the adaptive icon is used only on Android. Apple will reject builds whose iOS icon has a transparent background, so two distinct uploads are required when adaptive icons are enabled.

Adaptive icons can be toggled on or off at any time, but the change only takes effect after the app is resubmitted and approved.

Feature image (Google Play)

Used as a banner on the Google Play store listing. A company logo or other representative artwork works well.

  • Exactly 1024 × 500 px. Google rejects any other dimensions, including off-by-one
  • PNG (24-bit, no alpha/transparency) or JPEG
  • Keep critical content (logos, text) centered, since the graphic can be cropped to narrower aspect ratios in promotional placements

Screenshots

The app stores require a minimum number of screenshots per build:

  • Apple App Store: at least 1 per supported device type (3–5 recommended)
  • Google Play: at least 2 per supported device type (up to 8 allowed)

We generate screenshots automatically from the app's theme and content.

In-app graphics

These assets appear inside the running app rather than in the app store listing. All are resized to fit each device, so design with flexibility in mind rather than pixel-perfect placement.

Splash screen

Shown briefly (1–3 seconds) while the app loads.

  • Full canvas: 2048 × 2732 px
  • Horizontal safe area: 1150 × 2732 px
  • PNG or JPEG

Keep logos and text inside the 1150 px safe area. Background colors, patterns, or imagery should extend to the full 2048 × 2732 px canvas so nothing gets cropped on wider aspect ratios.

App header background

The background image that sits behind the app header.

  • 1024 × 400 px
  • PNG or JPEG
  • Resized to fit each device's screen width and header height
  • Should help reinforce the chosen theme (light or dark)
  • Images without a distinct focal point work best. Textures, gradients, out-of-focus photography, or abstract patterns scale better than photos with a clear subject, which can get cropped or off-centered

App logo

The app/event logo shown in the header.

  • Max width: 520 px
  • Max height: 200 px
  • PNG with a transparent background recommended
  • Resized to fit the header on each device, so keep some clear space around the mark so it doesn't crowd the edge of the bounding box
  • Should read clearly on top of the header background at small sizes

Landing page

A simplified promo URL that points users to download or open the app. This page is useful when sharing access with attendees who aren't browsing an app store. The URL will be provided by your getregistered support team once apps have been approved by both Apple and Google for marketplace deployment.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us