WeChat and phone-number auth plus China compliance layer for indie developers shipping apps to mainland China
Indie developers who built their app on Supabase/Firebase hit a wall when they try to ship to mainland China: WeChat and SMS login are expected, social/group features attract extra review scrutiny, and the whole backend stack is not usable there. They end up rewriting auth and backend plumbing from scratch with almost no references. A drop-in China-ready auth/backend layer that mirrors the Supabase API would let them keep their code and only swap the provider.
The problem
Developers finishing an app on Supabase auth find that Chinese app store review rejects or complicates the social/group features, and there is no way to plug in WeChat login or phone-number login on that stack. They must research unfamiliar providers, rewrite the auth flow, duplicate user tables, and separately figure out compliance requirements, turning a week of launch work into months of rework with no clear best practice or reference material.
What could be built
A China-ready auth and backend SDK/service that exposes a Supabase-compatible API but implements WeChat OAuth, phone-number + SMS login, and optionally Apple/QQ login, with mainland-hosted storage, a migration path that syncs existing user records, and a per-feature app store review checklist for social features. Sold as a managed service with a self-host option and priced per MAU.
Who it's for
Who is talking（1）
Related topics
Summaries are AI-generated. The original words are in the threads above.