Got an idea?

Tell us how we could make the product more useful to you.

In Progress

CALENDAR PAGE

What do you want: A dedicated Calendar page inside the Sonority app where all time-based data lives in one place β€” upcoming gigs, maintenance due dates, repair bookings, tour windows, instrument loan return dates, and insurance renewal reminders. Events should link directly to instruments in the inventory, so tapping an event opens the relevant gear record. The calendar should support month, week, and agenda list views, and allow manual event creation alongside events auto-populated by other Sonority features (Tour Prep, maintenance logs, repair bookings). Who does it help: All tiers β€” bedroom players who need maintenance reminders (GARAGE) through to touring professionals managing multi-city schedules and instrument logistics (TOUR). Roadies and techs with shared access benefit especially from a synced team calendar view. Current workaround: Users manually track gigs, maintenance intervals, and repair appointments in Apple or Google Calendar with zero connection to instrument data. Maintenance logs inside Sonority are historical only β€” no future reminders are generated. Tour prep dates live in the Tour Prep component with no visual calendar context. Everything is siloed. Mockup or example: Similar to how a standard calendar app looks, but with colour-coded event types per category (gigs, maintenance, repairs, tours) and each event tapping through to the linked instrument record in inventory.

Richard Jenkins 15 days ago

πŸ’‘

For Musicians

Completed

GOOGLE LOGIN

Feature Title: Google Login (Sign in with Google) What do you want: Allow users to sign in to Sonority using their existing Google account via OAuth 2.0. A "Sign in with Google" button on the login and registration screens would authenticate users instantly, without needing to create a separate email/password credential. Who does it help: All users β€” Musicians, Makers, Touring Pros, and Studios. Especially valuable for new users during onboarding, reducing friction at the sign-up stage and increasing conversion. Returning users benefit from one-tap access without remembering a password. Current workaround: Users must manually create and remember a separate Sonority email/password combination, or use a password manager. There is no social login shortcut currently available. Mockup or example: (optional) Reference: accounts.google.com/signin β€” standard "Sign in with Google" button (white pill button with Google logo). Common implementation examples: Spotify, Reverb, Bandcamp onboarding flows.

Richard Jenkins 29 days ago

πŸ’‘

For Musicians

In Progress

Auto Scene Generator (Pro)

Short description Sonority automatically turns your gear photos into clean, professional β€œstudio” shots. Upload a front photo of your instrument and we centre it, remove the background, and place it on a dark, premium background so your collection looks consistent and stage‑ready. How it works Works across popular instruments Guitar, bass, drums, microphones, amps, pedals and more all use the same automatic scene styling. Automatic pro look When you add an instrument and upload a photo, Sonority: detects the main instrument, centres it with room to breathe, removes busy backgrounds, places it on a dark gradient or studio‑style backdrop so it looks like a product or promo shot. Background styles Free members: a set of clean, basic gradient backgrounds to keep things tidy. Pro members: full access to advanced gradients, Sonority‑branded looks, and studio or stage scenes, with more themed packs coming in future. In‑flow preview While adding an instrument, you can flip through background styles and see the scene update instantly before saving it to your collection. Why it’s useful Your whole collection feels curated and professional, without needing photo‑editing skills. Perfect for showing your rig to collaborators, sharing your vault, or preparing visuals for touring and listings.

Richard Jenkins about 1 month ago

πŸ’‘

For Musicians

Stage plots / layouts builder

