Be Social Mobile

Be Social Mobile is an Expo and React Native client for a social app, wired end to end against Supabase. Posting with media, threaded comments, reactions, reposts, bookmarks, follows, hashtags, mentions, notifications, search, profiles, blocking, muting and reporting all run against a real Postgres database with row-level security on every table.

It is not a UI kit. The presentation layer is deliberately plain. The value is in the data layer, the auth plumbing, and the platform edge cases that cost weeks to find.

Find the desktop version here: https://zerotohundred.ai/listings/be-social-social-platform-boilerplate-next-js-15-supabase-ch2cf0

What runs on a phone today

• 20 screens on Expo Router with typed routes
• Compose with text, photos and video, from the library or the camera
• Trending, Following and Saved feeds, with infinite scroll and pull to refresh
• Threaded comments, indented one level then attributed with "Replying to @name"
• Reactions, reposts and private bookmarks, each with optimistic updates
• Notifications on follows, reactions, reposts, comments, replies and mentions, over Realtime
• Search across posts and people, plus suggested accounts
• Profiles with avatar, banner, bio, location and website
• Block, mute and report, applied across the feed
• Light and dark theme, with the design tokens ported from the web app
• 5 SQL migrations: schema, row-level security, functions, storage buckets, triggers

What is not included

• No paid tier. Apple requires in-app purchase for digital goods and takes 15 to 30 percent; Google Play Billing is equivalent. Both regimes changed materially in 2025 and 2026. The app reads subscription state if your backend sets it. It never sells anything.
• No push notifications. In-app and Realtime only. Push needs APNs and FCM credentials, which are per-app and cannot ship in a template.
• No GIF picker and no link previews. Both need a server to hide an API key or follow a URL. The hooks are shaped for a Supabase Edge Function; it is not built.
• No admin dashboard. Reports land in a table for you to build against.
• No automated test suite. There is an on-device verification screen and a manual checklist in AGENTS.md.
• No store submission. Icons, screenshots, privacy policy and review are yours.

What you will need

A Supabase project (the free tier covers development) and an Expo account. To ship, an Apple Developer account at 99 dollars a year and a Google Play account at 25 dollars once.

A Mac is not required to develop. The app runs in Expo Go rather than a native build, which is why FlatList is used over FlashList, and it targets the SDK the App Store currently ships rather than the newest one.

What was not verified

Android on physical hardware, tablets, older OS versions, and behaviour on a poor network. Block, report and avatar upload are confirmed at the data layer but have not been driven through the on-device UI. There is no automated test suite.

Documentation

AGENTS.md is an ordered runbook: every variable, dashboard step and verification check in order, with a failure-symptom table mapping each error string to its cause and fix. It is written to be followed by a coding agent or by hand. README.md is the reference.