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.
This page narrows the choice to the client side. To compare client SDKs with server SDKs and REST, start at Choose an SDK or API.
Choose a platform
Web application
Compare JavaScript, React, Vue, and Angular, and choose
between the ready-made SeatPicker and the map-only SeatingChart.
Native app SDKs
Compare Flutter, React Native, iOS, and Android and the four levels of buyer UI your app can own.
Choose the buyer component for your inventory model
| Inventory model | Buyer component | Platforms |
|---|---|---|
| One dated Event | SeatPicker or SeatingChart on the web; the native picker in an app |
Web and native |
| A Performance Group: one atomic selection across several performances | Performance Group picker | Web only |
| A Fixed Renewable Season: the same seats across a renewable Plan | Season picker | Web only |
If you have not chosen the inventory model yet, compare Events, Performance Groups, and Seasons.
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.