Deploy and Optimize TuneQueue Platform - 25/08/2026 10:32 EDT

TuneQueue is currently a working prototype built in Replit for managing song requests and DJ queues at a single venue.
I need an experienced developer to take the existing TuneQueue codebase and turn it into a real, scalable commercial product.
The main problem
The current version is essentially designed around one venue. The architecture needs to be changed so TuneQueue can support many independent venues simultaneously.
Each venue needs its own:
Account/workspace
Users and staff
DJ/queue
Spotify connection
Settings
Customers/song requests
Subscription/billing status
Data
Data must be completely isolated between venues.
SaaS / subscriptions
TuneQueue needs to become a subscription-based SaaS product.
I need:
Subscription plans
Monthly/yearly billing
Online payment
Automatic subscription status
Trial period if appropriate
Upgrade/downgrade
Cancellation
Payment failure handling
Access restrictions when a subscription expires
Customer billing management
The architecture should make it possible to introduce different pricing tiers later.
Scalability
The application needs to be designed so that going from:
1 venue → 10 venues → 100 venues → 1,000+ venues
doesn't require rebuilding the application.
I need the developer to review the current architecture and identify anything that would prevent this from scaling, particularly:
Database architecture
Authentication
Tenant isolation
API architecture
Spotify OAuth/token storage
Backend state
Concurrent queue usage
Real-time updates
Caching
Hosting/deployment
Background jobs where necessary
The existing prototype currently has application state stored in memory, which is not suitable for a multi-venue production system. This needs to be replaced with proper persistent infrastructure.
Spotify
Spotify integration is a core part of TuneQueue.
Each venue should be able to connect its own Spotify account securely.
Spotify authentication/token storage therefore needs to be designed around multiple independent venues, rather than one global Spotify connection.
Mobile application / App Store
The final product needs to become a real mobile application distributed through the Apple App Store and Google Play Store.
I don't necessarily want the existing application completely rewritten.
The developer should determine the best approach for turning the existing frontend/backend into a mobile product, potentially using a technology such as React Native/Expo or another appropriate solution.
The mobile app should use the same production backend/API and support the TuneQueue functionality required by users and DJs.
I need:
Android app
iOS app
App Store submission preparation
Google Play submission preparation
Production builds
App icons/splash screens/basic store requirements
Secure authentication
Connection to the production TuneQueue backend
What I want from the developer
I already have a working prototype and don't want to start from zero.
The job is to:
Audit → Refactor → Productionize → Scale → Monetize → Mobile
I want the developer to reuse as much of the existing code as makes sense while replacing prototype-level architecture where necessary.
The end result should be a commercially viable TuneQueue platform where multiple venues can independently sign up, subscribe, connect Spotify, manage their queues, and use TuneQueue through web and mobile apps.
Priority: Get the existing prototype out of Replit and establish the production architecture as quickly as possible, while making sure the architecture doesn't need to be rebuilt again when the number of venues grows.