Client SDKs render live seating inventory, manage selection, and create temporary holds. They do not replace your trusted checkout, payment, order, ticketing, refund, or fulfilment systems.
Choose a platform
Web application
Compare JavaScript, React, Vue, and Angular. Use the complete picker or compose a custom browser experience from the lower-level chart API.
Native app SDKs
Compare Flutter, React Native, iOS, and Android, including ready-made, customizable, composable, and raw-map integration levels.
Choose how much UI you own
| Surface | Choose it when | Your application owns |
|---|---|---|
SeatPicker |
You want the standard buyer selection and confirmation flow | Checkout, payment, commercial order, tickets, and fulfilment |
SeatingChart |
You need your own cart, layout, or hold controls | Buyer chrome, explicit hold lifecycle, checkout, and fulfilment |
| Native mobile SDK | The buyer journey belongs inside a mobile application | App navigation, platform lifecycle, checkout, and fulfilment |
| Performance Group picker | One atomic selection spans several performances | Checkout and fulfilment for the group handoff |
| Season picker | Buyers choose renewable fixed inventory across a Season | Season commerce, payment, and fulfilment after handoff |
Complete the trusted half
Every client path ends at the same boundary: pass the opaque hold identity to a trusted backend, inspect it there, and commit booking only after your own order or payment decision. Choose a server SDK or use the REST API directly.
If you have not chosen the inventory model yet, compare Events, Performance Groups, and Seasons.