Roadmap

7 May 2026

Simuze is built in the open, one piece at a time. This page is the honest version: what is built and usable, what is still thin, and what comes next. No marketing tense.

Built (structural)

Platform

  • Custom Modular stack powering the public site and the admin back office from one codebase
  • Unified routing for pages, posts, albums, tracks, playlists, events, and mixed archives
  • Re-runnable database schema as the single source of truth (idempotent, no migration sprawl)
  • Shared template, escaping, URL, and database helpers across the whole front-end
  • SEO foundations: sitemap endpoint and metadata hooks ready for the URL set as it grows

Identity & payments

  • Token-based session model with login, signup, forgot-password, and account management
  • Server-side auth proxy so the checkout and embed surfaces work the same on staging and production
  • Signed payment webhook updating purchase state in Simuze
  • Per-user and per-group payment settings, including a connectivity self-test for sellers

Community

  • Users, groups, activity, messages, friends, follows, reviews, and reports as first-class objects
  • Admin tooling for shows, cities, groups, group types, reviews, reports, messages, activity, and settings
  • Built-in export/import for community data

Groups & profiles

  • Group types: artist, label, venue, city, province, country, fanbase
  • Public group pages with a tabbed dashboard: overview, music, discography, artists, members, activity, shows, settings, invites, sales (where applicable)
  • Group creation wizard and group settings (handles, visibility, payment hooks)
  • Public profile pages with a full dashboard: home, playlists, activity, friends, groups, messages, shows, uploads, purchases, payment settings, profile settings
  • Header image upload and a cached avatar pipeline with sensible fallbacks
  • Internal API for messaging, user search, group updates, payment settings, and header uploads

Music & playlists

  • Albums, tracks, artwork, and lifecycle handled by a single music layer
  • Upload flow for audio and metadata, both on profiles and inside groups
  • Public music discovery: music hub, albums, tracks, singles, and latest releases on the homepage
  • Group music manager and public discography
  • User playlists: create, edit, reorder, add and remove tracks, and public playlist pages
  • Lightweight artist embed for use on external sites
  • Admin-side music tools for moderation and fixes

Commerce

  • Purchase and download flow with access pages, success and cancel paths
  • User purchase history and group-facing sales views
  • Webhook-driven order completion and follow-up actions
  • Server-side audio conversion step for deliverables
  • Seller dashboard template for keeping an eye on orders

Shows, events & ticketing

  • Events as first-class objects with venues, line-ups, and categories (concerts, festivals, tours)
  • Show listing, add, and edit flows
  • Ticketing service with pending orders and a clean hand-off to checkout
  • User ticket history and an organiser dashboard per show: guestlist, attendance, comments, line-up tools
  • Event comments, attendance toggles, and guestlist entry helpers

Social: activity, board, messaging

  • Activity feed and per-user activity tab
  • Community board with multiple post types (open slots, looking-for-band, requests, etc.) and inline compose
  • Direct messaging with threads, @mentions, read state, and inline compose
  • Welcome thread from Simuze for every new account

Discovery & geography

  • Live agenda with filters for country, province, city, genre, following, and event type
  • Network hub linking out into cities, countries, groups, genres, and playlists
  • Archive and letter-index pages for cities, countries, groups, playlists, and genres
  • Location avatars and geo helpers for place-type groups
  • Show matching and a venue layer behind event data

Editorial & trust

  • Weblog with listing, single-post layout, and structured post bodies
  • Static pages for About, FAQ, How-to, Roadmap, and Feedback
  • Feedback form with proof-of-work captcha that mails the team
  • User reviews and abuse reports with admin review queues
  • Privacy guards so email addresses never leak into public views or APIs

Design & front-end

  • House style across layout, components, hero, forms, and community-specific UI
  • Responsive dashboard layout shared by profiles and groups (sticky nav, chapter blocks, playful cards)
  • Homepage with network context, board preview, and release grids
  • Store and subscription page layouts in place, ready to plug deeper services into

Next (product & go-live)

  • Staging continuously deployed; structured testing with real users and musicians
  • Feedback from those sessions folded back into priorities and bug fixes
  • Production cutover to simuze.com once staging is stable enough to promise uptime
  • End-to-end payments test passes in production-like config; edge cases, refunds, and reconciliation hardened
  • End-to-end ticketing test passes (purchase, check-in, cancellations); organiser and buyer flows tightened
  • Post-launch iteration: clearer group payouts, statements, and sales analytics for sellers
  • Simuze apps for mobile and desktop with reliable playback, offline queues where feasible, and playlists as first-class objects
  • Subscriptions inside Simuze for streaming-style access to playlists and artist catalogs, with billing, entitlements, and fair payout rules
  • Musician store beyond digital music: merch, bundles, and inventory-aware fulfilment
  • Rozuro (or equivalent) integration so artist identity, credits, and rights metadata stay in sync for artists who already live there
  • More day-job tooling for musicians: tour routing, contract and checklist templates, promo assets, deeper stats, anything that shortens the gap between making music and running the business
  • Global search across people, groups, cities, genres, events, and posts
  • Notifications people actually want: digests, replies, follows, ticket reminders (email first, push later)
  • iCal and calendar subscribe links per user for their shows
  • Translations: Dutch and English at minimum
  • Public radio or curated always-on streams built on the same catalog
  • Fully populated sitemap and structured data once URLs stabilise

Missing something you need? Send feedback.