Don't tie your product's innovative features to the Adobe's Creative Cloud
There are not many professionals who like the creative cloud. It's cumbersome, awkward to use, not user friendly and slow. It's like the UI for the Typekit website - not fit for purpose. For some of the exciting features you have shown at MAX, history states and multi-user document access, please don't tie these to Creative cloud. Don't let 'Adobe' bully you into using legacy frameworks to support innovation. A lot of pro users will want to decide the place they write data to or use their own cloud service. For example, some of the worst performance I have seen in XD is when it has had to use (uuuuurgh) creative cloud when sharing prototypes. Most of us don't need or want Creative Cloud features such as importing and exporting files to and from Illustrator via 'cloud libraries' as mentioned here: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/13118382-copy-from-xd-paste-into-illustrator-or-photosho - we want to cut from XD and paste into Illustrator.
Unfortunately, the bloatware and background processes that run with creative cloud and adobe desktop apps constantly create kernel panic in Mac Mojave, 10.14.6 Macbook Pro 2017. Thankfully, I can uninstall it and keep illustrator and photoshop running. The same cannot be said for XD. An install without the crash reporter daemon, CXCS processes, CEP html engine, Core Sync, and Creative Cloud sync (which are all turned off in preferences) hogs all my 16 gigs of ram and causes freezing. As of today, I'm scrapping XD in favor of Figma and Invision, because of the bloatware attached to XD. Please consider revamping your software to run without RAM hogging processes that slow down creative and design's main MAC platforms.
Eddie Deighton commented
I cannot believe this has become the default way of working now. I have no use for it whatsoever in my workflow and nor does any of my team. I also have clients Japanese that frown upon any external connectivity in our workflow so it's going to cause real problems convincing them I have their best interests at heart if I want to use XD now. Come to that, I don't know anybody that likes the thought of CC or uses it. Were there that many request for cloud-based syncing that it became a priority? I can't see any requests for it on this site. I loved the way XD bucked the a-typical Adobe trend for shoving CC down our throats and now it's moved in the same direction. Sad times.
The more I see you retrofitting XD into existing Creative Cloud functionality the more I feel tiny droplets of sadness appearing in my heart...
Jens Lattke commented
Hi Jacob, it's not only the performance. The Problem is: in some cases our clients don't allow to store the data on different servers than theirs. Which means: for security reasons it's not allowed to share those files via the adobe/creative cloud … It would be great if we can specify own servers.
Yes, this is a 0.6.2.7 issue
Jacob, I am having more performance issues with uploading prototypes and my colleagues and frustratingly stake holders being able to see them. I will email you a file now. Thanks James
Jacob, I'm in the UK. Thanks for your response. Currently all prototypes are down, which I'm hoping, when I need to tomorrow, that will mean they're switched over to new, faster service. I've written plenty and send files to numerous people but what I really want, as I feel a lot of other people want, is just a service that works with my workflow, not one that makes me bend to a corporate requirement. I love what is going on with the core of XD and I hope it stays clean and true to it;s initial 'start-up' like values. Have a good day.