Reddit Community Analysis: r/iOSProgramming

1. Data Sources & Methodology

• 309 unique posts after deduplication across 4 time periods (all-time, year, month, week), 4 pages each (15 raw JSON files; top_week only produced 3 pages because the week has fewer than 400 posts).
• Per-period breakdown
  • top_all — 100 posts, score range 369–1017, median 459
  • top_year — 100 posts, score range 149–1017, median 222
  • top_month — 100 posts, score range 3–613, median 14
  • top_week — 56 posts, score range 0–112, median 3
• Overlap: 18 posts appear in both all + year; 22 in both month + week; only 1 post ("I just saw this and I HAD to share!" at 1017) appears in all + year + month. The near-zero overlap between the all-time leaderboard and the last 30 days is the single most important quantitative fact about this subreddit — see Section 2.
• Date collected: 2026-04-10
• Subreddit subscribers: 192,409 (created 2010-11-01)
• Score range & median (full dataset): 0 to 1,017; median 189
• Top-25 threshold: 596; top-50 threshold: 459; top-100 threshold: 369
• Cross-subreddit score calibration (using other analyses in this directory):
  • r/ClaudeAI peaks ~8,000 (the viral AI tier)
  • r/programming peaks ~4,500
  • r/IndieDev peaks ~3,500
  • r/iOSProgramming peaks ~1,000 (4 posts in the entire all-time top 100 clear 900)
  • r/macapps peaks ~2,000
  • So iOSProgramming is a mid-sized, low-ceiling dev community. A 300-point post is already comfortably in the top 100 of all time. If you are expecting 3,000+ upvotes on a tool launch, you are in the wrong subreddit.

Scope: this is a content-strategy and distribution guide for someone who wants to launch, promote, or build reputation through r/iOSProgramming. It is not a sociological study of Apple developers.

2. Subreddit Character

r/iOSProgramming is a dev-craft community with a once-a-year sanctioned commercial window and an unusually strong memetic/meme-image culture for a programming subreddit. It is not a product launch platform (that is r/macapps and r/SideProject); it is a place where iOS developers come to vent about Xcode, argue about SwiftUI vs. UIKit, celebrate milestones, and — on Saturdays — briefly tolerate each other's apps.

The top of the leaderboard is dominated by humor. 14 of the top 25 posts (56%) are Humor-flaired image macros. The #1 all-time post is literally titled "I just saw this and I HAD to share!" (1017, 0.98 ratio). The jokes are almost always about the same 3 targets: Xcode instability ("Every Day with Xcode" 958, "Xcode's best feature to this day" 667, "Whoa, Xcode, you good?" 493), SwiftUI-vs-UIKit confusion ("UIKit vs. SwiftUI" 704, "Certified SwiftUI Moment" 694, "WTF?? UIKit is being deprecated in 2026" 735), and Apple's opaque review process / developer experience ("App Review be like" 459, "How it feels talking to the Apple Review Team" 149). If a meme doesn't target one of those three, it struggles.

Commercial content is rule-gated, not culturally welcome. Rule 7 is the single most important rule to understand: "You may post about one app, once a year. Only on Saturday." The App Saturday flair is not a suggestion — it is mod-enforced. u/HumbleRevolter states explicitly in the #11 all-time post that his earlier version was removed and he had to repost on Saturday. This is why the App Saturday flair has only 16 posts in the entire 309-post dataset despite covering all 4 time periods — most app posts get removed. When you do post on Saturday, you compete in a small field, and the ceiling is real (top App Saturday post is 754, median 202).

The community is skeptical of self-promotion, skeptical of AI-slop, and allergic to "I made $X" posts that don't include vulnerability or technical substance. "Made $35K in sales" (976, #3 all-time) works because it's an AMA with 404 comments and the author openly discusses his health issues, ASO tactics, and exact costs. "How to create mobile apps that make $3,000 a day" (625) works because the author immediately pivots into "...and then Apple removed all my apps and blocked my account" — schadenfreude and solidarity. Compare: "My First App made w SwiftUI" under the ironic "Roast my code" flair hits 441 because the author is asking for criticism, not praise.

Cultural values, ranked:

1. Xcode-as-shared-suffering (universal bonding topic; rants reliably score 200-500)
2. Craft over grind ("Please learn to love programming again. I'm begging you." 613 — top text post)
3. Indie realism over hustle-culture ("The road to $1K/MRR is not immediate, nor glamorous" 186 > "Hit 2k USD" 276)
4. Anti-subscription maximalism ("From now on I'm going to downvote every single app promotion, especially tracking-for-subscription apps" 500, ratio 0.89 — net positive)
5. Anti-vibe-coding / anti-AI-slop ("AI coding is fucking trash and exhausting." 273, ratio 0.89; "Apple steps up crackdown on vibe coding apps" 180)
6. Suspicion of cross-platform / React Native ("Perils of being a Cross-platform Dev" 964; "Why you should start with UIKit" 55, ratio 0.73 controversial)

