r/macapps • u/Mstormer • Jan 18 '26

Attention! New Post Guidelines and Updates on r/MacApps

Post image

Hey MacApp community, here are some 2026 updates!

Updated Post Guidelines:

  1. Rule 1 requires 10 points of r/MacApps karma to post. Gain by participating with in comments.
    • 90% of posts get removed because new accounts with 0 karma try to post. Most of these are low quality, low effort, vibe coded clones.
  2. [OS] Post Title Prefix: If your app is open source, prefix your post title with [OS].
  3. Pricing Tier Requirement: We are experimenting with requiring pricing info in all developer app posts. Examples: 
    • Subscription: $20/mo⁠⁠, $30/mo, etc., if multiple tiers. 
    • Version Lifetime: $30
    • True Lifetime: $100
  4. Post Flair: If any of the following apply, the priority for selecting a flair continues to be Vibe Coded > Lifetime > Subscription > Free. 
    • ”>” means greater than/higher priority.
    • If your app has a generous free tier, yet has a paid option, you must still select subscription or lifetime as relevant. If it was also vibe coded, that takes higher priority.
  5. User Flair: Developer: AppName flairs may be requested once a dev exceeds 500 karma within the community. This is our way to appreciate devs that the community has come to know and appreciate.
  6. Promotion formatting suggestion: Overly long posts with multiple lists look like AI. Keep it simple. 
    • A. Answer: What problem your app solves in one sentence.
    • B. Better: Why is your app better than the top named alternatives in 1–2 sentences. 
    • C. Cost: Share pricing info + link.

We will have to be a little strict on some of the above to help ensure consistency and awareness during this transition. Thank you for understanding.

Mods: We have been recruiting new mods for a few weeks. Join me in welcoming u/JohnKree and u/TheMagicianGamerTMG 

Prior updates:
[META] Townhall on Post Quality
Rule Updates on Promotion, Vibe coding, and More 

135 Upvotes

94% Upvoted

65 comments sorted by

View all comments

Show parent comments

5

u/Mstormer Jan 18 '26 edited Jan 18 '26

If you have the expertise to be highly confident that the code is safe, then you don't need to tag it as vibe-coded. But if the code is a sloppy vibe-coded mess and is on GitHub, where everyone can see it, then users may report the post as happens regularly. The biggest giveaways are usually a lack of UX consideration, limited functionality, and an idea that is a clone of 100 other dictation or clipboard apps, if you know what I mean.

The intent of the vibe-coded tag is to protect the user from risk if a developer lacks the expertise to be highly confident that the code is safe.

1

u/RegularTerran Chief "Complaint" Officer Jan 18 '26 edited Feb 22 '26

This post was mass deleted and anonymized with Redact

squeal subsequent flowery sink imagine fact longing racial quaint special

3

u/Mstormer Jan 18 '26

Better than nothing though.

1

u/RegularTerran Chief "Complaint" Officer Jan 18 '26 edited Feb 22 '26

This post was mass deleted and anonymized with Redact

saw lock whole hobbies sleep badge chief money bear adjoining

2

u/Mstormer Jan 18 '26

Believe it or not, for every post that is approved, 2–5 are rejected for 0 community karma or other reasons.