Shipping a mobile app involves navigating a complex submission process, particularly with Google and Apple. For Google Play, developers must complete a mandatory 14-day closed testing phase with at least 12 active testers. The goal isn’t just to get downloads; Google tracks real engagement. This requirement can be a logistical nightmare, as finding people who will actively use an app daily for two weeks is more challenging than it seems. To streamline this, the author spent $15 on a service that provided real testers, highlighting the value of time in the development process. Once testing is complete, Google demands extensive documentation through a production access application. Developers must answer detailed questions about their recruitment strategies, user engagement, and feedback received. They expect concrete evidence of understanding user behavior and app quality. Apple’s process, while smoother due to tools like TestFlight, is equally rigorous in its own way. Apple emphasizes compliance with design and privacy standards over testing evidence. Both platforms aim to ensure quality apps that serve users well, but they go about it differently. The author reflects on the broader lessons learned from building and shipping the app, revealing that distribution for mobile is much more constrained compared to web products. Feature planning requires careful justification, as rolling back changes post-launch can be a lengthy process. Privacy compliance is non-negotiable, and understanding the nuances of each platform’s review philosophy can significantly impact a developer’s approach. Ultimately, knowing what not to include in an app is a vital skill, as demonstrated by the author's experience of cutting ambitious features that didn’t align with user needs.