Aniconfigurator is made up of three parts: Studio, Server and Client
The studio is used for creating, viewing and updating all data and content needed to run the configurator client. The 3D-assets that will help you visualize your product are uploaded and managed here, along with scene and camera setups. This is also where all the product data is uploaded or created. For example, price, article number and article description, as well as article and price mapping. Last but not least, product rules are created and managed here.
This is the application visible to your customer; the interface where all data and content from the studio comes together to create the configurator. Our built-in template can be customized to fit your specific product and customer journey. The client is browser native, which means that it works on all devices and that no additional downloads are needed.
The server runs the database which stores all data needed by the studio and client application. System administration tasks can be executed here; like password changes. The database is running on .Net core with a Postgres database. Since we have our own server application, there are no external dependencies of content storing systems.
Rules are the definitions for how a product, or products, can be configured. They also decide in what way the product is visualized.
The information needed to present the product to the user, input for applying product rules and article information to compile a meaningful summary and output from the configurator.
Standardised API design for exchanging information between web application and server.
Models and materials used for visualizing the product.
The default database used by the server.
Framework used for the server application.
Curious on how Aniconfigurator can change your business?
Niclas will answer all your questions.
Niclas Kreuger
Director Business Development
