I’ve come up empty-handed on one of these topics, and with sub-optimal solutions on the other after digging through tutorials and community threads.
The 1st problem: I have a ticketing app. My customer would like to purchase 5 tickets - 2 adult, and 3 child tickets. Currently, it seems like you have to tap the “buy” button 5 individual times to add 5 of them to the cart, and you’d have to navigate to entirely different products to differentiate between “adult” and “child” ticket options.
Possible solution: It would be much easier for them to choose ticket quantity or ticket type (adult, child, fastpass, “backstage pass”, etc) using a number picker and a general selection picker. These selections would also need to be passed along the purchase + processing flows to the backend for logging. Maybe a “Product” type Component would help focus the options? I could see a general “picker” being useful in ton of other product scenarios, as well. - Size options for clothes, as just one example.
The 2nd problem: I only have x capacity and therefore x available tickets to sell per night. Even basic inventory management is proving overly complex. Subtracting one ticket from my total upon purchase, or even upon adding it to the cart would help me avoid over-selling tickets.
Possible solution: Allow me to set inventory, and easily access the “App:Sales” tab within Glide to subtract purchases from that inventory.
In case more context is needed: I build a yearly Haunted House for my community, and I’m looking for fun and useful ways to leverage a companion app that my patrons will enjoy. It’s normally 100% free and visitors simply queue up, but this year, they need to reserve a time slot and purchase PPE to safely enter + “infiltrate the mad scientist’s lab”
A rough, unfinished 1-day effort on the ticketing portion: https://prismhaunt.glideapp.io/