Enforcement mechanisms: (a) Rule 7 App Saturday hard limit — see above. (b) MISLEADING TITLE flair appears as a mod-applied scarlet letter (one post, ratio 0.62). (c) Community self-policing on self-promotion: users actively call out astroturfing in comments and post "Anti-promotion" threads (Rule 4 is deliberately vague — "self-promotion is allowed to some extent" — which empowers community enforcement). (d) Rule 5 bans job ads, requests, and app ideas — this is routed to the Discord. (e) The sidebar FAQ is explicit that "Swift vs. Objective-C" posts will be removed.

How this differs from adjacent subs: r/swift is more technical and code-focused. r/iOSProgramming is more culture-plus-complaint. r/macapps is a launch platform (ceiling ~2000, products welcome). r/IndieDev and r/SideProject tolerate launch posts freely. r/iOSProgramming tolerates them for 24 hours a week, under one flair, once a year per author.

3. The All-Time Leaderboard

Median score across the full 309-post dataset: 189. Top-25 threshold: 596.

Observations:

• 20 of 25 are IMAGE (80%). Only 2 videos and 3 text posts. This is a meme-image economy.
• 14 of 25 are Humor-flaired. The second-most-common flair in the top 25 is App Saturday (3). Question has 0 entries in the top 25.
• The #2 post ("This has almost 30k upvotes in another sub…hm") is ironic/meta — the joke is that the post is complaining about karma farming while being a karma farm. The community loves this kind of wink.
• No flair is used ironically in the top 25, but lower down: Roast my code on "My First App made w SwiftUI" (441) is used earnestly as self-deprecation; Question on "AI induced psychosis is a real thing." (583) is used ironically — it's a statement post wearing a question mask.

4. Content Type Dominance at Scale

Three surprising findings:

1. Humor is the only flair with real upside. Its average score (460) is 2.2x the community-wide median of 189. Every other flair has an avg score below 500. If your goal is reach, humor is not just one option — it is the option.

2. Question has 54 posts (18% of the dataset) but an avg score of 42 — less than a quarter of the median. Questions get answers and discussions, not upvotes. This is a classic high-comments/low-score flair. Useful for relationships (see Section 9), useless for visibility.

3. Tutorial and Library are the WORST performing flairs, with avg ratios of 0.74 and 0.82 respectively. The community treats tutorial and library posts as thinly-veiled self-promotion unless they are exceptional. Tutorial has the lowest average ratio of any flair — people actively downvote tutorial posts. Do not use Tutorial to promote anything.

5. Content Archetypes That Work

Seven archetypes emerge from the data, ranked by score ceiling:

Archetype 1: The Xcode Pain Meme

Score range: 253–958 (8+ posts above 400) Examples: "Every Day with Xcode" (958), "Xcode's best feature to this day" (667), "Do you even simulator?" (643), "Whoa, Xcode, you good?" (493), "My face after deleting 90 GB of Xcode caches" (416), "Xcode is great except when it isn't" (374), "My favorite little game xcode plays with us" (175).

The pattern: A single image — screenshot, photo, or simple graphic — that captures a specific Xcode-induced frustration every iOS developer has felt. The more specific the frustration (simulator freezing, derived-data disk bloat, autocomplete suggesting C constants), the better. Zero selftext required. Pure communal suffering + recognition.

Why it matters for distribution: You can pre-build reputation here. Post 2–3 Xcode memes before you ever try to launch anything. Your account will be associated with community-insider voice, which reduces the "who is this guy" friction when you later post under App Saturday.

Archetype 2: The SwiftUI-vs-UIKit Holy War Meme

Score range: 439–735 Examples: "WTF?? UIKit is being deprecated in 2026" (735, intentionally false to provoke), "UIKit vs. SwiftUI" (704), "Certified SwiftUI Moment" (694), "Inb4 job requirements asking for 5 years of iPadOS and SwiftUI experience" (404).

The pattern: An image that stages the UIKit-vs-SwiftUI tension without explicitly taking a side. The audience splits and both factions upvote the meme and argue in comments. Note: text-form takes on this topic are much riskier — "SwiftUI was a mistake — and I've been using it since beta 1" (417, ratio 0.88, 203 comments) performed but with friction. "Xcode is actually a great IDE." (512, ratio 0.85, 260 comments) also performed but with friction. Memes dodge the friction.

Why it matters: This is the safest "take a stance" archetype. You cannot easily use it for launches, but it builds comments-in-your-DMs relationships with senior devs — who are your best beta testers.

Archetype 3: The Vulnerable Milestone AMA

