Hi all.
I am curious about this one. I am really interested in finding out who is using the Captivate Draft app and how you are using it?
What do you like about it? What don’t you like?
If you are not using Draft for your storyboarding, what are you using? I have met/discussed with others that simply use PowerPoint, but I really want to hear from this community of knowledgeable and experienced people.
Thanks in advance for the knowledge.
these comments are very helpful
I’ve used it more as a content gathering tool when in the field. It has the ability to capture video, audio, and notes in a way that can be easily uploaded to my Creative Cloud account and then later accessed in Adobe Captivate itself.
The last update for the app was to address iOS 11 compatibility issues. The version before that included feature improvements and was dated June 15, 2016. I can’t tell you the last time I seriously used it. I think it’s safe to say that it’s abandonware at this point.
I can say that when I purchased my 2020 iPad and Apple Pencil this fall, I reinstalled it to see if Apple Pencil would work with the App. I’m pleased to say that it does.
OK – I will chime in…
Like Lieve, I downloaded it when it first became available.
I quickly realized it was not something useful for me.
I do not storyboard any of my projects. If I was a part of a larger team, there might be some storyboarding going on but I am basically a one-man band. I design it, develop it, and deliver it and as such, I basically just create the thoughts as they come. Typically, a request for my work is in the form of “Hey Greg, can you make something on how to set some parameters on this?”
I struggle the most with ideas. You bring me the ideas and I will figure out how to create them.
Thanks Greg. I appreciate you chiming in, as you say.
And your comments are very helpful. I am someone who is semi new (as I am sure you can gauge) to developing, but I really want to get into it more and more. I have for some time now. I have trialed a few different authoring software but have never pulled the trigger as of yet.
I am here to learn, so the more people share the better for me. I haven’t done that much storyboarding as of yet either. I like to play around with tools and since I currently have a few months of usage of the software, I figured I would check out anything that would be helpful to my learning and development.
Lieve makes and interesting point about linking the CC files to draft. I should likely respond to her on this, but this is when I am thinking on it. I would assume then that whatever is pulled into draft from CC would then transfer over to Captivate, but that might be incorrect.
Anyway, thank you for sharing. Thank you for providing opinion and I look forward to hearing your thoughts on other subjects.
Whatever is in Draft will remain, also what you pulled from the CC Libraries. The reason why my repetitive feature request for access to CC Libraries has never been heard, is probably because very little Captivate developers use other Adobe applications? Or too little enter feature requests? It would be so useful, also for color themes. Now I am using Capture as intermediate appto create a Theme Color palette in Captivate. All those workarounds would not be necessary if there was the natural access to CC Libraries. Draft is taking advantage of CC cloud, Captivate not.
At the beginning of Draft I used it almost exclusively for this CC Libraries connection. But now that you can only export to a responsive project in Captivate that useful feature lost its usefulness since it is very rare I am asked to develop a responsive project.
You would think it would be something they would want to do to try to sell more CC subscriptions. Makes product/sales sense to me.
Question though, when you pull in the draft file and it opens a responsive project, how difficult is it to change the file type? I am guessing from you comments that is would basically be a rebuild of the materials, but more of a curious question.
thanks
I have no numbers but from the questions on the forums, and what I see on my personal blog (views), very few Captivate users do use other Adobe applications.
As for our second question: I will not take this as an insult, but really do you think I would use this argument if it was easy to switch project types? It is not, indeed. Even the possibility to convert a legacy non-responsive project to a responsive Fluid Boxes project will only work for very simple projects, never worked for me. The way round (if you talk about Fluid Boxes): better start from scratch and use the responsive project only as External Library.
Hi Lieve.
Thanks for your perspective as always. Good to hear your thoughts on the app. When I had a trial of the older version of Captivate back in 2018, I downloaded Draft as well, but after that trial I ended up deleting it. Wasn’t anything I needed to use. But I was thinking about it again. I may still take a look, but thought I would see if it is popular and if others could describe useful ways to utilize. This could still come from additional posters. I guess we will see how else jumps into the discussion.
Thanks
I can only tell you that I have seen less than 5 questions about Draft on the Adobe forums which I monitor daily, probably none here in the eLearning community which was started more recently. My biggest problem is that you cannot use it for a non-responsive project. Only a minority of clients is requiring a responsive project.
It is a good question. I have tried all most of the Adobe apps except Rush and the recent Illustrator for iPad (my iPad is too old). The one I used most is Capture, both on my Android phone and iPad.
Hi.
I’m actually surprised that more clients are not requesting responsive projects. I made the assumption that more and more projects would be moving to responsive design based on past working history in Marketing Communications, where there are more and more requests for responsive design. Interesting.
I have used Draft out of curiosity when it was launched years ago. Why do I not use it anymore? Main reason is that when sending the result to Captivate it is always a responsive project, you cannot use it for a non-responsive project which is decreasing its usability considerably.
Due to the kind of jobs I take on (consultancy, debugging, problem solving) a need for a Storyboard is seldom. If I needed it, would prefer a mind-mapping tool.
Occasionally I used Draft for a completely different reason: because it offers access to my CC Libraries, which is still not the case for Captivate. I cannot remember how many times I logged a feature request, but it looks like not many users want to be able to do that, since the request is never heard.
You must be logged in to post a comment.
