Apple's App Store now allowing marijuana-related apps that enforce geolocation checks and rejecting apps depicting gun violence in screenshots
Context & Ripple Effects
In early 2015 Apple quietly loosened one App Store taboo while tightening another: marijuana-related apps became acceptable as long as they enforce geolocation checks, while screenshots depicting gun violence became grounds for rejection. The geolocation requirement matters because it pushes compliance work onto developers — Apple admits the category but makes each app responsible for confirming users are somewhere it is legal.
That burden-sharing approach reads differently four years later, when Google took the opposite route and moved to ban apps that sell or facilitate marijuana sales on the Play Store outright, leaving the two dominant stores with divergent rules for the same category. It also foreshadows Apple's later willingness to police how apps handle location at all, including its crackdown on apps sharing location data with third parties without explicit consent.
First-order effects
- Cannabis app developers gain an iOS distribution path they previously lacked, but only by building geofence/verification logic into their apps — Apple shifts the legal-screening cost to them rather than refusing the category.
- Any developer whose current screenshots depict gun violence faces rejection or rework at submission time, an immediate metadata-level fix rather than an app-functionality change.
Second-order effects
- With Google's Play Store later banning selling-facilitation apps, multi-platform cannabis businesses must maintain different product scopes per store — an iOS presence without parity on Android — fragmenting their distribution strategy.
- Location-verification vendors and SDK providers get pulled into App Review compliance as a dependency, since an app's acceptance hinges on third-party geolocation tooling actually working.
Third-order effects
- If the pattern holds, App Store guidelines function as a de facto regulatory layer for categories whose legality varies by jurisdiction, with platforms setting entry conditions that substitute for (or exceed) what local law requires.
- Screenshot- and presentation-level rejections normalize review criteria that reach beyond code into marketing assets, expanding what 'guideline compliance' means for every developer.
The trend: App store review guidelines are hardening into jurisdiction-sensitive gatekeeping, where platforms like Apple admit regulated categories conditionally and make developers carry the verification burden.