A Microsoft open-source framework for building native device applications spanning mobile, tablet, and desktop.
Hi @Kim Strasser ,
Thank you for reaching out.
The better choice in most cases is to test your game first, then publish it only when it's ready and stable.
TestFlight (for iOS) and Internal or Closed Testing (for Android) let you send the game privately to just a few people, like reviewers or YouTubers very quickly. You can update the game fast if there are problems, and no one else can see or download it yet. There is no risk of bad reviews from normal users while you fix things.
If you publish first, you have to wait for Apple or Google to check the full game (this can take days or weeks), and once it's live, anyone can download it, even if small bugs are still there. That can lead to early bad feedback and hurt your game's start.
Hope this helps. If you found my response helpful or informative, I would greatly appreciate it if you could follow this guidance provide feedback. Thank you.