ParadigmJournal

Updated 2026-08-30

Why isn't there a cigar-tracking app on the iPhone App Store?

A few exist, but far fewer than the demand suggests, because a single App Store rule, Guideline 1.4.3, blocks apps that encourage tobacco consumption. Review applies it to what an app is for, not just what it says on screen, so even a plain tracking tool built for people who already smoke can read as promotional by concept alone.

What does Apple's Guideline 1.4.3 actually restrict?

It sits in the "Physical Harm" section of the App Store Review Guidelines, grouped with rules on illegal drugs and excessive alcohol. The substance of it: apps that encourage consumption of tobacco products aren't permitted on the store, and apps that facilitate buying tobacco aren't either, outside a couple of narrow, licensed exceptions. There's no separate carve-out for cigars versus cigarettes versus vapes: tobacco is tobacco to the guideline, regardless of how it's consumed or how niche the audience is.

That single sentence is doing a lot of work. It doesn't require an app to sell anything, glamorise anything, or target anyone underage to get flagged. It only requires that the app's purpose, as a reviewer reads it, be built around consuming the product.

Why does a plain tracking tool get treated the same as a promotional one?

Because the guideline is judged at the level of concept, not copy. A journal for logging what you smoked, a humidor inventory, a wishlist of cigars to try next: none of that glamorises anything, none of it sells anything, and all of it is written for someone who already smokes rather than someone deciding whether to start. But the entire premise of the app is still "cigars, and doing more of them well." To a reviewer working through a checklist, that premise is close enough to "encourages consumption" to fail the same test a promotional app would fail.

This is the part that catches most people off guard. The instinct is to assume a rejection means something in the text needs softening: remove a word, add a disclaimer, rewrite a screenshot. Sometimes that works. When the objection is aimed at the whole concept, it doesn't.

What's a "concept-level" rejection, and why can't you write your way out of it?

A wording rejection points at a specific line: a claim, an image, a missing disclosure. Fix the line, resubmit, move on. A concept-level rejection points at the app itself: what it exists to do. No amount of rewording the same concept changes what the concept is.

We went through this first-hand building a native iOS cigar journal. Across several submissions we reframed the description each time, always accurately, always describing a private record for people who already smoke rather than anything aimed at new consumers. The rejection held at the same level each time, because the object under review wasn't the paragraph, it was the app: something whose entire reason to exist was tracking cigars. Changing how that got described didn't change what it was. That's the practical signature of a concept-level call: the fix that would actually work isn't available to a developer, because it isn't a wording fix.

Does that mean no tobacco-adjacent app ever gets approved?

Not entirely. The pattern we saw, and it lines up with how the guideline is written, is that apps framed around reducing or quitting consumption have a path where apps framed around enjoying or organising it don't. A rule under "Physical Harm" is, unsurprisingly, more comfortable with an app whose stated purpose is less harm. An enthusiast tool has the opposite framing built into its premise no matter how carefully it's worded, which is why general availability of cigar-tracking apps on the store stays thin rather than absent.

Why do so many of these tools end up as websites instead?

Because a website isn't distributed through the App Store, so Guideline 1.4.3 has nothing to apply to. A page you open in Safari and add to your home screen becomes an installable web app, behaving like an app on your phone, with its own icon, working full-screen, and offline for what it caches, all without ever passing through Apple's review pipeline. That's not a workaround dressed up to look legitimate; it's a different, equally standard distribution channel that simply sits outside the one gate this particular rule controls.

It's the reason Paradigm, the tracking tool this blog sits behind, ships as an installable web app rather than a native download: a photograph identifies the cigar against an 11,519-entry catalogue, on-device, and the record (humidor, journal, wishlist) lives in the browser instead of behind App Review. For what a tracking tool needs regardless of which side of that line it sits on, see what to look for in a cigar journal or humidor tracking app; for the plainer alternative some people land on instead, spreadsheet versus app for tracking cigars covers what each one actually costs you in effort.

Is this an iPhone-only problem?

The specific rule is Apple's, but the underlying tension isn't unique to iOS. Google's Play Store carries a comparable restriction on tobacco-related apps, worded differently and enforced with its own inconsistencies in practice, but the same basic pull is there: a store that sets content policy for everything distributed through it is going to treat an app organised around a regulated product with more suspicion than a browser ever will. A web app answers to none of that, which is a structural reason, not a marketing one, that this category of tool keeps showing up as a website rather than a store listing. If you're weighing up the options, cigar tracking apps compared lays out what to expect from each format.

Native App Store app Installable web app
Subject to Guideline 1.4.3 Yes No
Approval needed before release Yes, per submission No
Update speed Review queue each time Immediate
Feature scope for a tobacco-adjacent tool Restricted to what clears review Unrestricted by store policy
Installs to home screen Yes Yes, via browser

The short version