Problem statement Right now, Sonority helps track instruments, tours, and tech details, but it does not give musicians and touring crews a native way to design clear, reusable stage layouts tied directly to their actual gear. Most bands and tour managers fall back to ad‑hoc tools (PowerPoint, Canva, PDFs, hand sketches, scattered files) that live outside their main inventory and tour workflow. This creates inconsistent stage plots from venue to venue, makes it easy for details to go out of date as rigs change, and forces engineers and backline to interpret messy or incomplete information on the day of the show. Because those plots are disconnected from the inventory, any change in instruments, players, or setups has to be manually reflected in multiple files, increasing the risk of errors, duplicated work, and miscommunication between artists, crew, and venues. For touring acts juggling multiple configurations (fly dates vs full production, festival stages vs club shows), maintaining separate static plots becomes especially painful and error‑prone. Proposed feature Add a visual stage plots / layouts builder inside Sonority that lets users design, save, and adjust stage layouts using instruments and rigs already stored in their inventory. Users would drag and drop players, mics, amps, pedalboards, keys, drum risers, wedges/IEM packs, stands, and power drops onto a grid‑based canvas, with labels and metadata auto‑filled from their existing Sonority items (instrument name, player, notes). Each stage plot would be linked to a tour, date/venue, or configuration (for example β€œFull band”, β€œFly rig”, β€œFestival set”), so users can quickly clone and tweak layouts instead of rebuilding from scratch. The builder would include snap‑to‑grid and alignment tools, plus templates for common setups such as solo acoustic, 3‑piece, 5‑piece, and festival stage, to speed up creation. Users could export plots as PDF or PNG, with optional tech notes like input lists, patch notes, and power requirements, ready to send to venues, engineers, and backline. What this feature would solve - Centralises stage plots in the same place as instrument inventory, tour prep, and documentation, reducing duplicated work and keeping everything in sync when gear changes. - Improves clarity for venues, FOH and monitor engineers, and backline by producing clean, consistent, standardised layouts per show or tour. - Speeds up tour preparation, especially for acts with multiple configurations, by allowing users to clone, version, and adjust existing plots instead of re‑creating them in separate tools. - Strengthens Sonority as a single source of truth for gear lists, weights, maintenance status, and stage layouts inside the same tour pack export.

Richard Jenkins about 1 month ago

1
🏟️

For Venues

Foldback / In-Ear Mix Builder

What do you want: Add a foldback / in-ear mix builder that lets users create and save personal monitor mix presets using an ADSR-style slider interface. Each musician (or their tech) can define where key instruments sit in their in-ear or foldback mix (for example, guitar position in the stereo field and its overall level as β€œgenerally louder” or β€œgenerally quieter”). These settings should be savable as reusable presets so a musician’s preferred monitoring layout can be recalled quickly across rehearsals, shows, or tours. Who does it help: - Musicians using in-ears or wedges who want consistent, personalized monitor mixes. - Touring pros and techs who need to quickly recall or deploy known in-ear mixes for different players. Current workaround: Right now, musicians and techs have to rebuild monitor mixes manually on consoles or apps for each show, relying on notes, console scenes, or memory rather than stored preference-based presets tied to the musician. Mockup or example: An β€œIn-Ear Mix Presets” screen where each instrument (guitar, vocals, click, tracks, etc.) has an ADSR-style control or simple level/position sliders. A user can tap β€œSave as preset,” name it (e.g. β€œSam – Festival IEM mix”), and recall it later or share it with a tech profile. Would you like this phrased more technically (for devs) or more simply (for musicians read ing the portal)?

Richard Jenkins about 2 months ago

🚌

For Touring

Completed

DISCORD LOGIN

Ability for users to use their Discord credentials to sign up/in to Discord. Here’s that version, cleaned up for public-facing use: Problem Many Sonority users are already active on Discord and expect to use their existing Discord account to access new music tools and communities. Having to create and manage a separate Sonority password adds friction, increases drop-off at signup, and creates yet another set of credentials for users to maintain. Proposed solution Add Discord as a social login option alongside existing authentication methods, allowing users to sign up and sign in with their Discord account in one click. This would use Discord’s OAuth2 flow (for example, identify and email scopes where available) to create or link a Sonority account, and then log the user in automatically on subsequent visits. Why this is valuable Reduced friction at signup for Discord-native musicians, techs and community members, leading to higher conversion and activation. Fewer passwords for users to remember, improving both security and user experience. Tighter alignment with Sonority’s existing Discord community and bots, making it easier to connect in‑app identities with Discord roles and channels in future. High-level acceptance criteria β€œContinue with Discord” button is available on both Sign up and Log in screens. New users can create a Sonority account using Discord OAuth (no separate password required), with basic profile data (name, avatar, email) pulled from Discord where possible. Existing Sonority users can link and unlink their Discord account from their profile/settings, and then use Discord to log in. Clear error handling if Discord authorization fails or is cancelled, with a simple way to retry or fall back to email login.

Richard Jenkins about 2 months ago

2
πŸ’‘

For Musicians