Score range: 186–976 Examples: "Made $35K in sales over the past 30 days as an indie dev… AMA" (976), "I got a $400K+ offer… and then Rounds.com emailed me" (542), "Just got my first payment from @AppStore" (754), "Got my first Apple payout!" (389), "Hit 2k USD in proceeds" (276), "Just earned my first $100 from my apps" (319), "Just reached €100 MRR after 4 years" (201), "The road to $1K/MRR is not immediate, nor glamorous" (186).

The pattern: Revenue is disclosed, but always paired with either (a) a hardship disclosure (health issues, years of failure, 4 years to €100 MRR), (b) a caveat (first-ever payout, first $100, tiny amount), or (c) an antagonist (Rounds.com scam, Apple freezing the account). Pure bragging tanks — the community demands a vulnerability tax on every revenue claim. "Made $35K" includes: "I have severe health issues", "I live alone", "I won't share links", "API costs $150/month". That combination is what separates 976 from zero.

Why it matters for distribution: The single most powerful way to promote an app on this subreddit is to post your first payout, not your app. Announce the milestone, not the product. Share the number. Share the timeline. Share what went wrong. The app link goes in a comment, not in the title. This archetype is the closest thing iOSProgramming has to a "sanctioned launch vehicle" outside App Saturday.

Archetype 4: The App Saturday "I Built This For Myself" Post

Score range: 0–754 (median App Saturday: 202) Examples: "Shipped an App! Meet Schema - Postgres/MySQL client" (626), "Built my first app! A clock that uses metal shaders" (386), "I built an app to manage my app projects" (371), "I'm building an app to stop me doomscrolling" (589), "I Built a Virtual Pet App for Tracking Alcohol Free Days" (206).

The pattern: Saturday posting, App Saturday flair, IMAGE or GALLERY format, framing is "I made this for myself and it helped / amused me — maybe it'll help you too". The hook is personal utility, not market opportunity. Never frame the post as a business launch. Never mention ASO, pricing tiers, or revenue models in the opening paragraph. The Schema post (626) opens with "Like many of you, I build things regularly and often find myself wishing for X. So... I'm shipping one." That is the template.

Why it matters: This is the one legitimate commercial archetype. See Section 11 for the full App Saturday launch playbook.

Archetype 5: The Craft/Sincerity Text Essay

Score range: 186–698 Examples: "From 'Hello World' To Your First Job: Self-Taught iOS Roadmap" (698, 0.99 ratio), "Please learn to love programming again. I'm begging you." (613), "After many years of prison I was released, learn to program, and was hired" (369), "In December 2019 I got fired… February 2021 I got offered a job as a Junior iOS Developer" (401), "Senior iOS dev by day, indie developer by night" (154), "A hard truth from years of indie Apple dev" (418).

The pattern: Long-form (usually 1500+ words), zero-promotion, zero-link, written from earned experience, sincerity dialed to 10. The top-ranking example is a 4000-word beginner's guide with free resources and no call-to-action. These posts are comment magnets (78, 142, 164 comments) and establish authority that carries across future posts from the same account.

Why it matters for distribution: If you are trying to build reputation for a future launch, one well-written essay of this type will do more than five product posts. The author of the Hello World Roadmap (u/NothingButBadIdeas) is universally cited in community FAQ lists. Earn that status first.

Archetype 6: The SwiftUI Animation Showreel Video

Score range: 376–921 Examples: "AR animated iPhone box made with SwiftUI, ARKit 4, RealityKit" (921, no flair), "Animated Pokédex app created with SwiftUI" (625), "I made this elegant SwiftUI timeline" (509), "Drinks ordering app created with SwiftUI and UIKit" (504), "Animated Circular Download Button" (484), "It's amazing how much of a difference a skeleton loader can make" (458), "Exploring drag and drop delegates in SwiftUI" (391).

The pattern: A 10–30 second video (or gallery) of a single polished UI interaction, usually demonstrating a custom animation, drag-and-drop, transition, or effect. Title is descriptive ("X made with Y"). Source code is typically linked in a top comment. These posts have extraordinary ratios (0.94–1.00) and very low downvote counts.

Why it matters: If your product has any visually impressive UI component, rip a 15-second clip of just that component and post it as a standalone. Do not frame it as a launch. Frame it as "I built this, here's how". Reserve the full product launch for Saturday.

Archetype 7: The Apple Villain Story

