ShapeDiver API backend or frontend?

Hi,

I am working on a cabinet design that consists of n vertical separations and each section should have its own width and number of shelves. The number of vertical separations should be customizable (from 0 to …) + their position and thickness (every separation could have its own values). I made a simple sketch with 2 sections here

Clients want to add a drag and drop function for adding shelves like in this example. The number of shelves per vertical volume is independent, same for each shelf position and thickness, as well as door for each vertical volume

Since every vertical volume is independent with their own width, shelves and door options, it seems to me that I need to create several grasshopper definitions for each vertical volume that are integrated in one scene via ShapeDiver API?

In order to combine it, do I need a frontend or backend API? In other words is it possible to make in Designer+ licensing or Business plan ?

Thanks in advanced

There are multiple ways to implement this feature, from including most of the logic in one Grasshopper definition to loading in the same viewer sessions to several ShapeDiver models (or even the same ShapeDiver model multiple times with independent parameters). This depends on several factors including readbility of implementation, reusability of components and performance.

This can all be done with the viewer API (without the need for the backend API), therefore using a Designer+ license. However, consider that exporting production files might take much longer than typical computations, and that you might want to only trigger them when customers actually place an order. In that case, the backend API might prove to be very useful. This choice does not influence the implementation of your configurator so you could start with a Designer+ for the configurator phase of the implementation and decide further down the line if you need to upgrade to Business to access the backend API.