Adobe CreativeCloud suite should be individual components
Andy Corps
I appreciate the ease with importing a single AutoLicensed Adobe Creative Cloud suite, but generic applications are preferred with either a single small NUL or SDL dependency app for several reasons:
- If NUL or SDL users utilise the same device, you could have 40+gb of stp as opposed to shared applications .stp' and a single 1gb NUL\SDL package
- individual components could be updated as required
- many users only require 1 or 2 components
- dynamically increasing the size or freeing space in the paging cache takes time and degrades user experience.
Thanks
M
Mark West
In addition to the arguments already posted, there are
very
few users that truly use the entire suite. In our user based, we have a number of user personna's that will access just a very small subset ofthe suite.e.g. Admin staff will generaly use only Acrobat Pro, many academic staff make use of Rush to edit videos for upload to our LMS.
It's only the creative types that use the suite - and even then, as Andy notes, a limited subset of that.
T
Tom Fish
Another argument for individual components, there is an issue with the Adobe Creative Cloud suite made available on https://packaging.software2.com/ the application launcher for Premier Rush launches Premier Pro.
When it comes to having to alter the apps in this way, one large application will be very difficult. Especially as we deploy precache to our devices
A
Andy Corps
Another bonus of having he individual components, is I can see the usage of the individual components within AppsAnywhere's analytics. Turns out nobody really uses Substance3DStager, InCopy or Dimension...