r/UI_Design — Distribution Playbook

A field manual for posting work, sparking discussion, and (carefully) distributing a product through r/UI_Design. Built from a full read of 288 unique top posts pulled across all-time, year, month, and week windows.

1. Data Sources & Methodology

• Subreddit: r/UI_Design
• Subscribers: 227,726
• Date collected: 2026-04-10
• Unique posts after dedup: 288
• Source files: 14 JSON pages across 4 time windows (top_all 1-4, top_year 1-4, top_month 1-4, top_week 1-2)

• Dataset score range: 0 → 985
• Dataset median: 75
• Dataset mean: 146
• Top-25 cutoff: 358
• Top-50 cutoff: 286
• Top-100 cutoff: 215

The drop-off from year (median 105) to month (median 7) is the single most important quantitative fact about this sub: weekly/monthly content is overwhelmingly low-engagement (single-digit scores), while the all-time leaderboard concentrates around a small number of breakout viral posts. A median post in any given week scores ~4-7 upvotes. This is not r/macapps where every solid launch clears 1,000. r/UI_Design is closer to "trickle of low-engagement feedback requests punctuated by occasional viral moments."

Cross-subreddit calibration (vs prior analyses in data/analyses/):

• r/UI_Design peaks ~985 vs r/ClaudeAI ~8,000 vs r/macapps ~2,000 vs r/webdev (mid-thousands).
• Median weekly post ~4 here vs 50-200 on most active subs. This sub is structurally low-velocity.
• Top-25 threshold (358) is closer to r/SomethingIMade than to r/SideProject.

This is a content strategy guide, not a sociological study.

2. Subreddit Character

r/UI_Design is a quiet feedback workshop with viral spikes around shared design grievances. The everyday rhythm is solo designers and devs posting "feedback please" mockups that get 5-20 upvotes and a handful of polite, often shallow comments. The viral posts are something else entirely: Design Humour memes, Apple/Google rage threads, novel micro-interactions, and "look what I made in Figma" experiments that punch through to 400-985.

Who is here? A mix of:

1. Junior designers and bootcamp grads asking for portfolio help.
2. Devs (often solo founders) who need design feedback but can't afford a designer.
3. Working UI/UX professionals who lurk and occasionally vent.
4. Game devs showing off custom UI for indie projects.

The technical level is genuinely uneven. Comments on Left or Right? posts are full of useful critique, but comments on "is this hireable?" portfolio threads tend toward generic encouragement. There is no dominant "expert class" the way r/ExperiencedDevs has.

Self-promotion stance: officially hostile, practically tolerated for legitimate work. Rule 1 explicitly forbids self-promotion ("posts or articles that serve primarily as self-promotion are not permitted"). Rule 5 ("Requesting feedback") repeats: "No self-promotion in images, titles, or comments." In practice, "I built this app, what do you think?" posts that include genuine feedback questions get through. Posts that drop a download link prominently get downvoted to oblivion (see ratio 0.27-0.5 cluster).

Humor works extremely well. Design Humour is the highest-ceiling flair: 20 posts, average 332, top post (Water drop button) is the all-time #1 at 985. The community shares a deep well of collective frustration about bad enterprise UI, Apple's recent missteps, and lazy AI-generated work — humor that taps into those gets rewarded.

Cultural values, ranked:

1. Craft and intentionality — explaining why a design choice was made trumps showing pretty pixels.
2. Anti-AI-slop — "Someone built this only via Claude" hits 0.69 ratio; "AI related posts on this sub should be banned" sits at 73 upvotes; "Leadership demanding AI usage" is the highest-comment General Help post.
3. Anti-self-promotion — links in body, "download my app," and "rate my X" with no actual question all underperform.
4. Pro-skeuomorphism nostalgia — Y2K, Vista, Windows 2098, Zune, MSN Messenger redesigns all appear in top 100.
5. Anti-Apple-trillion-dollar-laziness — Safari iOS 26, Liquid Glass, Forget Device button, corner radius rant all hit Top 100.

Enforcement mechanisms:

