We at Gira would also greatly benefit from this. We develop firmware that shares common software components from our Firmware Platform and it would be of extremely high value to re-use components in different contextes and see where the components are being used.

If components had connections to each other, it would be great if these connections would be shown if you place two connected components inside the same app. (we would "misuse" apps to model our device firmware packages.)

Likewise, if components would have connections to outside apps or components, it would be great if these would also be shown on the diagram of each app (device) that the component is used in.

This would greatly increase the value of icepanel for our organisation.

This would be a highly valuable addition! It’s a common and critical scenario where the same applications, libraries, or binaries are reused across multiple systems, domains, or platforms. Without native support, it becomes repetitive, confusing, and harder to maintain. This feature could significantly streamline architecture modeling and accelerate adoption across teams.

My team absolutely need this! We cannot perpetually add same apps in a system in different domains, on and on and on....

this would be great to represent scenarios where multiple applications share and/or export libraries as right now such scenarios are very hard to represent without creating confusion

This is feature we would like to see in ice-panel and it is critical use case for us and helps expedite the adoption.

Would appreciate this!

Some contexts where this might apply:

Same OpenCL kernels run on a laptop CPU vs server NVIDIA GPU accelerator

Same C binaries linked into both a Python prototyping app and an iOS mobile-app