BETTER STREETS BAYSIDE · SERVICE CONCEPT

A local voice.
A shared space.

Better Streets Bayside could connect Council, local organisations and residents through one reviewed community publishing service. The app and website would draw from the same approved content.

01 · INTAKE

Groups send it in

An email address or website form accepts text, photos, organiser details and source links. The original submission is retained.

02 · PREPARATION

AI prepares a draft

Suggest a category, extract dates and locations, flag missing facts, check for duplicates and identify material that needs a closer look. Uncertain details stay uncertain.

03 · YOUR APPROVAL

Vincent reviews

A private queue shows the proposed post beside its sources and image permissions. Vincent edits, asks for clarification, declines or approves. AI cannot publish.

04 · PUBLICATION

One update, shared

The existing publishing workflow updates the website and app. A dated activity also goes to the calendar; news can appear in RSS.

This is the proposed operating model. Inbox intake, uploads, AI processing and a private approval queue have not been connected to this demonstration.

Give each kind of content a home

News & activities

Useful Council and neighbourhood updates sit in News. Activities contains local walking and cycling routes plus running and volunteering opportunities. What’s on is the separate calendar for confirmed dates, meeting points, cost and joining details.

Groups & community

Group profiles help people find running clubs, family playhouses, cycling clubs and nature volunteers. Community is a simple local community feed for questions, ideas and replies. Organisation announcements continue through News and What’s on.

Local discussion, with a named moderator

The Community prototype uses clearly labelled example threads, Like and Comment actions and private post drafts. Posts and replies support photos, screenshots and flyer images, optional captions and preview/removal before saving. Demo text and photo attachments stay on the device; there are no public accounts or live discussions. Facebook sources can continue to contribute research leads without becoming an embedded social feed.

Before discussions go live, appoint a moderator and connect authenticated accounts, a review queue, reporting, blocking and published contact details. New discussions need moderator approval. The prototype’s report screen does not send a report. Apple’s requirements for user-generated content ↗

Design references checked in Mobbin

Apple News: a useful editorial home ↗
Meetup: activity categories, dates and discovery ↗
Nextdoor: local publisher and community updates ↗

These are iOS interface references. Mobbin does not establish which implementation language each app uses; our sample is built in SwiftUI.