• Rule 1 (self-promotion) → low ratio + downvote brigade
• Rule 3 (career/getting-started posts must go in megathread) → those posts get 3-5 score
• Rule 5 (no self-promotion in titles) → "Please rate my UI" framing underperforms vs "What if I am 28?" framing
• No public blacklist or hall of shame, but the community self-polices in comments

How it differs from neighbors: Unlike r/web_design (commercial-friendly) or r/graphic_design (broader), r/UI_Design is narrowly focused on screens and interactions, hostile to portfolio dumps, and structurally smaller. Unlike r/UXDesign (theory and career), this sub wants to see the pixels. There is no "Show & Tell" / "Made by Me" megathread culture — every post is freestanding.

3. The All-Time Leaderboard

Median score in dataset: 75. Top-25 threshold: 358.

Notes:

• Zero galleries in the top 8. Galleries first appear at #9. Gallery posts are heavily back-loaded (top-25 has 1 gallery; top-50 has 3).
• Ironic flair use: Curved window control buttons is tagged "UI/UX Feedback Request" but is 95% a showcase post; Hey guys am I doing this right? is technically a feedback request but reads as showcase. The community rewards posts that frame as humble feedback while actually presenting polished work.
• Of top 25, only 7 also appear in the "year" period. This means 18 of the 25 highest-scoring posts are 2+ years old. The community ceiling has dropped — recent peaks are ~890 (Curved buttons), ~549 (Liquid Glass), ~530 (date format), ~463 (Guys, is it true?). Anything you post today is realistically chasing a ~500-900 ceiling, not 985.

4. Content Type Dominance at Scale

Most surprising finding: Feedback Request (the legacy/generic flair) has 93 posts — by far the most populated — with an average score of just 61 and a 0.85 ratio. This is the single largest "trap" in the sub: defaulting to the obvious flair name puts you in a pool with 92 other feedback posts averaging double-digits. The newer UI/UX Design Feedback Request (45 posts, avg 167) performs nearly 3x better despite being the same intent — almost certainly because it's the current-default that mods/UI surface, while the older flair is associated with legacy low-effort posts.

Second surprise: The top performer by raw avg is UI/UX Software and Tools (avg 412 across only 2 posts) — both are tool-launches that genuinely fit the rule against self-promotion by leading with the tool rather than asking for clicks. But the sample is too small to use as a strategy.

