In the Forge, when sharing a module or extension, it is possible to have dependencies displayed and automatically managed by ServiceStudio when installing.  When sharing a solution, this is not possible.

The process of having to download a Solution instead of being able to simply install via ServiceStudio also seems like a non-ideal situation.

Forge should either allow manual configuration of dependencies, or have it able to read the actual solution to see what dependencies are needed.  This could also work when developers create specific solutions for upload to the forge whereby the process could include a link to certain forge components.

And no, before anyone asks, these dependencies were not custom apps/modules/extensions; they were OutSystems UI components needed in a LifeTime environment (OSUI is not default for LT)..  This has come to the forefront with an application that was recently launched (packaged as a solution), Forge clearly stating that no dependencies were needed, but when installing the solution, clearly dependencies were missing and had to be manually installed.  

It sounds like a 1 in a million case study, but I believe this one solution is not the outlier and most developers who would like to upload Solutions to the Forge can benefit from this.  OutSystems is expecting applications to be built on a 4-layer canvas, but uploading a properly built solution to the Forge should not be hampered by an inferior experience compared to apps/modules/extensions.