Backend API & Database for Ticketing App
Budget: ₹600 – ₹1,500 INR
Project: Backend & API for “Marquee” — Movie & Event Ticketing App (Phase 1 of 2)
Summary
I have a working frontend prototype (HTML/CSS/JS) of a movie + event ticketing app — similar in concept to BookMyShow / District — with mock data and no backend. I need a developer to build the real backend, database, and API so the app uses live data instead of hardcoded mock data, then connect my existing frontend to it.
This is Phase 1 of a larger project. Phase 2 (native iOS/Android apps) will be posted separately once Phase 1 is delivered and budget is allocated for it — please scope your Phase 1 quote on backend + web only.
What already exists
• A working frontend prototype (HTML/CSS/JS, ~3 files) covering: movie browsing/filtering, showtime selection, interactive seat map, event browsing, ticket tier selection, a mock checkout flow, and a booking confirmation screen.
• All current data (movies, cinemas, events, seat availability) is hardcoded mock data with no persistence.
• I’ll share the prototype files with whoever I hire so they can see exactly what needs real data behind it.
Phase 1 scope (this posting)
1. Database design for: movies, cinemas/screens, showtimes, seat inventory, events, venues, ticket tiers, users, bookings/orders.
2. Backend API (REST or GraphQL — your recommendation) covering:
• List/search/filter movies and events
• Get showtimes by movie/cinema/date
• Get seat map + live seat availability for a showtime
• Lock/reserve seats during checkout (prevent double-booking)
• Create a booking/order record
• Basic user accounts (signup/login, view “my bookings”)
3. Payment integration: one gateway suited to my region (e.g. Razorpay or Stripe) — checkout creates a real payment intent; sandbox/test mode is fine for now.
4. Connect my existing frontend to the new API (replace the mock data calls with real ones). I’m flexible if you’d rather rebuild the frontend in a framework (React/Vue) instead of keeping plain JS — open to your recommendation if it speeds things up within budget.
5. Basic admin capability to add/edit movies, showtimes, and events (an admin panel UI, or even a simple authenticated set of endpoints I can use via Postman, is acceptable for this phase).
6. Deployment: get the backend + database + connected frontend live on a low-cost host (e.g. Render, Railway, Fly.io, or similar) so I can access and test it via a URL.
Out of scope for Phase 1 (will be Phase 2)
• Native iOS/Android apps
• Advanced features: reviews/ratings, push notifications, loyalty points, dynamic pricing, multi-city scaling, analytics dashboards
Tech stack
Open to your recommendation, but I’d lean toward something common and well-supported for easy handoff later, e.g.:
• Backend: Node.js (Express/Fastify) or Python (FastAPI/Django)
• Database: PostgreSQL or MySQL
• Hosting: Render/Railway/Fly.io (low-cost tiers acceptable)
If you have a stack you’re strongest in that fits these needs, say so in your proposal — I care more about a working, maintainable result than a specific stack.
Budget & terms
• Hourly, with a not-to-exceed cap of $1,000 total for Phase 1 as scoped above.
• Please give your hourly rate and an estimated hours range in your proposal so I can see how the cap maps to scope — if full scope doesn’t fit the cap, tell me what you’d trim or phase instead of underbidding.
• Payment via Freelancer milestones, released on agreed checkpoints (see below).
Suggested milestones
1. Database schema + API skeleton running locally — demo via Postman
2. Seat locking + booking creation working end-to-end (test data)
3. Payment gateway integrated in sandbox mode
4. Frontend connected to live API, deployed to a public URL
5. Basic admin access for adding movies/events
What to include in your proposal
• Relevant past work: links to similar booking/e-commerce/inventory systems you’ve built
• Your recommended stack and why
• A realistic hours estimate against the $1,000 cap, and what (if anything) you’d suggest cutting to fit it
• Your availability/timezone overlap with me
Timeline
Open to your estimate, but I’d like a working local demo within 2–3 weeks of starting.
Summary
I have a working frontend prototype (HTML/CSS/JS) of a movie + event ticketing app — similar in concept to BookMyShow / District — with mock data and no backend. I need a developer to build the real backend, database, and API so the app uses live data instead of hardcoded mock data, then connect my existing frontend to it.
This is Phase 1 of a larger project. Phase 2 (native iOS/Android apps) will be posted separately once Phase 1 is delivered and budget is allocated for it — please scope your Phase 1 quote on backend + web only.
What already exists
• A working frontend prototype (HTML/CSS/JS, ~3 files) covering: movie browsing/filtering, showtime selection, interactive seat map, event browsing, ticket tier selection, a mock checkout flow, and a booking confirmation screen.
• All current data (movies, cinemas, events, seat availability) is hardcoded mock data with no persistence.
• I’ll share the prototype files with whoever I hire so they can see exactly what needs real data behind it.
Phase 1 scope (this posting)
1. Database design for: movies, cinemas/screens, showtimes, seat inventory, events, venues, ticket tiers, users, bookings/orders.
2. Backend API (REST or GraphQL — your recommendation) covering:
• List/search/filter movies and events
• Get showtimes by movie/cinema/date
• Get seat map + live seat availability for a showtime
• Lock/reserve seats during checkout (prevent double-booking)
• Create a booking/order record
• Basic user accounts (signup/login, view “my bookings”)
3. Payment integration: one gateway suited to my region (e.g. Razorpay or Stripe) — checkout creates a real payment intent; sandbox/test mode is fine for now.
4. Connect my existing frontend to the new API (replace the mock data calls with real ones). I’m flexible if you’d rather rebuild the frontend in a framework (React/Vue) instead of keeping plain JS — open to your recommendation if it speeds things up within budget.
5. Basic admin capability to add/edit movies, showtimes, and events (an admin panel UI, or even a simple authenticated set of endpoints I can use via Postman, is acceptable for this phase).
6. Deployment: get the backend + database + connected frontend live on a low-cost host (e.g. Render, Railway, Fly.io, or similar) so I can access and test it via a URL.
Out of scope for Phase 1 (will be Phase 2)
• Native iOS/Android apps
• Advanced features: reviews/ratings, push notifications, loyalty points, dynamic pricing, multi-city scaling, analytics dashboards
Tech stack
Open to your recommendation, but I’d lean toward something common and well-supported for easy handoff later, e.g.:
• Backend: Node.js (Express/Fastify) or Python (FastAPI/Django)
• Database: PostgreSQL or MySQL
• Hosting: Render/Railway/Fly.io (low-cost tiers acceptable)
If you have a stack you’re strongest in that fits these needs, say so in your proposal — I care more about a working, maintainable result than a specific stack.
Budget & terms
• Hourly, with a not-to-exceed cap of $1,000 total for Phase 1 as scoped above.
• Please give your hourly rate and an estimated hours range in your proposal so I can see how the cap maps to scope — if full scope doesn’t fit the cap, tell me what you’d trim or phase instead of underbidding.
• Payment via Freelancer milestones, released on agreed checkpoints (see below).
Suggested milestones
1. Database schema + API skeleton running locally — demo via Postman
2. Seat locking + booking creation working end-to-end (test data)
3. Payment gateway integrated in sandbox mode
4. Frontend connected to live API, deployed to a public URL
5. Basic admin access for adding movies/events
What to include in your proposal
• Relevant past work: links to similar booking/e-commerce/inventory systems you’ve built
• Your recommended stack and why
• A realistic hours estimate against the $1,000 cap, and what (if anything) you’d suggest cutting to fit it
• Your availability/timezone overlap with me
Timeline
Open to your estimate, but I’d like a working local demo within 2–3 weeks of starting.