Third surprise: General Question flair has a 0.81 average ratio — the second-lowest among populated flairs. The community is mildly hostile to "why is X like this?" framing unless the question has a strong observation embedded (e.g., Why is Amazon's UI so bad? clears 317 by being a rant disguised as a question).

5. Content Archetypes That Work

Six distinct archetypes derived from the data, ranked by score ceiling:

Archetype 1: The Visual Joke (ceiling: 985)

Score range: 222 → 985 | Format: IMAGE almost always | Examples:

• Water drop button (985) — Figma experiment that looks like a joke
• It is what it is. (742)
• Take a bow (732)
• That's why UX Matters...!! (426)
• Eras of Modern Aesthetics/UI Design (358)
• Are facebook designers okay? (439) — found-in-the-wild bad UI

The pattern: A single image with zero or one-line selftext, captioned with knowing exhaustion or dry observation. Often either (a) a punchline visual the designer made themselves as a joke or (b) a screenshot of real product UI being mocked. Works because the community shares an in-group fatigue with bad design and rewards content that names it.

Distribution use: If you have a product, don't try to launch it through this archetype. But you can build account credibility with one or two of these before a launch post. Comments are usually conversational and you can be a person.

Archetype 2: The "I Made This For Fun in Figma" Showcase (ceiling: 890)

Score range: 232 → 890 | Format: VIDEO heavily, IMAGE second | Examples:

• Curved window control buttons (890)
• Hand-Drawn UI for an Indie Game (532)
• Onboarding Animation made with Figma (411)
• Table Booking Animation in Figma (392)
• Send email interaction (367)
• Reflection layer turned out (14, lower-tier example)

The pattern: An experiment, not a product. Selftext explicitly says "just for fun," "experimental thing," "weekend project," or names the inspiration source. The framing inoculates against the self-promotion downvote brigade. Even when there is a real app in the background, the post is structured as design exploration first.

Why it matters: This is the highest-ceiling archetype that someone with a product can actually use. Strip the product name. Show a single interaction or microinteraction. Frame it as "I was experimenting with X" or "Inspired by Y, I tried Z." If asked in comments, you can name the project. Don't lead with it.

Archetype 3: The Genuine A/B Decision (ceiling: 450)

Score range: 91 → 450 | Format: IMAGE or GALLERY | Examples:

• We're in a UI war over book displays — help us break the tie (450, 336 comments)
• Thank you all for your feedback. I've made the adjustments. (304) — the follow-up post after the war
• Left or Right? (162, 141 comments)
• Which one is better, option 1 or 2? (179, 91 comments)
• Which one works better? (Wireframe) (71, 50 comments)

The pattern: Two designs side-by-side, a real decision the OP can't make, and a clearly-stated "which?" question. These posts generate the highest comment volume in the entire dataset — book displays (336), Left or Right? (141), option 1 or 2 (91). They are the discussion machine of the sub.

Distribution use: If you have a product, this is the single best stealth-launch vehicle. The OP of book displays literally added "(+ The feature's coming soon, so if you're interested, feel free to download the app from the link in my profile... please... 🙏😅 name: repov)" at the bottom of the post — and it scored 450 with 336 comments. The follow-up post Thank you all for your feedback then scored another 304. Two posts, ~750 cumulative score, 380+ comments, all from one A/B framing.

Archetype 4: The Apple/Google Grievance (ceiling: 549)

Score range: 109 → 573 | Format: VIDEO or IMAGE | Examples:

• Reddit video player scrubber out of safe zone (573)
• Liquid Glass? (549, 263 comments)
• Unpopular opinion, Safari on iOS 26 (287, 108 comments)
• Apple's Forget Device Button Design (145)
• Apple, what the HELL is that corner radius (143)
• Sparkles or robots to represent AI (109, 69 comments)

The pattern: Identify a real, recent UI choice from a trillion-dollar company, document it, and let the community vent. Apple is the most reliable target. The comments section becomes a group therapy session. Note: Liquid Glass? scored 549 despite a 0.92 ratio — the post hit a divisive nerve and people came to argue.

Distribution use: Build credibility, not direct distribution. Posting a sharp Apple critique gives you community reputation that compounds when you later post your own work.

Archetype 5: The Industry Vent / Hot Take (ceiling: 317)

Score range: 71 → 317 | Format: TEXT | Examples:

• Why is Amazon's ui so bad? (317, 103 comments)
• Got laughed at for my rates (317, 106 comments)
• Fuck montserrat (291, 150 comments) — the only post in this dataset that appears in 3 periods (all/year/month)
• Unpopular Opinion: Wireframing tools have become too high-fidelity (59)
• nobody cares about your "redesign of netflix" (237)
• Material UI single handedly ruined the internet (162)
• Why the modern UIs are so souless? (71)

The pattern: A short, punchy, opinionated text post that names something the community already feels but hasn't said. Best examples are personal — "I just came here to vent" — and surprisingly low-effort. Fuck montserrat is 84 words and has the longest staying power of any post in the dataset.

Distribution use: Cannot directly carry a product. Use to establish account voice. Your account becomes someone people recognize when you later post work.

Archetype 6: The "What's This Style Called?" / Identification Post (ceiling: 337)

Score range: 59 → 337 | Format: IMAGE | Examples:

• Historic System Scrollbars (337) — itself an answer
• What is this called? (248) — Gumroad-style drop shadows
• Need help identifying this design style/design language? (119)
• How was this UI made? (59)
• Can anyone tell me what does this type of design called? (75)

The pattern: One screenshot, one direct identification question, explicit naming of a design style. The community loves naming things and these posts function as collective glossary-building.

Distribution use: If you can frame a real curiosity about how a competitor or inspiration achieved something, you can post a screenshot from your own product or a competitor's, ask a real question, and have the comments do the work of contextualizing your space.

Notable archetype absent: Giveaways

There are zero giveaway posts in this dataset. The combination of Rule 1 (no self-promotion) and the small subscriber base (227k) means the "200 promo codes" tactic that dominates r/macapps does not exist here. Don't try it.

6. Format Analysis

Key observations:

• IMAGE dominates top tiers. Single images outperform every other format at the highest level. This is a "show me one perfect screen" community more than a "show me everything" community.
• GALLERY is heavily back-loaded. 60 gallery posts but only 1 in the top 25. Galleries average 82 vs IMAGE's 192. The "swipe through 6 screens" format is not how this sub consumes work — readers stop at frame 1.
• VIDEO is the strongest tied-second. 14 of top 50, 9 of top 25. Microinteractions, animations, and polished UI demos in <30 second loops perform consistently.
• TEXT mostly fails — except for hot takes. 43 text posts but only 3 in top 100. The 3 that hit are all rant/discussion archetypes.

What format to use for what

What makes a good demo video on this sub

Drawn from the top 14 video posts (Curved buttons, Liquid Glass, Reddit player, device frame tool, PS5 UI Concept, Reaction to UI tools, Onboarding Animation, Table Booking Animation, Hidden Brain landing, Send email, Microinteraction posts):

1. Length: 5-30 seconds. Single loop, single interaction. No here's the entire app walkthroughs.
2. No talking head, no voiceover. Nothing in the top 25 has narration. Silent screen recordings only.
3. Show the interaction not the product. Curved buttons, the date format toggle, the burger animation — they isolate one motion. The eye knows where to look.
4. High-contrast UI on a dark background. Most top videos are dark-themed; the motion pops.
5. Loop must be obvious. If your video is 8 seconds and ends mid-action, it feels broken. Either land the gesture or seamlessly loop.

Gallery rules (when you must use one)

• 3-6 frames maximum. Top gallery posts (Hand-Drawn UI for Indie Game, Sketch to clickable prototype) hover around 5-8 images.
• Frame 1 must be your strongest shot. The sub does not swipe.
• Number frames in image overlays. Top gallery posts use sequential labels.

7. Flair/Category Strategy

Raw performance ranking (avg score, populated flairs only)

Distribution utility ranking (different from raw performance)

If your goal is to launch or distribute a product, the best flairs are different:

1. UI/UX Design Feedback Request — gives you cover to show product UI, framed as a real question
2. Microinteraction — perfect for showing one interaction from your app without "launching"
3. General UI/UX Discussion — best for opinion/debate posts that mention your work
4. Design Humour — for credibility-building only, not direct distribution
5. Avoid: Feedback Request (legacy), General Question, Product Design (rare and underperforming), Let's Discuss (lowest ratio in dataset, 0.78)

Flair tags and brackets in titles

This sub does not have bracket/tag conventions like [OS] or [FREE] that you see in r/macapps. Looking through 288 titles, I found one [Android App] prefix (scored 0). Don't use bracket tags here — they signal "I came from another sub."

Pricing-model preferences

There is no pricing-model hierarchy because the sub doesn't allow direct product pricing discussion in posts at all (Rule 1). But the implicit hierarchy from comment culture is:

1. No-mention / "personal project" (preferred)
2. Free / open-source (acceptable if mentioned in comments)
3. One-time purchase (rare, no signal)
4. Freemium (use sparingly — Free Forever! Until it isn't. scored 312 by mocking the model)
5. Subscription (community is hostile, see comment threads on TradingView interaction post)

8. Title Engineering

Top 10 titles deconstructed

1. Water drop button — Pure noun. No promise, no question. Image carries 100%. Technique: zero-effort label that lets the visual punchline land.
2. Curved window control buttons — Same. Three nouns. Technique: descriptive minimalism.
3. It is what it is. — Cynical caption framing. Technique: dry observation, image = reveal.
4. Hey guys am I doing this right? — Faux humility. Technique: insiders posting polished work behind beginner framing. Comments respond to the polish.
5. Take a bow — Two-word praise framing. Technique: implied screenshot of something impressive.
6. Steam on mobile doesn't look as good so I designed this. My first design btw. — Context + humility + trigger. Technique: observed problem + offered solution + "first time" disarming.
7. Whoever designed the reddit video player for iPhone 10 - 12 clearly doesn't know basic Apple design guidelines. The video scrubber is out of the safe zone. — Direct accusation + technical justification. Technique: name a target, cite a rule.
8. Liquid Glass? — Single-word reference + question mark. Technique: zero exposition, assumes the reader knows the news.
9. Hand-Drawn UI for an Indie Game — Genre + medium + use-case. Technique: description-as-pitch, no question.
10. Such a small UI thing, but so helpful when dealing with European and American dates — Diminutive + specificity + pain point. Technique: framing a tiny win as universal.

Title formulas that work

Formula 1: Pure descriptive noun phrase

• Water drop button
• Curved window control buttons
• Hand-Drawn UI for an Indie Game
• PS5 UI Concept
• Send email interaction

Formula 2: Faux-humble feedback request

• Hey guys am I doing this right?
• I'm in love with this interaction I made, but...
• Looking for some feedback for the UI of my game.
• Was bored today, so i designed a camera app! what do you think?

Formula 3: Apple/Google grievance

• Whoever designed the reddit video player...
• Are facebook designers okay?
• Apple, what the HELL is that corner radius
• Unpopular opinion, Safari on iOS 26 has the most unintuitive UI...

Formula 4: Single-word or phrase prompt

• Liquid Glass?
• Pls stop
• What now?
• neumorphism
• Cheatcode.

Formula 5: A/B decision question

• We're in a UI war over book displays — help us break the tie
• Left or Right?
• Which one is better, option 1 or 2?
• Which color direction would you pick for this UI?

Formula 6: Vent / hot take

• Fuck montserrat
• nobody cares about your "redesign of netflix" if you can't design a boring table ui
• For the love of Christ stop hiding shit that was readily available

Title anti-patterns (community-specific)

These are not generic Reddit advice — they are observed failure modes in this exact dataset:

Anti-pattern 1: ALL CAPS pleas. UI UX FEEDBACK FOR MY TRAVEL PLATFORM (0 score, 0.29 ratio). The sub reads caps as desperation.

Anti-pattern 2: "Please rate my X." Please rate my UI for my app (8 score, 0.73 ratio). "Rate" framing is a downvote magnet.

Anti-pattern 3: Naming your product in the title. New UI for newspaper in cozy game (15) is fine; Solo Dev! Revamped Game UI in DualVerse86 (0 score, 0.5 ratio) is not. The difference: the second one names the product.

Anti-pattern 4: Selling the question. Hero section for an AI execution system. Aiming for a "premium/stoic" vibe... (1 score, 0.54 ratio). Long, jargon-loaded, framed as "I have a product positioning thesis."

Anti-pattern 5: Multi-platform shoutout / cross-post energy. [Android App] I built a hyper-minimal to-do list... (0 score, 0.5 ratio). Brackets and platform mentions signal "I came from r/AndroidDev."

Anti-pattern 6: Title is a meta-question about the sub or industry. (Serious question) Ux / Product designers currently in top companies... (5 score, 0.73 ratio). The community does not want career megathread content in feed posts.

Anti-pattern 7: AI-built or AI-style framing. Someone built this crazy design only via Claude (25 score, 0.69 ratio); Figma Make can generate wireframes from prompts now (5 score, 0.56 ratio). Naming AI in the title triggers the anti-slop reflex.

9. Engagement Patterns

Comments-to-upvote ratio by format

Reading the table:

• TEXT posts have the highest C/U ratio (1.34). Hot takes and questions punch above their weight in conversation per upvote — but most flop in absolute terms.
• VIDEO has the lowest C/U among real formats (0.51). Beautiful microinteractions get passive upvotes. People like and scroll. Don't expect deep discussion from your video post.
• IMAGE A/B posts are the best of both worlds — high score AND high comments (book displays 450/336 = 0.75 ratio; Left or Right? 162/141 = 0.87 ratio).

Conditional recommendation

• Goal = visibility? Post a polished IMAGE or short VIDEO microinteraction with descriptive nouns as the title. Aim for the Made-in-Figma archetype.
• Goal = relationships and discussion? Post a TEXT hot take or an IMAGE A/B decision. You will get fewer upvotes per impression but 5-10x the comments per upvote.
• Goal = stealth product distribution? Post an A/B decision frame (Archetype 3) — it gives you the comment volume and lets you mention the product in passing in selftext.

Highest-discussion topics in the dataset

Regardless of upvote count, these subjects generate the most comments:

1. Apple's recent design choices (Liquid Glass, Safari iOS 26, corner radii) — Liquid Glass? 263 comments
2. A/B decisions on real apps — book displays 336, Left or Right? 141, option 1 or 2 91
3. AI in design / "AI ban" — Leadership demanding AI usage 66, AI related posts should be banned 10 (small but high engagement-per-upvote)
4. Pay/rates/career laments — Got laughed at for my rates 106
5. Why is [BigCo] UI bad — Amazon 103, Reddit 65, Material UI 51

10. What Gets Downvoted

63 posts (22% of dataset) have ratios below 0.85. This is a notably high friction rate compared to most subs. The pattern is sharp.

Notable downvoted posts

Three ratio tiers

• >0.94 — universally well-received. 70% of posts above the median sit here. Posts are accepted regardless of strength.
• 0.85-0.94 — net positive but with friction. Often controversial Apple/AI posts that are still popular. Acceptable.
• <0.85 — controversial or community-hostile. 22% of all posts. Almost always fall into one of the anti-patterns below.

Anti-patterns (community-specific, named)

1. The Hostage Beg. Please rate my UI for my app. Begging language ("please," "rate," "honest feedback wanted") with no specific question. Treated as low-effort. Example: Please rate my UI for my app (8/0.73).

2. The AI Tell. Mentioning AI in the title or first line. Even when the post itself is fine. Examples: Someone built this crazy design only via Claude (25/0.69), Figma Make can generate wireframes from prompts now (5/0.56), Feedback wanted on my local AI chat app UI (0/0.42).

3. The Self-Promo Stealth Fail. A post that looks like feedback but the selftext contains a download link, app store URL, or "if you like this, check out my app" CTA. Example: Hero section for an AI execution system (1/0.54) — selftext was a positioning pitch.

4. The Caps Plea. ALL CAPS title. Example: UI UX FEEDBACK FOR MY TRAVEL PLATFORM (0/0.27). The lowest ratio in the dataset.

5. The Off-Topic Career/Hustle Post. "How do I find high-ticket clients?" "Should I do bootcamp or self-teach?" These belong in the Careers megathread (Rule 3). Examples: How do you guys find high-ticket clients (8/0.69), (Serious question) UX / Product designers in top companies... (5/0.73).

6. The Empty Question. "What is this style called?" with no image, or with a single-line description. The sub will help if you put effort in; it will downvote if you don't. Example: What is this style called? (0/0.27).

7. The Bitter Designer. Posts that complain about other people's posts on the sub. Example: Let's call a shit a shit (3/0.51) — 25 comments, mostly arguing back. Self-policing is welcome from comment threads but not from top-level posts.

No public blacklist or hall of shame

Unlike r/macapps (which has a blacklist), r/UI_Design enforces purely through community downvoting and comment callouts. There is no named astroturfing enforcement mechanism. Mods enforce through the rules listed in Section 2 — you may see your post removed silently, but there's no "wall of shame."

11. The Distribution Playbook

Phase 1: Pre-launch (2-4 weeks before posting your work)

1. Read the sub for 7 days before posting anything. Notice which Apple posts get traction, which A/B questions thrive, who is recurring.
2. Build a non-product account if you don't have one. A 0-karma account posting feedback requests is treated as suspicious. You don't need 1000 karma — you need some prior comments.
3. Comment on 5-10 feedback request posts. Real, substantive critique. Use this to learn the community's evaluation vocabulary (typography, hierarchy, contrast, accessibility, density, alignment).
4. Write down your why. What design decision did you make and why? You will need to explain this in the selftext and in comments. Posts without a why get the 60-point treatment.
5. Strip your product name from everything you plan to post. Even if it leaks in comments later, the post itself should not function as marketing.

Phase 2: Launch day

Format choice:

• Single screen of polished work → IMAGE
• One animated interaction → VIDEO (5-30s, silent, looped)
• An A/B decision → IMAGE side-by-side
• A discussion/observation → TEXT

Flair choice:

• Default to UI/UX Design Feedback Request (NOT Feedback Request — the legacy version is the trap)
• Use Microinteraction if your post is one isolated animation
• Use General UI/UX Discussion for industry-observation posts
• Use Design Humour only if it is actually funny
• Never use Feedback Request, General Question, Let's Discuss, or Product Design

Title:

• Lead with a noun or descriptive phrase
• Max 60 characters
• No CAPS, no brackets, no product names, no "please"
• If using A/B framing, end with a real choice question

Selftext (mandatory if you have a product to mention):

• Open with the design decision you made and why
• Name 1-2 specific things you want feedback on (clarity, hierarchy, color, motion, density)
• Optional product mention: 1 sentence at the end, in a self-deprecating tone, with no link
• Never include a download URL in the body of a launch post

Timing:

• The dataset doesn't expose post time directly, but the high-scoring all-time posts span years and the year/month posts are spread across months. Timing matters less than the format/framing combination on this sub.

Phase 3: First 24-48 hours

1. Respond to every comment in the first 4 hours, even if it's "thanks!" This is when the post is being evaluated by the algorithm.
2. Treat criticism as conversation, not threat. The fastest way to tank your ratio is to argue with critique. Acknowledge, ask follow-ups, share your reasoning.
3. Drop the product link only when asked. Wait for someone to ask "what app is this?" — there's almost always one comment. That is the moment.
4. Save the screenshots of comments. If you do a follow-up post (Archetype 3 follow-up), the previous discussion is your credibility.
5. If your post hasn't moved past 20 upvotes in 4 hours, do not panic-edit the title. Edits are visible. Either the post will catch a slow burn (year-period posts often do) or it won't.

Phase 4: Ongoing presence

1. Plan a follow-up post within 1-2 weeks. The Thank you all for your feedback. I've made the adjustments. post (304 upvotes) demonstrates this works. The community rewards designers who actually iterate on their feedback.
2. Don't repost the same UI more than twice per month. This sub will start ignoring you.
3. Mix archetypes. A designer who only posts product mockups is read as a marketer. A designer who posts a humor post, then an A/B, then a microinteraction, then a feedback request reads as a community member.
4. Do NOT use multiple accounts. Sidebar explicitly bans this.

Community-specific comment strategy (pre-written replies)

When critics show up, here are templates calibrated to the sub's culture:

"Looks AI-generated": "Fair concern — I built this in Figma over [time]. The components are [name them: cards, type system, etc.]. Happy to share the file if it helps." (Specificity beats denial.)

"Looks like every other SaaS dashboard": "That's the critique I needed. The decision I made was [X], because [reason]. Curious whether you'd push the [specific element] further or rethink the layout entirely." (Don't defend; redirect to one concrete decision.)

"Why didn't you just use [existing tool/style]?": "Honestly considered it. The reason I went custom was [user need]. If you're seeing a place where I'm reinventing the wheel for no reason, would love to know which part."

"Is this vibe-coded / built with Claude?": "Designed in Figma. The implementation is [Flutter/SwiftUI/etc]. AI was used for [boilerplate / not at all]. I don't think AI design holds up at the spacing/hierarchy level — I'm still doing that part by hand."

"What's the pricing model?": "Not selling anything yet — this is a [side project / portfolio piece / WIP]. Happy to share the link if you want to play with it." (Defer commerce talk.)

Stealth distribution tactics

1. The A/B Trojan Horse. Build a real A/B decision into your product, post it as Archetype 3, mention the product name once at the end of selftext. This is the single highest-yield tactic.
2. Become the commentator. Top commenters on viral posts are visible in the sub. Comment substantively on Liquid Glass?-style posts and your username starts getting recognized.
3. The follow-up post. After a feedback post, do "I made the adjustments" 1-2 weeks later. This is permitted and rewarded.
4. Microinteraction extraction. Pull one animated detail out of your app and post it as Archetype 2 ("just experimenting with X"). The detail, not the product, is the post.
5. The sub-as-glossary play (Archetype 6). Find a competitor or inspiration whose style you admire. Post "what is this style called?" with their screenshot. The comment thread becomes free education and a place where you can mention your own work in passing.

Score-tier calibration (be honest with yourself)

If you need 3,000+ upvotes for visibility, this is the wrong subreddit. Cross-post to r/webdev, r/SideProject, or r/macapps for that.

Post-publication measurement

12. Applying This to Any Project

Quick-reference checklist

• I have read the sub for at least 7 days
• I have made 5+ substantive comments before posting work
• My title is a noun phrase or A/B question, not a plea
• My title contains no caps, brackets, or product names
• My flair is UI/UX Design Feedback Request or Microinteraction (NOT Feedback Request)
• My selftext explains why I made a design decision
• My selftext lists 1-2 specific things I want feedback on
• No download links in the post body
• No mention of AI in the title
• Format: IMAGE if single screen, VIDEO if interaction, side-by-side IMAGE if A/B
• If I have a product, I have a follow-up post planned for 1-2 weeks later

Scenario-based launch guides

Scenario A: Free / open-source project

• Optimal formula: Microinteraction VIDEO + Microinteraction flair + descriptive noun title. In comments, link to the open-source repo when asked.
• Key risk: Treating "open-source" as a free pass. Rule 1 still applies. Don't lead with "I open-sourced this."

Scenario B: Lifetime / one-time pricing

• Optimal formula: Archetype 3 (A/B decision) + UI/UX Design Feedback Request flair + product name as the very last line of selftext. The book displays post is the template.
• Key risk: Mentioning price anywhere. Even "$10 lifetime" reads as a sale.

Scenario C: Subscription product

• Optimal formula: Archetype 4 (Apple/Google grievance) using a real bad UI from a competitor. Build credibility for 2-3 weeks. Then post Archetype 2 as a "what I'm building instead" microinteraction.
• Key risk: This sub is structurally hostile to subscription apps. Direct subscription mentions get the TradingView treatment (sub of Interactive "please don't go!" when canceling TradingView post). Lead with the anti-subscription design choices in your product.

Scenario D: AI-built or AI-powered product

• Optimal formula: Pretend the AI part doesn't exist for the post. Post Archetype 2 ("I made this microinteraction in Figma"). Talk about the design, not the model.
• Key risk: Mentioning AI in the title is the single most reliable anti-pattern in the dataset. Someone built this crazy design only via Claude (25/0.69), Figma Make can generate wireframes (5/0.56). Avoid even sympathetic AI mentions.

Scenario E: Indie game with custom UI

• Optimal formula: GALLERY of 5-6 frames + UI/UX Design Feedback Request flair + title naming the genre and aesthetic ("Hand-Drawn UI for an Indie Game"). The game UI archetype is one of the few cases galleries work.
• Key risk: Posting too many similar shots. Pick the strongest 5; lead with frame 1.

Cross-posting guidance

If you have content that could go to multiple subs, reframe per audience:

• r/UI_Design → "Here's a microinteraction I made — feedback on the motion?"
• r/webdev → "Built this with Tailwind + Framer Motion, here's the code/repo"
• r/SideProject → "Launched my app this week, would love feedback"
• r/macapps → "macOS is missing X, so I built it"
• r/sideproject + r/UI_Design double-post → Post the product on r/SideProject, post the interaction on r/UI_Design. Same project, different framings, different formats. Don't use the same title and screenshot on both.

The r/UI_Design framing is always: the design decision, not the product launch. If you cannot translate your post into "the interesting thing about this is the [hierarchy/motion/density/typography] decision," you are in the wrong sub.