Developer posts enable you to engage and grow your community by providing content such as text and images that are displayed on your application’s product detail page (PDP). You can use posts to highlight promotions, announce new content, and share updates about your app with users. Posts are visible on the Meta Horizon Store, your app’s PDP, and the Meta Horizon mobile app.

Age-based feature limitations

When developing your apps, consider the following limitations related to age:

Child users under 13 (10-12 year olds): Regardless of your app’s self-certification status, child users under 13 cannot access this Platform SDK feature. Implement error-handling for this unsupported feature to maintain a safe and pleasant experience for child users.

Developer posts in the Meta Horizon mobile app

Developer posts appear on your application’s product detail page (PDP) in the Meta Horizon mobile app once a user selects your game or app.

The following image shows a developer post in the Meta Horizon mobile app.

The following image shows the detail page when users click on a post in the Meta Horizon mobile app.

Example Developer Post in Mobile App Details

Create a developer post

To create a developer post, follow these steps.

In the Developer Dashboard⁠, select your app.

In the left-side navigation, click Engagement > Posts.

On the Posts page, click Create Post.

For each post, you must provide:

Title: A short title for the post.

Description: A description for the post. You can use markdown to format your description, as well as upload images to be embedded anywhere within your description. Embedded images must be in 16:9 aspect ratio and a 2560 x 1440 24-bit .png file.

Don’t Show This Post Until: The time you would like your post to start displaying.

You can optionally provide:

Image: This should be different than your app cover art. It should reflect the content of your post. It must be in 16:9 aspect ratio and a 2560 x 1440 24-bit .png file. If it does not meet these requirements, your image will be rejected.

Stop Showing This Post After: The time you would like your post to stop displaying.

Deeplink Message: Provide a deep link message that indicates the app will launch the user directly into a new level or experience that you are promoting with the post. For more information about implementing deep links, see the engine-specific documentation listed in Related links.

Click Save Changes to preview your post before you submit, or Submit for review when you are ready to have your post reviewed.

Comments

You can enable comments on your developer posts to allow users to interact with your content. Comments provide a direct channel for user feedback and community engagement.

How comments work

Toggle comments: You can enable or disable comments on each post at creation time, or toggle them on or off after the post has been published.

Flat-thread model: Comments are top-level only. Users cannot reply to each other’s comments in nested threads.

Developer replies: You can reply to user comments from the Developer Dashboard. Replies appear under your Builder Profile identity, not an individual team member’s profile. You can post one reply per comment.

Character limit: Each comment is limited to 140 characters.

Platform availability for comments

Full interactivity (read, write, reply): Meta Horizon mobile app and meta.com

View-only: Meta Quest headset

Reporting

Users can report inappropriate comments for policy violations.

Moderation tools

You have several tools available to manage comments on your posts from the Developer Dashboard:

Hide: Make a comment invisible to all users except the original commenter.

Delete: Permanently remove a comment. If the comment has a developer reply, the reply is also removed.

Block: Prevent a specific user from commenting on your future posts.

Report: Report a user for policy violations.

Automatic moderation

A comment that is reported by 10 different users is automatically hidden from everyone except the original commenter.

If a parent comment is hidden or deleted, any developer reply to it also becomes invisible.

Merchandising shelves

You can attach purchasable items to your developer posts, allowing users to discover and buy content directly from your announcements.

Supported item types

You can attach the following types of items to a post:

Add-on content (IAP/DLC)

Bundles

Other released apps from your organization

You can select more than one item per post and mix different item types.

Requirements

All attached items must be released. Unreleased items are not eligible.

Items must belong to your app or your organization.

Fallback behavior

If an item is ineligible for a particular user (for example, the user has already purchased the item, or the item is geo-restricted or age-restricted), the post falls back to the standard install or launch call-to-action (CTA) for that user.

Platform availability for merchandising shelves

Merchandising shelves are available on:

Meta Quest headset

Meta Horizon mobile app

Meta Horizon Store

Preview a post

It is useful to see how the content will appear on the headset before you submit it for review. To preview the post, do the following:

Create a post and select Save Changes.

Navigate back to the Posts page under Engagement.

Click the link under the View column. The preview of the post will appear.

(Optional) If you’ve chosen to integrate deep links, you can click through your post to launch your app and test the deep link.

When you’re satisfied with the post and deep link, you can submit the post for review and public release.

Content review

All developer posts are reviewed by the Meta team to ensure that they meet the Meta Quest Content Guidelines and adhere to the Code of Conduct for Virtual Experiences⁠. Once you submit your post, it will be evaluated by the Meta Quest team and the status will change to Approved or Rejected when the evaluation is complete.