thanks for the quick reply 
In relation to this i was thinking about tools like anaconda, flutter, go, cuda libraries etc.
All of them could be installed anywhere in the home folder for example.
And reading the guide on software installations here, i assumed it would have been better not to install any third-party package in the template itself for security reasons.
But yes, i agree that we could do this in the template as well.
This seems extremely useful, thanks.
I haven’t read anything about the local proxy yet.
When it comes to just providing the same tools to App Qubes i see no big problem in your suggestions.
What i meant is that if i use an IDE or a framework that requires heavy configurations or long setups, i don’t want to do that multiple times.
As an example, if we have multiple IDEs like vs codium, configuring them properly potentially requires a lot of time.
How do we manage to set them up only once, and automatically have them configured in each Qube as soon as we create it?
This is my main concern, i see no quick solution to this if not cloning the configured qube n times.
A more simple example could be the configuration of a browser: settings, extensions and preferences.
Is there a way to configure it once, and simply log-in with different accounts on each child Qube without any other manual tweaks?
Unfortunately, not all tools allow exporting settings and configurations easily.