AGrouped & labelled
Keep everything on one page but in clearly-titled grouped cards (iOS-settings rhythm): About · Members · Admin · Content · Notifications · Danger. Admin rows sit under an ADMIN-tagged group, not scattered. Opaque labels get a current-value ("Who can interact · Reactions").
📢
Village Notice Board ✔
@village_notice
Channel · Public · 1 member
f◎🌐▶
Channel settingsADMIN
⟲
Who can interact
Reactions
›
Notifications
🔔
Mute channeltap to customize per-type
✔ every row keeps its place but is grouped + titled · opaque "Interaction" → "Who can interact · Reactions" · restores granular mute · danger zone isolated · RULE (owner 2026-07-02): Info = identity + frequent-use — @username shown under the logo (same as header/share/all major places, tap = copy link) and Add members / Join requests / Share stay HERE; Manage = configuration (Username EDIT row lives there)
BManage-screen split ★ rec
The info page becomes calm & identical for everyone: identity, actions, members, shared content, danger. Every admin control moves behind a single ⚙ Manage channel button → a dedicated admin screen. Kills the "list swings by role" smell — members never see admin clutter.
📢
Village Notice Board ✔
@village_notice
Channel · Public · 1 member
Official notices for the village — events, alerts & updates. more
f◎🌐▶
⚙ Manage channel ›
✔ member view is short & identical for all · admin power = one button → focused screen (next frame) · role-conditional list gone
B· the Manage screen
Behind ⚙ Manage channel — every admin/owner control in one focused place, grouped & labelled, with the semi-destructive Visibility change clearly flagged. This is where the role-conditional complexity goes to live, off the member path.
Profile
✎
Edit name, photo & description
›
@
Usernamenyburs.com/channel/…
@bjp_kurhani
›
Posting & interaction
⟲
Who can interactreactions · comments · broadcast
Reactions
›
Discovery
🏷
Categorywhere your channel shows in discovery
Politics
›
⚠
Switch to private channel
›
✔ surfaces latent slow-mode · "Switch to private" reads as a flagged action, not a benign row · group mode swaps "Who can interact" → "Only admins can post" · NEW (2026-07-02): every admin control in ONE place — Username (@handle edit exists but was buried inside Edit-channel; row deep-links to the same sheet, shows the current handle) · Channel rules (exists in create/edit; now visible with Set/— value) · Discovery: Category & Location (were pick-once-at-create, no edit path; category change re-indexes discovery) · Banned users (ban/unban API exists with NO list surface in the app) · Join requests stays on Channel Info too (both entry points, same queue)
Every current feature is preserved — here's the mapping (nothing lost; the dead
GroupSettingsPage is retired but its
granular notifications are restored as "customize mute"):
| Today | A · grouped | B · manage-split (recommended) |
|---|
| QR (channel) | nav right | nav right |
| Mute / Search / Add / Share | action row (Add=admin) | action row · Add moves into Manage |
| Edit profile (admin) | Admin group | Manage › Profile |
| Interaction = Reactions (ch) | "Who can interact · Reactions" | Manage › Posting |
| Only-admins-post (group) | Admin group (group mode) | Manage › Posting (group mode) |
| Approval required (public) | Admin group toggle | Manage › Access |
| Switch private/public (owner) | "Visibility ›" | Manage › flagged danger row |
| Media / Links / Requests | Content group | Shared (Media/Links) · Requests→Manage |
| Members (5 + see all, roles, ⋯) | Members group | Members group (unchanged) |
| Exit / Delete | Danger group | Danger group |
| (latent: slow mode, proximity) | — | Manage › Posting (slow mode surfaced) |
Fixes applied to today's complexity smells (all options)
de-dupe the
two member-search entries into one · clarify
"Interaction" with its value · isolate the
danger zone · drop
dead Proximity / Live-stream / block-restrict scaffolding · restore
granular notifications.
My recommendation
Option B (Manage-screen split). It attacks the root cause: today the page is a different length and shape for every role, which is why it "feels complex." B gives
every viewer the same calm info page and pushes all role-conditional power into one focused Manage screen — the enterprise pattern (Slack, Discord, Telegram admin panels all do this). A is the lower-effort middle ground if you'd rather keep one scroll. Tell me B, A, or a mix → I build it in Flutter and we validate the same way we did the header.