Storyline 2: Caveat, Critique and Request
Ok, let me preface this by saying that I have been a loyal Articulate customer for about 7 years now. I have dutifully upgraded and migrated from early Articulate to SL2. I've developed scores of increasingly sophisticated modules with the products. We've also been a long term AO client as well. I've always been impressed with the prompt customer service and the amazing community that's been built around the offering. I remain a huge fan.
That being said, beyond a certain threshold, SL2 doesn't work. Granted, that threshold is a big one that 95% of users don't cross. But here's the problem: SL2 is too good not to push to that threshold. SL2 crosses into a realm of advanced user experience and has the potential to really change the learner experience in the hands of the right designer. But once you do cross the threshold, whether it be size or complexity, the application becomes unstable. I've experienced this over the last few months working on a nextgen project and have followed the 'repair' advice at least fifty times. I must uninstall 10 times a day. I have followed every scrap of advice in the threads like a starving man trying to get my project to alternately save/publish. Yes, my project is big but I have more than the system requirements and have followed every protocol about publishing locally etc. It just doesn't work. I don't know whether the app designers were too ambitious or the coders unable to execute but there's a disconnect with SL2 at the margins which will stifle its development until it is made more stable.
Here's my request. Is is possible to provide an honest list of factors that lead to error messages/crashes/etc? Surely you have log reports and could advise on what causes crashes more often than not? For example, after wasting hours, I discovered a thread on how the logo as png could crash the app. Knowing that would have saved me those hours. I now have a project I must essentially rebuild yet again because while it published yesterday morning, it would not publish in the afternoon after a few minor tweaks. I don't believe I am the only one in this situation.
Please do not respond with a "let's open a support ticket for this" offer. It isn't related to a single instance but a series of them. I could be opening tickets for weeks. Just give me a guide to what might cause crashes so I can avoid these and I'd be ever so grateful.
Again, I'm a fan and supporter and I am trying to offer a constructive critique based only on my experience as a relatively well-informed operator. Other user experience may vary. Thanks for your patience AND an (almost) great product!