Score range: 180–625 Examples: "How to create mobile apps that make $3,000 a day" (625 — actually a story about Apple closing the author's account), "I got a $400K+ offer to buy my app, and then Rounds.com emailed me" (542), "Taking on Apple in Court: Their mistake wiped out our $33,680 MRR" (373), "Apple steps up crackdown on vibe coding apps" (180).

The pattern: The author is the victim, Apple (or a predatory third party) is the antagonist. These posts work because they channel the community's universal frustration with the opaque review process, arbitrary rejections, and account terminations. They reliably cross 300+ upvotes and generate 100+ comments of solidarity.

Why it matters for distribution: You should not fabricate antagonist stories, but if you have a legitimately bad App Store experience (5+ rejections, guideline 4.3 spam flag, IAP review mistakes), write it up as a structured post-mortem with checklist. "Got rejected 5 times before getting approved. Here is what I learned." (54) was a small post but this archetype scales to 500+ when the stakes are high.

No giveaway archetype exists. Only 2 posts in the entire 309-post dataset use [FREE], [FREE TRIAL], or Giveaway framing, and neither clears 200 points. The rate-limited App Saturday rule makes traditional code-giveaway mechanics structurally impossible. Do not plan a giveaway-driven launch on this subreddit.

6. Format Analysis

Key facts:

• Visual content dominates the top: 88% of the top 25 and 86% of the top 50 are IMAGE or VIDEO. TEXT accounts for 38% of all posts but only 12% of the top 25.
• GALLERY is the surprising zero — 15 gallery posts in the dataset, none in the top 25, best at 386. Galleries appear useful for App Saturday screenshot sets but do not chart the top.
• LINK posts are a promotional red flag: 24 total, none in the top 25, and they average below 200 points. Hosting the content on Reddit (as a TEXT post or IMAGE) massively outperforms linking to an external blog.
• GIF = 0. The community uses static IMAGE memes, not animated GIFs. This is slightly unusual for a meme-heavy sub.

What Format to Use For What

What Makes a Good Demo Video (derived from the 22 video posts in the dataset)

1. Short. Every video in the top 10 videos is under 30 seconds. Most are 10–15 seconds. No one watches 2-minute walkthroughs.
2. Silent / screen-recorded, not talking-head. Zero of the top-performing videos feature the developer on camera. They are all QuickTime screen captures of the simulator or a real device.
3. Show the effect, not the feature list. The Pokédex (625), timeline (509), drag-and-drop (391), and download button (484) posts each show ONE interaction — not a whole app tour.
4. Source in top comment. Multiple top video posts note "Github repo in comments" — this is an unwritten rule. Posters who link out in the title underperform vs. posters who stash the link in a self-comment.
5. Descriptive, craft-forward titles. "X created with Y" format. No hype words, no "check this out", no emojis.

Gallery sizing

The 15 gallery posts average 3–6 images. "Just got my apple developer account terminated" (189) is 4 images. "I built an iOS app to clean up my photo library" (206) is 5 images. Stick to 3–6 — more dilutes the feed.

7. Flair/Category Strategy

Raw performance ranking

1. (none) — avg 528 (n=7). Highest avg but tiny sample; the posts that work here are unflaired because they predate the flair system or are SwiftUI animation videos.
2. Humor — avg 460 (n=55). The workhorse of the top tier.
3. Application — avg 440 (n=13). Works for SwiftUI animation videos specifically, not for full app launches.
4. Roast my code — avg 296 (n=2). Too small to generalize, but consistent.
5. App Saturday — avg 289 (n=16). Correct flair for launches. Median 202.
6. Solved! — avg 230 (n=4). Tiny sample.
7. Article — avg 206 (n=21). Works for long-form essays, fails for link-outs.
8. Discussion — avg 206 (n=106). The default. Very wide spread.
9. News — avg 182 (n=12).
10. Library — avg 46 (n=9). Self-promo flag.
11. Question — avg 42 (n=54). Good for discussion, bad for upvotes.
12. Tutorial — avg 38 (n=8). Worst performer. Avoid.

Distribution utility ranking (different!)

1. App Saturday — The only legitimate commercial vehicle. Rule-enforced once per year per author, so use it carefully. Median 202 with a 754 ceiling is excellent relative to the 1017 all-time peak.
2. Discussion — The stealth launch flair. 106 posts means nobody can accuse you of gaming anything. Milestone AMAs and vulnerable revenue posts go here, not under App Saturday.
3. Humor — Reputation-building flair. Do not attempt to promote anything under humor; use it to earn community standing.
4. Article — Use for genuine post-mortems, roadmaps, and craft essays. Never for disguised blog promotion.
5. Roast my code — Surprisingly useful if your product is open-source. Self-deprecation as distribution.
6. Question — Low visibility but high discussion. A well-crafted Question post gets you 50+ developer conversations, some of which will DM you. This is where you find beta testers, not upvotes.
7. Application — Only use if you have a single genuinely impressive UI demo.
8. Library — Avoid. Signals self-promotion and scores poorly.
9. Tutorial — Avoid. Only Tutorial post in the top 50 is "Just learned you can show App Store banner on your website" (193).

Title-prefix tags

Almost unused. Only 4 posts in the entire dataset use [BRACKET] title prefixes, and only one ([FREE TRIAL] at 200) scores notably. Do not use [OS], [FREE], [Giveaway], [Updated] prefixes — they signal promotional intent in a sub that is suspicious of promotion.

Pricing-model hierarchy (from community reaction signals)

1. Free, open-source — universally acceptable. Best ratios.
2. Free + lifetime IAP — well received.
3. Free + one-time unlock — acceptable, common in Schema-style launches.
4. Free trial → subscription — tolerated but explicitly called out in "I'm going to downvote every single tracking-subscription app" (500, 0.89 ratio). Stating pricing up front helps.
5. Paywall-first subscription — hostile territory. The 613-upvote essay ("Please learn to love programming again") is literally an anti-subscription rant. Expect friction.
6. Ad-supported — barely represented in the dataset. Unknown reception.

8. Title Engineering

Deconstruction of the top 10 titles

Six title formulas from the dataset

1. "First [X]" humble milestone: "Just got my first payment" (754), "Got my first Apple payout!" (389), "Just earned my first $100" (319), "I made it! Just got my first app approved" (304). The word "first" is a credibility-lowering humility signal.

2. Specific-number AMA: "Made $35K" (976), "Hit 2k USD in proceeds" (276), "Just reached €100 MRR after 4 years" (201). Always include the exact number. Never round.

3. Universal-frustration noun phrase: "Every Day with Xcode" (958), "Do you even simulator?" (643), "Being a iOS developer is not easy" (597), "Xcode's best feature to this day" (667). 3–6 words, no punctuation clutter.

4. Tribal-identity "Perils of being": "Perils of being a Cross-platform Dev" (964), "Solo developer life" (172), "Senior iOS dev by day, indie developer by night" (154).

5. SwiftUI/UIKit debate bait: "UIKit vs. SwiftUI" (704), "Certified SwiftUI Moment" (694), "WTF?? UIKit is being deprecated in 2026" (735). The format is: faction name + emotional word + implied controversy.

6. Stack-list craft title (for videos): "X made with SwiftUI", "X created with SwiftUI and UIKit", "AR animated iPhone box made with SwiftUI, ARKit 4, RealityKit". List the frameworks. This signals "craft content, not promotion".

Community-specific title anti-patterns (all with evidence)

1. "How to make $X/day" as a pure promotional hook — "How to create mobile apps that make $3,000 a day" scored 625 only because the selftext was about Apple banning the author. Without that pivot, this title reads as scam-bait. Do not use it without a vulnerability anchor.

2. Tutorial framing without specificity — "Offline Storage with SwiftData" (0, ratio 0.33), "A Swift package for chat with your data" (0, ratio 0.40), "Spec-Driven Development with OpenSec" (0, ratio 0.33). Generic topic + link = dead on arrival.

3. "Built X with Y" as a tutorial pretext — "Building List replacement in SwiftUI" (12), "How to Clear Xcode Derived Data" (7, ratio 0.67). The community reads these as blog-drive posts.

4. Bracket tags — Only [FREE TRIAL] and [Book] appear at all. No post with a bracket tag clears 200. The community does not use this convention.

5. Star counts, download numbers, growth metrics as vanity flexes — zero posts in the top 100 lead with "1000 GitHub stars", "100k downloads", or "1000% growth". The community is allergic to these. Use revenue-with-hardship instead.

6. React Native / Flutter / cross-platform framing — "Swift vs. React Native: After scaling 2 apps…using only AI" (0, ratio 0.43). Native-only subreddit; cross-platform content is hostile territory.

7. Vague emotional confession titles — "That gut-wrenching feeling" (0, ratio 0.39). No content hook; reads as attention-seeking.

9. Engagement Patterns

Comments-per-upvote by flair (all-time)

Comments-per-upvote by format

Conditional recommendation:

• If your goal is VISIBILITY, post an IMAGE under Humor or an App Saturday hero-screenshot. Expect 300–900 upvotes, 30–80 comments.
• If your goal is DISCUSSION and RELATIONSHIPS, post a TEXT under Discussion or Question. Expect 50–200 upvotes but 100–400 comments. This is where you find beta testers and collaborators.
• If your goal is AUTHORITY, post a 1500+ word TEXT under Article or Discussion with zero links. Expect 200–700 upvotes AND 100+ comments AND a followable author badge.

Highest-discussion topics (regardless of score)

1. Xcode quality / Xcode rants — Xcode 15 is a Joke (349 comments), Xcode is actually a great IDE (260), XCode rant, sorry (172), No one wants to admit Xcode is a buggy pile (123). The single most-discussable topic in the sub.
2. AI coding / vibe coding — AI coding is fucking trash (195), AI induced psychosis is a real thing (121 via image), After scaling 2 apps using AI (75).
3. Apple review rejections — Even Elon Musk complained (155), Cannot install app, Unable to verify (273), How do you deal with 1 star reviews (81).
4. Indie revenue honesty — $35K AMA (404), A hard truth from years of indie Apple dev (164), I've been an iOS dev for 5 years and I'm starting to regret it (240).
5. SwiftUI vs UIKit framework debates — SwiftUI was a mistake (203), Why you should start with UIKit (46).

10. What Gets Downvoted

Ratio tiers

• Above 0.94 (safe): 182 posts (59%)
• 0.85–0.94 (friction — net positive but debated): 67 posts (22%)
• Below 0.85 (controversial / hostile): 60 posts (19%)

Most-downvoted posts worth studying

Seven community-specific anti-patterns

1. The Google-able Question ("Is there any way to remove the black corners in simulator" — ratio 0.60). Any question that can be answered by reading the Xcode docs is routed to Discord by the sidebar and draws downvotes.

2. The Defensive Launch Qualifier ("(0 AI Code) I built a cozy daily tracker" — ratio 0.52). Prefixing your post with (0 AI Code) or (Not AI) reads as guilty. The community can smell defensiveness. If you are asked, answer in comments; never pre-empt in the title.

3. The Blog-Drive Tutorial ("Offline Storage with SwiftData" — ratio 0.33). Link posts with tutorial titles that point to Medium/personal blog are interpreted as SEO content and downvoted.

4. Cross-Platform Advocacy ("Swift vs. React Native…using only AI" — ratio 0.43). Advocating React Native, Flutter, or Kotlin Multiplatform is near-tabooed. Native-only audience.

5. The Contrarian Framework Take ("Why you should start with UIKit for your new app" — ratio 0.73, "SwiftUI was a mistake" — ratio 0.88). Contrarian takes are tolerated only with deep credibility. If you have fewer than 5 years of Apple dev experience, this post is not for you.

6. The Xcode Defense ("Xcode is actually a great IDE" — ratio 0.85). Defending Xcode is contrarian in this community. Even though the post scored 512, the ratio penalty is real.

7. The Sidebar-FAQ Question ("How do devs make their app compatible with very old iOS versions" — ratio 0.60). The sidebar explicitly calls out repeat beginner topics. Read the sidebar, read the FAQ wiki, then post.

No public blacklist or hall of shame exists

Unlike r/macapps, r/iOSProgramming does not maintain a public list of banned promoters. Enforcement is done via (a) Rule 7 timing limits, (b) the MISLEADING TITLE mod-applied flair, and (c) comment-section self-policing. Ban risk is lower than r/macapps but post-removal risk is higher — mods will delete violating App Saturday posts without warning, as the #11 author notes ("I posted similar post before but it was taken down due to not being Saturday").

11. The Distribution Playbook

Phase 1: Pre-launch (2–8 weeks before posting)

1. Read Rule 7. Memorize it. "One app, one post, once per year, on Saturday." This is the only way to use App Saturday, and you get exactly one shot per calendar year.
2. Read the sidebar FAQ. Bookmark the linked GitHub FAQ. Any question already answered there will be removed.
3. Build karma and presence with 2–3 humor posts or craft-video posts. Use Archetype 1 (Xcode Pain Meme) or Archetype 6 (SwiftUI Animation Showreel) to establish an account history without spending your App Saturday slot. 2 successful posts in the 300–500 range will make your App Saturday post land on a warm rather than cold audience.
4. Comment, specifically on Xcode-rant and indie-revenue threads. The authors of "$35K AMA" and "A hard truth from indie Apple dev" are your future allies. Leave substantive comments on their posts. Do not pitch in DMs.
5. Write your launch post body in a draft. Target 150–400 words. Open with personal utility ("I built this for myself because…"). Include at least one hardship admission.
6. Prepare 3–5 hero screenshots. Native screenshots from the simulator, no mockup frames. The Schema post (626) and the Project Planner post (371) both use single high-quality screenshots, not glossy marketing mockups.

Phase 2: Launch day — specifically, Saturday, 13:00–17:00 UTC

1. Wait for a Saturday. Do not attempt to launch on any other day. Confirm the current day is Saturday in UTC terms, not your local time, before hitting post. The top App Saturday posts were created early-to-mid Saturday UTC.
2. Use the App Saturday flair. This is non-negotiable under Rule 7.
3. Title formula: Either "First X" humble milestone (if you have one — the 754 post used "Just got my first payment from @AppStore… kinda surreal.") OR "Shipped an App! Meet X — Y for Z" (the 626 post used "Shipped an App! Meet Schema - A MySQL and PostgreSQL database client for iOS."). Avoid superlatives, no all-caps, no emojis in the title beyond an occasional 👀 or 🥲.
4. Format: single IMAGE of your hero screenshot, or GALLERY of 3–5 screenshots. Not a video. Videos are for UI-demo standalone posts, not for launches.
5. Body copy structure (Schema template): (a) one-sentence product description, (b) "like many of you" inclusion hook, (c) one-line origin story, (d) App Store link on its own line, (e) offer to answer questions. No pricing in the body. No feature list. No founder story.
6. Post time: Early Saturday UTC. Avoid posting on Friday night local time thinking you'll catch Saturday traffic — you will be removed.

Phase 3: First 24–48 hours

1. Reply to every comment in the first 4 hours. This is the active window. Comments-per-upvote is your success signal — aim for a C/U ratio above 0.10 in the first 2 hours.
2. Do not argue about pricing. If someone complains about a subscription, respond with your reasoning once and move on. Argumentative replies tank ratio.
3. Do not post the App Store link in the title. Put it in the body or a top comment. Keeping the title clean of links reduces the "this is an ad" reflex.
4. If someone asks "is this vibe-coded?" or "is this built with AI?" — answer truthfully and immediately. A confident "Yes, roughly 40% AI-assisted, and here's how I kept architecture consistent" is fine. Dodging the question is not. See the 48-point post "How I got an AI coding agent to actually respect our iOS architecture" — a pro-AI post can work if it's specific and technical.
5. Threshold check at 4 hours: If you're below 30 upvotes and ratio below 0.90, the post will not recover. Do not delete. Do not repost. You have used your annual slot.
6. Threshold check at 24 hours: 100+ upvotes and ratio 0.94+ means you're a successful launch. 200+ is top-10% for App Saturday. 400+ is top of the flair.

Phase 4: Ongoing presence (post-launch, year-round)

1. You cannot post about the same app again for 365 days. Plan accordingly.
2. You can still benefit from the launch by (a) posting a milestone update as a Discussion post 3–6 months later — Archetype 3, the Vulnerable Milestone AMA — framed around revenue or a hardship pivot, not the product, (b) posting a technical deep-dive as an Article (Archetype 5) about a specific challenge you solved, or (c) posting a UI animation video (Archetype 6) of a single interaction from your app.
3. Be helpful in Question threads related to your domain. If your app is a database client, answer every Postgres/SwiftData/CloudKit question you can. Over 12 months this builds a followable author.
4. Do not post a second app on App Saturday for a different project — the rule says "one post per year" across all apps, not per app.

Community-specific comment reply templates

For pre-launch or launch-day comment sections, pre-write responses to these 5 common objections:

1. "Is this AI-generated / vibe-coded?" → "Roughly [X]% of the Swift was written with [Claude Code / Cursor / etc.], the rest was me. I enforce architecture with a [AGENTS.md / CLAUDE.md / project rules file] and review every diff. Happy to share the setup if useful." (See the 48-point "How I got an AI coding agent to actually respect our iOS architecture" for the template.)

2. "Subscription? Why not one-time?" → "Fair question. The [specific recurring cost, e.g. API/server bill] means a one-time doesn't sustain it. I do offer a lifetime unlock for $X if you prefer." Never be defensive; explain the economics once.

3. "Why not use [existing tool]?" → "I tried [existing tool] for [X months]. The specific thing that broke for me was [concrete pain point]. This app is built around that pain point." Specificity beats feature comparison.

4. "Xcode will eat you alive on this" → "Oh yeah, [specific Xcode pain I've hit], and [how I worked around it]." Join the shared-suffering bonding ritual. Never defend Xcode.

5. "Why native instead of React Native / Flutter / Kotlin Multiplatform?" → "I wanted [specific native feature: SwiftUI animations / ARKit / WidgetKit / App Intents / etc.] and cross-platform would have been a dead-end for that." The community will upvote a native-first justification.

Stealth distribution tactics (non-launch)

1. The "how do you all use AI in Xcode" thread answer. These threads appear every few months. Be the second or third commenter with a concrete workflow and your tool/app will get organic DMs.
2. The Xcode-rant reply. When someone posts an Xcode pain post, reply with (a) agreement, (b) the workaround you found, (c) optionally: "actually, I built a tiny tool for this". 1 of 3 replies converts.
3. The screenshot-feedback offer. Post "Feedback on App Store Screenshots" (222 upvotes, 143 comments) style content — give feedback generously on others' screenshots, become the trusted screenshot person.
4. The "curated resources" post. "I've curated 159 resources to help you grow your app" (171) works in this sub. Build one, include your own tool as item 47 of 159, post as Discussion.
5. Reply-mining the Question flair. 54 posts, 25 avg comments. Be the helpful senior voice in question threads for 2 months and you'll be treated as a regular.

Score-tier calibration (what to realistically expect)

Do not expect 3,000+ upvotes. Only 1 post in the entire 309-post dataset clears 1017. The ceiling is real.

Post-publication measurement (what ratios and signals mean)

• Ratio 0.98+ in the first hour: You're on trend for a top-50 post. Stay responsive.
• Ratio 0.92–0.97: Normal. Most top posts sit in this band.
• Ratio 0.85–0.91: Friction. One of: pricing callout, AI callout, contrarian framing. Respond to specific criticism, don't delete.
• Ratio <0.85 at 2 hours: The post is controversial. Decide whether to defend (if you have the credibility) or accept the hit (if you don't).
• Comments >> upvotes (C/U above 1.5): You've hit a Discussion nerve. Great for reputation, but don't confuse it with visibility.
• 0 comments, moderate upvotes: You've posted a passive meme. Fine for visibility.
• Post stalls below 30 upvotes at 4 hours: It's over. Recovery is extremely rare. Do not delete (it signals deletion-as-manipulation to mods).

12. Applying This to Any Project

Quick-reference pre-post checklist

1. ☐ Is today Saturday in UTC? (If no, and you're planning App Saturday, stop.)
2. ☐ Have I used my annual App Saturday slot this year? (If yes, stop.)
3. ☐ Is my title under 15 words, with no emojis and no brackets?
4. ☐ Does my title include a "first", "just got", or milestone anchor?
5. ☐ Is my hero image a native simulator screenshot (not a mockup frame)?
6. ☐ Does my body copy open with "I built this for myself because…"?
7. ☐ Is my App Store link in the body or a top comment, NOT in the title?
8. ☐ Have I pre-drafted responses to: AI accusation, subscription complaint, "why not X" alternative, Xcode pain bonding, cross-platform "why native"?
9. ☐ Have I read the sidebar FAQ to confirm my post isn't a restricted topic?
10. ☐ If I have any Xcode frustration to share, is it in a separate comment (not the post)?
11. ☐ Do I have 2+ pieces of prior karma (humor or animation) on this account?
12. ☐ Am I prepared to reply for the next 4 hours straight?

Scenario-based launch guides

Scenario A: Your product is free / open-source

Optimal launch formula: App Saturday IMAGE post + title = "Open-sourced my [thing]: [one-line value prop]" + body mentions GitHub link in a self-comment. Expected: 150–400 upvotes, high ratio (0.97+). Key risk: Falling into the Library or Tutorial flair by mistake — these tank. Use App Saturday if it has an iOS app component. Bonus move: Post an Archetype 6 UI animation video from your app as a separate Discussion post 2 weeks before launch to warm up the audience.

Scenario B: Your product uses one-time / lifetime pricing

Optimal launch formula: App Saturday IMAGE + body explicitly states "$X one-time, no subscription". The explicit anti-subscription positioning is worth 100+ upvotes in this community. Key risk: Hiding the price. Not disclosing price until someone asks reads as scammy.

Scenario C: Your product uses subscription pricing

Optimal launch formula: App Saturday IMAGE + body must include: (a) what the recurring cost covers (server, API, AI tokens), (b) a free tier with real utility, (c) a one-time/lifetime alternative if possible. Expect friction regardless. Key risk: You will be compared to "yet another subscription app". Pre-draft the reply from Section 11. Fallback: Consider launching as Archetype 3 (Milestone AMA) after 3 months of real revenue instead of as an App Saturday post. The $35K AMA (976) beat every App Saturday post combined — revenue-as-entry can outperform launch-as-entry.

Scenario D: Your product was built with AI

Optimal launch formula: Do not lead with the AI angle. Use App Saturday with personal-utility framing. If asked in comments, answer transparently with specifics (X% AI, architecture guardrails). Key risk: Defensive pre-emptive framing like "(0 AI Code)" or "Not vibe-coded!" in the title — the 3-point example shows this tactic tanks the post (ratio 0.52). The community smells defensiveness. Alternative: Write Archetype 7 content: "How I got an AI coding agent to respect our iOS architecture" (48) as an Article to establish pro-AI-but-rigorous credentials, then launch under App Saturday later.

Scenario E: Your product is a developer tool (MCP server, CLI, API, agent)

Optimal launch formula: This is the Schema (626) path. App Saturday flair, IMAGE of the product running on iPhone, body = "I build things and always wished I had this. So I built it." Link in body. Key risk: Positioning as "AI-enabled" rather than "for developers". The community buys Schema: a database client more than it buys AI-powered Schema.

Cross-posting guidance

If you've already built analyses for other subreddits in this directory:

• r/macapps — Reframe the same product as "macOS is missing X, so I built it." r/macapps tolerates 4.2–4.9 star rating claims; r/iOSProgramming does not.
• r/swift — Reframe as technical post: "I built X, here's the challenging architecture decision." Focus on implementation.
• r/SideProject — Focus on the builder journey and revenue/traction numbers. r/SideProject tolerates explicit "I shipped" framing that works here only once per year.
• r/IndieDev — Emphasize the solo/indie angle and include visuals. More tolerant of pure launch framing.
• r/apple — Avoid. This is a consumer sub, not a dev sub. Your iOS dev launch will be off-topic.
• r/programming — Avoid unless you have a technical deep-dive; pure launches will be removed.

Reframe rule: On r/iOSProgramming, the frame is "I built this for myself as an iOS developer, and the journey taught me X." Never "Launching my app." Never "Please try my product." Always "I have 9 months of Xcode pain to show for this screenshot."