
First let me explain my situation. My company helps other companies create e-learning projects. We are a small firm, but we probably have 50 courses under development right now. For most of these courses, the customer has a special request (actually many special requests), like restrictions ... for example not having access to the test until all pages are viewed, or points or badges awarded for performing page activities, or a Table of Contents, accessed by clicking a custom button. The list goes on and on. With Lectora, we can do any of these things. When the customer asks if something can be done, we always say yes. So Lectora gives us the best flexibility. So I advise people who are making a software decision, if they want templates and low learning curve, choose Articulate. If they want to explore, create, learn, and go outside the box, use Lectora. Review collected by and hosted on G2.com.
With Lectora's constant push to get better and add more functionality (which I love ... and this year, the way buttons and graphics are handled is a tremendous improvement) comes versions that are not quite ready for prime time - but released anyway - with Trivantis ready to add patches as bugs are identified. We seem to always jump in first with the upgrades, and then suffer the bugs. For some reason we always think the problems are our fault, or our computer's ... but then eventually learn about the bug. I wish Trivantis (and all software developers) would be more open and proactive about communicating known bugs and fix schedules. Review collected by and hosted on G2.com.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
Validated through LinkedIn
This reviewer was offered a nominal gift card as thank you for completing this review.
Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review.




