Skip to main content

Launch checklist

Before submitting your game for review, make sure it meets the requirements below. This checklist is split into two sections:

For legal and content requirements (Acceptable Use Policy, Game Development and Publishing Agreement, and Jest Games Fund obligations), see Review and moderation.

Basic requirements​

These requirements ensure a great experience for players on the Jest platform.

Mobile web build readiness​

Your game must run smoothly in mobile browsers (primarily iOS Safari and Android Chrome).

  • Optimize initial load times to minimize player churn.
    • Targets: < 5 MB for web-native engines (Pixi, Phaser) | < 20 MB for heavier engines (Unity).
    • Assets: Load essential assets first; load the rest progressively or on-demand.
    • Engine: Minimize runtime. Unity devs: See mobile web optimization and profiling guides.
  • Remove or disable unsupported features (e.g., vibration/haptics). Native features unavailable in browsers can cause unexpected behavior or crashes.
  • Verify stability on lower-end devices after extended play (10+ minutes). Mobile browsers have strict memory limits; crashes or freezes will result in a failed review.

Platform requirements​

  • Remove all external links (e.g. links to Instagram, TikTok, "Add to Home Screen" prompts, app install banners).
  • Remove all ads and adjust any game mechanics that depend on ad revenue.
  • Remove all unsupported features (e.g. Facebook invites, vibration APIs).

User management​

  • Call getPlayer() to handle player authentication.
  • Call login() to register or log in users.
  • Make sure player progress is preserved when going from guest to registered user -- JestSDK provides a stable playerId via getPlayer() so make sure to use it to store any guest progress
  • Do not use any external user authentication system - do not prompt players to sign up with an email outside Jest, add to home screen, or download a separate app.

Jest Games Fund requirements​

Studios applying to the Jest Games Fund should meet the following criteria in addition to the basic requirements above. Proactively fulfilling these will significantly improve your application.

User acquisition​

User acquisition on Jest refers to players registering via messaging. This is a critical step because it unlocks your ability to message and re-engage users. For detailed guidance, see the User acquisition guide.

  • Support direct-to-game registrations by presenting login prompts in a compelling, contextually appropriate moment in the game flow to convert players into messaging subscribers.
  • Integrate smoothly with Jest onboarding flows (e.g. accept custom inputs such as a player name, fit naturally with the onboarding sequence via entry payloads).

Notifications​

Notifications are one of your most powerful retention tools on the Jest platform because messages are incredibly sticky. For detailed guidance, see the Notifications guide.

  • Call notification.scheduleNotification() to schedule notifications to bring players back into your game.
  • Schedule notifications as early as possible in the player session.
  • Customize notification content to personalize messages and avoid generic copy.
  • Reschedule notifications dynamically based on player progress.
  • Send a variety of notifications to avoid repetitive messaging.
  • Use fuzzy scheduling for notifications (preferred over fixed schedules). See the scheduledInDays parameter in the SDK reference.
  • Write compelling, emotionally resonant notification copy.
  • Tie notifications to a strong callback mechanic - give players a specific reason to return (a reward, an emotional hook, a meaningful in-game event), not just a generic "we miss you" message.

Virality​

Because Jest games load instantly without app store friction, leveraging virality turns the inherently social nature of messaging into a powerful distribution channel. For detailed guidance, see the Virality guide.

  • Implement outside-network virality: enable a Jest player to invite someone who is not yet on Jest (e.g. via a share link or referral mechanic).

Monetization​

  • Confirm all monetization paths work end-to-end.
  • Handle incomplete purchases gracefully - players should never be left in an inconsistent state after an interrupted transaction.