Skip to main content

Pre-launch Checklist

Objective

Essential testing steps to ensure your PuzzleMe integration is ready for launch.

Pre-launch Testing Checklist​

Before launching your games product, carefully go through these testing steps to ensure everything works correctly. These steps are based on common issues we've encountered in practice.

1. Test Your Puzzles​

Complete at least one full game yourself to verify:

  • Puzzle layout is correct at different screen widths
  • No technical glitches or errors
  • Game mechanics work as expected
  • Game completion experience as expected

2. Mobile Device Testing​

Test how your puzzle appears on mobile devices and check for these critical issues:

Iframe Visibility Issues​

  • The entire iframe should be visible on screen
  • Users shouldn't need to scroll to access the puzzle keyboard (if present) or menu bar
  • The iframe should not have any margins or padding on the sides

Layout Problems​

  • No whitespace on either side of the iframe
  • PuzzleMe navigation bar and keyboard should span the full width
  • Any padding makes it harder for users to type as they're accustomed to

Overlap Issues​

  • Sticky menus, footers, or headers (including ad banners) should never overlap with the PuzzleMe iframe

More information on iframe sizing →

3. User Progress Persistence​

Verify that partially solved puzzles can be reloaded and continued from where you left off:

  • Progress Saving: Check that puzzle progress is saved correctly
  • Picker Information: Verify solved puzzles appear correctly in pickers
  • Streak Tracking: If enabled, ensure streak information displays properly

Technical Note: These features depend on PuzzleMe being able to re-identify users via unique user identifiers or cookies. If using JavaScript, WordPress, or Slack publishing methods, this should be handled automatically.

Troubleshooting: If users aren't being re-identified correctly, check your UIDs or verify that PuzzleMe can save cookie-based identifiers (third-party cookie restrictions may interfere).

More information on user identity →

4. Social Play Testing​

If social play is enabled, test the following:

  • Start a social play session from one device
  • Join from other devices
  • Verify both devices connect successfully
  • Test letter entry from connected devices
  • Ensure chat functionality works properly

5. Social Sharing Verification​

If social sharing is enabled, verify it works correctly:

  • Automatic Setup: JavaScript, WordPress, and Slack publishing methods handle this automatically
  • Manual Setup: For other methods, refer to our social sharing documentation

6. Print Functionality​

For puzzle types that support printing, test all print versions:

  • Blank puzzle (empty grid)
  • Solution (completed puzzle)
  • Partially filled (with user's progress)

Mobile App Integration: If embedding puzzles in mobile apps, additional setup is required for print functionality.

More information on app integration →

7. Multi-language Support​

If your puzzles are not in English, verify:

  • All messages in the puzzle solver interface are properly translated
  • Help section content is in the correct language
  • No translation problems or missing text

Report Issues: If you notice any translation problems, please contact our support team.

Testing Best Practices
  • Test on multiple devices and browsers
  • Test with different user accounts
  • Verify both desktop and mobile experiences
  • Check during different times of day to catch any time-sensitive issues
Common Issues
  • Iframe sizing problems on mobile devices
  • User progress not persisting due to cookie restrictions
  • Social features not working due to incorrect setup
  • Print functionality not working in mobile apps