Mobile App Developers

Mobile developers: iOS, Android and cross-platform help, store rejections and reviews, design critique and launches.

9 categories
37 channels
15 roles
Medium

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

LOBBY

dev-guidelines
No store-review manipulation, no fake referral links, credit the libraries you use.
whats-your-stack
Say hi: platforms, languages, what you have shipped or want to.
platform-pick
iOS, Android, Flutter, React Native, Design and Launch Pings.
mobile-dev-news
Platform releases, policy changes and deadlines that affect submissions.

IOS

swift-and-swiftui
One thread per problem. Include the OS version, the Xcode version and the code.
xcode-and-build-issues
Builds that fail, archives that will not upload, simulators that vanish.
apple-frameworks
The system frameworks: maps, health, AR, widgets, notifications.
testflight-and-signing
Certificates, profiles, entitlements and TestFlight processing.

ANDROID

kotlin-and-compose
One thread per problem. Include the API level, the library versions and the code.
gradle-and-build-issues
Sync failures, dependency conflicts and the build that worked yesterday.
jetpack-and-libraries
Jetpack, third-party libraries and what to use for what.
device-fragmentation
The bug that only happens on one manufacturer's phones.

CROSS-PLATFORM

flutter
Flutter and Dart, widgets and platform channels.
react-native
React Native, the new architecture and native modules.
kotlin-multiplatform
Shared Kotlin, and where the platform code still has to live.
which-framework
The argument everyone has once. Bring a real requirement.

STORE AND REVIEWS

app-review-rejections
Title with the guideline number and the platform. Paste the reviewer's message with private details removed.
aso-and-listings
Store pages, keywords, screenshots and what changed conversion.
subscriptions-and-iap
In-app purchases, subscriptions, receipts and refunds.
handling-reviews
One-star reviews, replying well, and the review that is actually a bug report.
release-checklists
What to check before every submission, per platform, maintained by the mods.

DESIGN FEEDBACK

ui-critique
One screen per thread. Say what the screen is for and what you are unsure about.
icons-and-screenshots
App icons and store screenshots. Post the alternatives too.
accessibility
Screen readers, contrast, dynamic type and the things a checklist misses.

SHOWCASE

app-launches
One thread per launch: the store links, what it does, what you learned.
beta-invites
TestFlight and Play testing links. Say what you want tested. Regulars and publishers only.
milestones
First hundred users, first payout, first feature. Celebrate here.
community-favourites
Vetox posts the launches and screens members starred most.

VOICE

Dev Hangout
Debug Together
Design Review
Mobile Talks
AFK

STAFF

mod-team
Verified Publisher checks, reports and the checklist updates.
report-triage
One message per report: link, what happened, outcome.
server-logsHidden from @everyone
Vetox posts moderation and join logs here.
Mod Room

Roles

OwnerAdministrator
AdminAdministrator
ModeratorModerator
Verified Publisher
Regular
Indie Dev
Studio Dev
iOS
Android
Flutter
React Native
Design
Launch Pings
Muted

Overview

A server for people who ship apps to the stores, whether they build for one platform or all of them. The platform categories are split by stack rather than by device: iOS has a #swift-and-swiftui forum tagged SwiftUI, UIKit, Concurrency and Xcode, plus #xcode-and-build-issues, #apple-frameworks and #testflight-and-signing; Android has a #kotlin-and-compose forum with #gradle-and-build-issues, #jetpack-and-libraries and #device-fragmentation; Cross-Platform gives Flutter, React Native and Kotlin Multiplatform a channel each and #which-framework for the argument everyone has once. Store and Reviews is the category other developer servers lack: #app-review-rejections is a forum tagged Guideline, Metadata, Privacy and Payments where a rejected build gets a thread and usually a fix, #aso-and-listings covers store pages, #subscriptions-and-iap the money, #handling-reviews the one-star replies, and #release-checklists is read-only. Design Feedback has a #ui-critique forum tagged by screen type. Showcase keeps #app-launches as a forum, with #beta-invites for TestFlight and Play links. Voice has a Debug Together room and a Design Review room; moderation is hidden.

When to use it

Your mobile dev server has one help channel where a SwiftUI layout question, a Gradle sync failure and a rejected App Store build all wait for the one person who happens to know. Splitting by stack means each question reaches people who use that stack, store rejections get a forum where the same guideline problems are solved over and over in searchable threads, and launches and beta invites have a home that is not the general channel.

What makes it different

iOS and Android each get a forum tagged by the sub-topic that actually breaks: SwiftUI, Concurrency, Compose, Gradle.
#app-review-rejections is a forum tagged Guideline, Metadata, Privacy and Payments, where rejected builds get a thread.
#subscriptions-and-iap and #handling-reviews cover the two parts of shipping that are not code.
#ui-critique is a forum tagged Onboarding, Navigation, Dark mode and Accessibility, so feedback is one screen at a time.
#app-launches is a forum and #beta-invites is separate, so a TestFlight link never gets lost in a launch thread.

Recommended Vetox setup

Self-Roles
Post Self-Roles in #platform-pick for iOS, Android, Flutter and React Native plus Launch Pings, so a launch announcement reaches the people who want to try it.
Starboard
Point Starboard at #app-launches and #ui-critique with #community-favourites as the board, so the apps members rated most are collected in one place.
Auto-Mod
Enable Auto-Mod link filtering in #beta-invites and #app-launches against fake store links and referral spam, which is where they show up first.
Leveling
Make Regular a Leveling role reward at a level that takes a month of participation; it allows posting in #beta-invites, so drive-by promotion has a cost.

Questions

Why split iOS and Android if most members do both?

Because the questions are still platform-specific: a Gradle failure and a signing error have nothing in common except the developer. Members who do both take both roles and follow both forums. Cross-Platform is for the frameworks that sit above the split, and #which-framework is for the argument.

What is Verified Publisher and who grants it?

A moderator grants it to anyone with a live store listing after checking the link. It is a marker that helps newcomers weigh advice about reviews, subscriptions and rejections, and it allows posting in #beta-invites. Regular, earned through Leveling, allows the same after a month of participation.

How should a rejection thread be written?

Title it with the guideline number and the platform, paste the reviewer's message with private details removed, say what the build does, and tag it. The people who have been through the same guideline will recognise it from the title, and the thread is what the next developer with that rejection finds.

Common mistakes

One help channel for every platform, where the person who knows Gradle never sees the Gradle question under the SwiftUI ones.
Letting beta links and launch posts into general chat, which turns it into a feed of apps nobody asked for.

Consider instead

Programming Community Mobile is one topic among many for your members, and splitting by platform would divide one conversation.

Do you have any doubts?

Our team is there for you

0.0k

Servers

Commands

Users

Languages