Current/Problem Process Flow
1. Business owner decides on music setup
2. Owner chooses: Hire DJ (expensive), Simple playlist (no customization), or Manual requests (time-consuming)
3. If manual requests: Staff must interrupt workflow to handle requests
4. Customers have no way to influence the atmosphere
5. Owner misses potential revenue and engagement opportunities
Solution Process Flow
1. Business owner signs up for VibeQueue subscription
2. Owner sets up QR codes at tables/devices
3. Customer scans QR code to access song request interface
4. Customer browses/searches songs via Spotify API
5. Song is added to queue (subject to owner's filters)
6. SoundMachine plays licensed music in venue
7. Owner manages everything via Business Control Center
Major Functional Components Diagram (MFCD)
Prototype Major Functional Components Diagram (MFCD)
Competition Matrix
| Revenue Share | Hardware Agnostic | Customer Song Selection | App or Machine Required | |
|---|---|---|---|---|
| Vibe Queue | 67% | ✔ | ✔ | |
| TouchTunes | 33-39% | ✔ | ✔ | |
| Rockbot | 0% | ✔ | ✔ |
Risk Matrix
Feature Table
| Category | Feature | Customer | Staff | Owner | RWP | Prototype (Planned) |
|---|---|---|---|---|---|---|
| Account | Account Creation | ✔ | ✔ | ✔ | Creation of user accounts | Fully Implemented |
| Account | Login | ✔ | ✔ | ✔ | Login screen and authorization | Fully Implemented |
| Account | Payment Processing | ✔ | ✔ | ✔ | Payment processing through Stripe API | Partially Implemented |
| Song Queue | Song Selection | ✔ | ✔ | ✔ | Song selection from list | Fully Implemented |
| Song Queue | Vibe Engine | ✔ | ✔ | ✔ | Song recommendations based on venue music preferences | Fully Implemented |
| Song Queue | Priority Boost | ✔ | ✔ | ✔ | One or more tiers that push the request higher in the queue | Partially Implemented |
| Song Queue | Block Songs (Queue Override) | ✔ | ✔ | Prevent songs that don’t fit the vibe from playing | Fully Implemented | |
| Venue | Blacklist Song/Genre | ✔ | Choose which genres or moods to block from being playable | Fully Implemented | ||
| Venue | View Revenue | ✔ | Live tracking of revenue from song requests | Partially Implemented |
Algorithms
Database Schema
UX Mockups
Customer Song Request Interface
Business Control Center Dashboard
Dependencies
| Libraries | Tools | Technology |
|---|---|---|
| Django REST Framework | VS Code | Soundcharts API |
| Stripe Python Library | GitHub | SoundMachine |
| Django Channels | GitHub Actions | Stripe QR Mobile Payment |
| Requests | Docker | Web Server |
| PostgreSQL | Django(Python) |
What It Will Do
- Easy Access & Song Selection
- QR Code Access
- Song Browsing & Requests
- Influence the Atmosphere
- Provide Owner & Staff Control
- The "Business Control Center"
- Dynamic Vibe Moderation
- User Management
- Generate a Revenue Stream
- Pay-to-Request
- Automated Payment Processing
- Profit Sharing
- Ensure Legal Compliance
- Hardware Agnostic
- Licensed Streaming
What It Will NOT Do
- Play Music Without Licensing
- VibeQueue will not play any music that the business owner does not have the proper licensing to play
- Generate New Music
- VibeQueue will not generate custom songs for customers at this time
Interfaces
