Blog
Mobile apps on device forums
iOS and Android apps belong on XDA and MacRumors. ProductPost 360 uses that pack for device apps, not for social networks.
Someone looking for an Android utility is already on XDA. Someone living in the Apple ecosystem is already on MacRumors. A Product Hunt launch does not replace either room. ProductPost 360 has a consumer-mobile pack so device apps are drafted for those forums, and so they are not confused with dating or community apps.
How the rooms get chosen
The pack is for iOS and Android apps and device utilities. The catalog says to use the social pack instead when the product is a social, community, or dating app. The score looks for iOS app, Android app, iPhone, and device utility. A stronger social or gambling signal wins first place, and mobile becomes the second pack — which is how a poker client can be in player forums and on XDA.
Forums:
- XDA Forums
- MacRumors Forums
Reddit hints: r/androidapps, r/iosapps, r/Apple, r/androiddev, r/iOSProgramming.
XDA wants a device problem: a version of Android, a handset, a permission. MacRumors wants the Apple-side equivalent. The title names that problem. The brand and the version number do not lead.
Who on the account this fits
No product is stored on the consumer-mobile pack.
Snagto is the closest device tool: a private Windows capture queue for selected text and follow-up. It is stored as developer, so the plan is AWS, Cloudflare, and Vercel. XDA and MacRumors are not on it. Windows is also a weak fit for those two forums, which are Android and Apple. r/macapps lives on the productivity pack, not here. The stored pack is what you get.
Muffine Stressbomb — a one-minute venting toy — is stored as developer as well. If it is a phone app, consumer-mobile or social is the pack that matches the buyer. Developer matches the people who would build it, not the people who would install it.
DelbarMe is a community app, and it correctly sits on the social pack rather than this one. Social and consumer-mobile are allowed as a pair when an app is both a network and a store install. One id alone leaves half the rooms out.
After you paste
Write the device behaviour someone on that forum already hits. Disclose the app once. Link the release notes. Keep dating and community conversation on the social pack’s rooms, even when the binary is the same.
A consumer app with only the developer pack, which is where Snagto and Muffine sit today, will keep receiving drafts about infra. Those drafts are writable and useless to the person on XDA who wants to know if the app survives a specific Android build. Saving consumer-mobile adds XDA and MacRumors and the app subreddits. It does not delete Dev.to. You can still explain the architecture there.
If the app is also a social network, save social as the other id. DelbarMe shows the split working in the other direction: community rooms first, device forums absent until mobile is added. The catalog’s rule is the same either way. Two packs, the union of their rooms, and you paste the draft that the room will keep.