Problem
Pickup games, league schedules, venue rules, group chats, gear needs, and student access all live in different places. Players cannot tell who is actually coming, and organizers do not have a clean operational layer.
Mobile-first sports community OS
Sports infrastructure for pickup games, intramurals, event feeds, campus communities, leagues, and trusted organizers.
A polished interactive demo for universities, rec departments, partners, and early investors. Most actions save locally in the browser while the production backend is still being built.
Local sports still run through scattered chats, stale calendars, unclear RSVPs, and uneven trust.
Playmo puts discovery, event feeds, chat, leagues, communities, reliability, and operator review in one mobile surface.
This shareable build is frontend/static, with local demo state and backend foundation work documented for the next phase.
What it solves
Pickup games, league schedules, venue rules, group chats, gear needs, and student access all live in different places. Players cannot tell who is actually coming, and organizers do not have a clean operational layer.
Playmo lets people find games, join leagues, post event updates, comment in the feed, chat with the group, coordinate gear, view venues, manage waitlists, and see whether a community or organization covers access.
Reputation signals, safety notes, organizer approval, closed communities, and admin queues make feeds and chats more serious than another open group thread.
Partner model
A campus, rec department, club network, company, or district can cover seats so members discover pickup, intramurals, and trusted groups inside a closed community.
League pages show organizer status, schedules, member access, sponsor coverage, and demo-only payment states before any production checkout or payout system exists.
The dashboard covers access requests, organizer approvals, safety review, demo finance previews, listing visibility, waitlist pressure, and venue readiness.
Prototype feature map
Browse nearby games by sport, place, community, skill, open spots, and personal availability.
Inspect venue details, lighting, surfaces, access notes, backup suitability, and saved preferred places.
Open game and league feeds for social posts, comments, local image attachments, and quick group or direct chat.
Request campus or organization access, filter by public or member communities, and show sponsor coverage.
Open league pages with schedules, verified organizer context, member counts, fees, and approval states.
Join waitlists, confirm attendance, report safety issues, review reputation, and track host readiness.
Preview paid league dues, sponsored seats, pending statuses, and future payment-provider boundaries.
Review access, safety notes, organizer requests, game visibility, league visibility, and venue readiness.
5-minute demo path
Start at the mobile demo app and skip or complete the short onboarding.
Use discovery, filters, availability, waitlists, and attendance confirmation.
Add a local post or comment, then open Chat Hub to choose a group or direct chat.
Open Central Rec Courts or another place to inspect readiness and access notes.
Review organizer trust, sponsor coverage, dues, and the prototype payment state.
Show reputation, campus license leads, community access, and organizer approval requests.
Use the dashboard for access requests, safety queue, demo finance previews, listing controls, and venue readiness.
Why now
Players already coordinate in chats and social threads, but those tools do not handle capacity, waitlists, venue context, reputation, payment status, or sponsor-backed access.
Universities and rec departments need lightweight ways to increase participation, make facilities more visible, and support safer student or member communities without building custom software.
Local organizers need a path from informal pickup to approved leagues, predictable dues, and clearer trust signals. Playmo can start as a focused local network and add backend depth later.
Ready to inspect it
The public root opens this overview first. The demo app is a static, local-state prototype at app.html.
Enter demo app