Attendee App: Branding Requirements

This article lists every asset and piece of copy we need from you to brand a native Attendee App for iOS and Android. The same assets are used on iPad and Android tablets; each store and operating system re-lays them out for the device.

If you are your organization's IT or developer-account contact, see Attendee App: Apple App Store Access Requirementsinstead.

At a glance

Everything we need from you, in one list. Each item is explained in detail below.

Item	Limit or size	Format	Store
App full name	30 characters	Text	Both
App short name	20 characters (11–14 recommended)	Text	Both
Short description	80 characters	Text	Google Play
Promotional text (optional)	170 characters	Text	Apple
Full description	4,000 characters	Text	Both
Keywords	100 characters	Text	Apple
Privacy policy URL	—	Public web page	Both
Support URL	—	Public web page	Apple
Copyright line	—	Text	Apple
App icon	1024 × 1024 px, no transparency	PNG or JPEG	Both
Adaptive icon (optional)	1024 × 1024 px, transparent background	PNG	Google Play
Feature image	Exactly 1024 × 500 px	PNG (no transparency) or JPEG	Google Play
Splash screen	2048 × 2732 px (1150 px safe area)	PNG or JPEG	In app
App header background	1024 × 400 px	PNG or JPEG	In app
App logo	Max 520 × 200 px	PNG (transparent recommended)	In app

In this article

Before getting started
App store listing text
Store listing details
App graphics
In-app graphics
What we handle for you
Landing page

Before getting started

Send us everything at least three weeks before your launch date. Apple and Google review can take up to two weeks, and we need time to build and test first.
All listing text, graphics and theme must be final before we submit. Once a build is with the stores, nothing can change until it is approved.
After launch, updates are easy. We can resubmit the app at any time. Content inside the app (agenda, speakers and so on) updates in real time and never needs resubmitting.
Apple: the app is published from your organization's Apple Developer account. Your IT team will need to give us access; see Attendee App: Apple App Store Access Requirements.
Google Play: we publish the app through getregistered's own Google Play account. No account is needed on your side.

App store listing text

App full name (30 characters max)

The title shown on each store listing. Shorter is better; think about how attendees would search. Examples: ABC Corp Events , ABC Summit .

App short name (20 characters max; 11–14 recommended)

The name shown under the icon on the home screen. Special characters (@ , + and so on) are not allowed. Anything longer than about 14 characters is cut off by the operating system: Example Short Name becomes ExampleSho… .

Short description (Google Play, 80 characters max)

A one-line teaser shown above the full description on Google Play. Example: The official app for XYZ's annual conference.

Promotional text (Apple, 170 characters max, optional)

A short line shown at the top of the App Store page, above the full description. It can be changed at any time without resubmitting the app, so it suits date-specific messages, such as "Doors open Monday at 8am, see you there!". Plain text only: no bullets, bold, italics or line breaks.

Full description (4,000 characters max)

Shown on each store page. Describe the app's purpose, who it is for, and the features available at submission. Both stores reject descriptions that promise features the app does not have. Google Play uses this text to rank the app in search, so include the terms attendees would search for.

Keywords (Apple, 100 characters max)

Comma-separated search terms for the App Store. Don't put spaces after commas; they count towards the 100-character limit and don't help search.

Example: XYZUniversity,XYZCampusEvents,XYZStudentLife . For phrase keywords, keep spaces inside a phrase but not after the comma: XYZ University,XYZ Campus Events,XYZ Student Life .

Google Play ignores this field, so put those terms in the full description too.

Store listing details

The stores require these before they will review the app. Because the app is listed under your organization's name, they should point to your organization's pages.

Privacy policy URL

A public web page explaining how the app handles attendee data. Both Apple and Google require one, and Apple checks that the link works and matches the app's publisher. If your organization's policy does not cover event apps, talk to us before submission.

Support URL (Apple)

A public web page where attendees can get help or contact you, such as your event's contact page.

Copyright line (Apple)

The rights holder shown on the App Store page, usually the year and your organization's name. Example: 2026 XYZ Corporation .

App graphics

App icon

The icon on the home screen and store listing.

1024 × 1024 px, square
PNG or JPEG
No transparency. Apple rejects icons with a transparent background
Don't round the corners; both stores apply their own

Adaptive icon (Android, optional)

Adaptive icons let Android show the icon in different shapes (circle, squircle and so on) and add motion effects.

1024 × 1024 px, square
PNG with a transparent background, plus a background color
Keep the logo within the central two-thirds of the canvas. Android crops the edges to fit each shape, so anything near the edge can be cut off

The standard icon is used on iOS; the adaptive icon only on Android. If you use one, we need both files. Switching adaptive icons on or off takes effect only after the app is resubmitted and approved.

Feature image (Google Play)

A banner across the top of the Google Play listing. A logo or event artwork works well.

Exactly 1024 × 500 px. Google rejects any other size, even by one pixel
PNG (24-bit, no transparency) or JPEG
Keep logos and text centered, as Google may crop the image in some placements

Screenshots

No action needed. We generate store screenshots automatically from your app's theme and content.

In-app graphics

These appear inside the app rather than on the store listing. All are resized to fit each device, so design for flexibility rather than pixel-perfect placement.

Splash screen

Shown for 1–3 seconds while the app loads.

Full canvas: 2048 × 2732 px
Safe area: the central 1150 × 2732 px
PNG or JPEG

Keep logos and text inside the safe area. Extend background colors, patterns or imagery across the full canvas so nothing looks cropped on wider screens.

The image behind the header inside the app.

1024 × 400 px
PNG or JPEG
Should suit the chosen theme (light or dark)
Images without a clear focal point work best. Textures, gradients, blurred photography or abstract patterns scale better than a photo with a subject, which can end up cropped or off-center

App logo

The app or event logo shown in the header.

Max 520 px wide, 200 px high
PNG with a transparent background recommended
Leave clear space around the mark so it doesn't crowd the edge when resized
Should read clearly over the header background at small sizes

What we handle for you

The stores ask for several other things at submission. getregistered takes care of these; no action is needed from you unless we get in touch.

App Review contact: we are the contact for Apple's and Google's reviewers.
Demo login for reviewers: if attendees sign in to the app, Apple will reject it unless its reviewers can log in. We create a test attendee account for them. Your event must be set up in getregistered before we submit.
App category, age rating and data privacy questionnaires: we complete these for both stores based on how the Attendee App works.
Screenshots: generated automatically, as above.

Landing page

A short promo URL that sends attendees to the right store to download or open the app. It is useful when sharing the app outside the app stores, such as in emails or on signage. Your getregistered support team will send you the URL once both Apple and Google have approved the app.