Can you use AIO components in an AIO component?

Hi everyone!

I am facing the same issues as those raised in here or here Improving on All-in-One (AIO) components. In short: I need to make some (ideally nested) components reusable in a multi-page app. More precisely, I need to duplicate a pretty complex Form involving about 30 callbacks and relying on a small server-side database. The outputs of this form are aggregated and turn into different graphs / dynamic visualizations (5-6 more callbacks).

My questions are the following:

  1. Will performance be significantly affected if using 3 instances of an AIO Form class (involving about 30 callbacks) split in 2 different pages?
  2. @Emil May DashBlueprint from dash-extension be the solution?
  • A. Is it possible to nest several (similar or not) DashBlueprint instances?
  • B. Should I have concerns with regard to performance in the conditions described above?
  • C. Is there a dedicated way to encapsulate DashBlueprint instances into a class. I was thinking of wrapping DashBlueprint instances into classes inheriting from DashProxy for instance but I am not cleary not sure about this…
  1. Any tips with regard to this topic? Is React still the best solution?

Answers to any subset of questions would definitely be appreciated!

Thank you very much in advance and sorry for the length of this post!