App Store Review Processes and the Limits of Developer Transparency
The Apple App Store review process remains a point of contention for independent developers, yet recent events underscore the risks when creators misrepresent their submissions. On August 8, 2026, John Gruber retracted a post that had criticized Apple’s rejection of an app called “Dark Hours,” revealing that Terry Godier had provided misleading information regarding the app’s content and submission history.
The Discrepancy Between “Dark Hours” and “Asterly”
The controversy centered on claims that Apple rejected an astronomy app, “Dark Hours,” for allegedly being astrology-themed. According to the retraction published on Daring Fireball, the application submitted to Apple was actually titled “Asterly.” The app included a “Tarot card of the day” feature and other occult content, which Apple’s App Review Board cited as grounds for rejection. While the developer later removed the astrology-based features and rebranded the project, the original rejection was based on the version containing occult material, not the astronomy-focused tool eventually launched on the web.
Did you know?
The developer’s web-based version of “Dark Hours” sparked further scrutiny after it was discovered to share a name and functional bugs with an existing open-source project by Miguel Beher. The developer has since redirected his domain to Beher’s project.
Developer Responsibility and Public Discourse
This incident highlights the importance of verification in reporting on platform-developer disputes. Gruber noted that he had reviewed the story with Godier prior to publication, yet the developer failed to disclose the existence of the “Asterly” build or its occult features. This lack of transparency led to a public mischaracterization of Apple’s review standards. When developers seek public support against platform rejections, the accuracy of their claims regarding the submitted build is the primary factor in determining the validity of their grievances.
FAQ: App Store Rejections and Developer Conduct
- Why do apps get rejected for “astrology”? Apple maintains guidelines regarding app utility and content.
- How can developers ensure a fair review? Developers are expected to submit the final, intended version of their app and provide accurate metadata to the App Review team.
- What happens when an app name is already in use? As seen with the “Dark Hours” naming conflict, using a name already associated with an established project—especially open-source software—can lead to confusion.
Pro Tip:
If you are an independent developer, maintain a clear, honest record of your App Store correspondence. If an app is rejected, verify the specific build and content that triggered the decision before seeking public advocacy.
Have you encountered issues with the App Store submission process? Share your experiences in the comments below or subscribe to our newsletter for more updates on the intersection of indie development and platform policy.
Worth a look