Apple rejected the calendar app from Hey, an alternative email platform created by Basecamp founders Jason Fried and David Heinemeier Hansson [1].
The rejection marks a recurring conflict between the software company and Apple regarding App Store policies. This tension highlights the ongoing struggle for independent developers to bypass Apple's strict ecosystem rules while maintaining their own subscription models.
Hey launched in 2020 [1] as a tool designed to reduce email clutter and provide users with intentional control over notifications. The service costs $99 per year [1], [2]. Along with its primary email functions, the platform includes Hey World, a feature that allows users to create blogs and newsletters directly from their email [3]. James Vincent said Hey World is easy to use and lets anyone create a blog directly from their email [3].
Despite the success of its email and blogging tools, the company faced a setback on Jan. 7, 2024 [4], when Apple blocked the release of the Hey calendar app. Natasha Lomas said Apple rejected the app citing the same concerns it had with the email app four years ago [4]. The dispute centers on policy concerns that echo the earlier friction between the two companies.
Users of the service have praised the platform's approach to productivity. Megan DeMatteo said Hey changed the way she looked at her inbox [1]. However, the inability to launch the calendar app on iOS limits the platform's goal of providing a comprehensive, integrated suite of productivity tools.
Hey remains available globally via the web and native apps for Android and iOS, though the calendar functionality remains restricted on the latter due to the App Store dispute [1], [4].
“Apple rejected the calendar app citing the same concerns it had with the email app four years ago.”
The repeated friction between Basecamp and Apple underscores a broader industry conflict regarding 'walled gardens.' By rejecting the calendar app on the same grounds as the original email app, Apple is signaling a consistent enforcement of its distribution and payment policies, regardless of a developer's tenure or the popularity of their existing services.
