Wishlist 180 day restriction
Hi everyone, I’m currently planning the roadmap for my upcoming title, targeting a Q1 2027 release. I’m looking to start building my community and capturing wishlists now to ensure a strong launch, but I’ve just discovered the 180 day restriction for "Coming Soon" listings on the Horizon Store. Steam's philosophy is to get your store page up as early as possible, sometimes years in advance, to get as many wish lists as possible. This allows indie devs to funnel all social media and press traffic to a single source from day one. With the current Meta policy, I have to wait until late 2026 to even have a presence on the Store. Any hype generated now has nowhere to go on the platform, forcing me to use third-party tools (Discord/Email) which have much higher friction for users than a simple "Wishlist" button on their headset. My questions for the community and Meta team: Is the 180 days just a suggestion and really I could submit a page now? If not, what is the internal reasoning for this limit? I can see a possible issue with vaporware, but I've already sunk a lot of work into my project (which I hope shows in the screen shots and video), and I would not want to give up on it now. How are other devs handling long-term "wishlisting" when the platform itself blocks the page until 6 months before launch? I’d love to understand the strategy here, as it feels like we are losing out on a lot of early organic discovery compared to other platforms. Thanks!
Event-Based Push Notifications Not Being Received on Mobile Devices
We are experiencing inconsistent delivery of push notifications to mobile devices through the Meta Horizon app. We created an event-based push notification and it has already been approved. The notification is configured to launch a specific destination within the app when tapped. After it got approved, we used the request ID to trigger the push notification from our server to our active users, the response shows "success": true, but the delivery appears unreliable. Occasionally, the notification is successfully received on our test user account, but in most cases no push notification is delivered. The request itself appears to complete successfully, so there is no obvious indication of failure from the API response. To isolate the issue, we tested with a single test user account and manually triggered the requests multiple times. The behavior remains inconsistent—sometimes the push notification arrives, but most of the time it does not. We would like to understand: Are there any rate limits or throttling rules for sending push notifications through the Meta servers? Is there a limit on the number of users per request or the frequency of requests? Are there any recommended retry mechanisms or delivery guarantees we should implement? Are there any logs or diagnostics available to verify whether the notification was accepted and processed by Meta’s push service? Any guidance on troubleshooting or best practices for reliable push notification delivery would be greatly appreciated.
