Skip to content

Launch checklist

To be featured on the xmtp.org home page and receive amplification from XMTP's social channels, follow this checklist. Meeting these criteria helps you provide a best-in-class messaging experience with your client.

A. Follow this quality checklist

Before launching, ensure your app meets the following criteria:

Meet performance benchmarks

  • Implement a Local-first cache.
  • Cache conversation list conversations.list() to boost performance by 90%.
  • Serialize securely stored DecodedMessage histories to reduce redundant downloads and decryptions.
  • Implement message pagination.
  • Compress message content with a suitable compression algorithm.
  • Follow the testing tutorial
  • (Bonus) Implement optimistic sending.

Meet reliability benchmarks

  • No duplicate conversations should be created or displayed. If duplicates exist, only the latest conversation should be visible.
  • The app should be stable and not crash frequently.
  • No visible critical bugs.
  • Make sure to use the latest XMTP client SDK.
  • Always set an appVersion value.

Support content types

Support identity resolution

  • Offer forward and reverse identity resolution support for ENS.
  • (Bonus) Support for UNS, cb.id, .lens, Cyberconnect.

Track basic and privacy-preserving metrics

Enable your app to keep track of:

  • Number of active wallets: At least one message sent.
  • Number of active conversations: At least one message.
  • Number of returning conversations: A minimum of one message from each participant.

B. Launch your app

Way to go! 🎉 Here are some resources and ideas for promoting your app launch:

C. Keep in touch post-launch

  • Keep in touch using the XMTP Community Forums. This helps ensure that you hear about the latest SDK and content type releases, as well as upgrade and deprecation notices.
  • Contribute to the XMTP GitHub Repos: If you have code improvements, bug fixes, or features that could benefit the XMTP ecosystem, consider contributing to the XMTP GitHub repositories. By doing this, you not only improve the protocol but also gain valuable experience and recognition within the community. Make sure to follow the guidelines laid out for pull requests and XMTP Improvement Proposals.