Search for a command to run...
A customer sees a bundle directory as a simple page. Maybe it contains: All Bundles [ Search ] Sort: Newest ┌─────────┐ ┌─────────┐ ┌─────────┐ │ Bundle │ │ Bundle │ │ Bundle │ └─────────┘ └────
Subscription-based Shopify apps eventually face an important architectural question: Where should feature access be enforced? A bundle-builder application may have several plans. One merchant may have
A Shopify application can become difficult to maintain when unrelated responsibilities are stored and handled together. A bundle-builder application is a good example. At first, the data model seems s
A storefront listing page does not need thousands of records to become slow. Sometimes the problem is not the amount of data. It is how the data is requested, transferred, filtered, sorted, and render
A bundle-builder app usually has two very different sides. The first side is the merchant experience. Merchants create bundles, configure designs, manage products, and control how bundles behave. The
Shopify apps often have multiple plans. A bundle-builder application is no different. One merchant might have access to advanced bundle rules, while another might only have access to basic bundle func
A bundle builder becomes much more interesting when the price changes as the customer adds more products. For example: 2 items → Regular price 3 items → 5% off 5 items → 10% off 8 items → 15% off
There is a dangerous assumption in many bundle builders: If a product was available when the page loaded, it will still be available when the customer clicks Add to Cart. That assumption is unsafe.
A build-your-own-bundle page looks like a collection of product cards. Underneath those cards, it is really a state machine. The customer moves from one step to another, selections change available ac
