We are using MadCap Flare for most of our customers projects. Some are still working/requesting Word or FrameMaker, but there is hope to migrate them to a "real" technical writing XML tool.

We are continually looking at how we can enhance our documentation to support the current and future needs of our customers and partners. With MadCap, we have a publishing solution provider that shares our forward-looking commitment to providing a state-of-the-art user experience.

Our client asked how many extra months it would take to produce a knowledge base. I explained that, by generating it as online Help, we could complete it with the rest of the project. That's the power of Flare.

The new Style Inspector in MadCap Flare 2017 r3 is amazing! I’ll be using this constantly in my projects. The reading analysis feature also saves time and effort when updating our content; I no longer have to use outside tools to analyze my text!

I just completed a week of training in La Jolla, California using MadCap Software, Inc. It was an amazing class. I can hardly wait to get started using my new skills. A special thank you to Mike Hamilton & his crew for their first class service.

Have I told y’all lately how awesome you folks are?

This feature takes what was a separate process requiring different tools and skills and starts to make it just one more Flare output. I expect that more developers will try outputting to mobile devices now that it's easier and more convenient to do so with Flare.

I am pleased that our company is converting over to Flare. It has been very unpleasant working in RoboHelp® over the past year. I'm so relieved that it's only going to be a bit longer and I can hopefully say goodbye to RH® for the last time!

Even though it was our first time using Flare, we completed the project in nearly half the time the first project took.

The topic-based approach to authoring and content reuse enabled by Flare have allowed us to drastically cut down the time it takes to create manuals and get the information out to our assessors and customers.

Flare has been an extremely valuable tool for giving our students real-world experience.

When we overhauled the class, we knew our students would need to start a project in DITA using the oXygen XML editor and then create a set of topics that could be single-sourced and re-used for online Help.We looked at a number of tools, but Flare was the one that dovetailed nicely with our needs. With its native XML architecture, singlesourcing, and topic-based paradigm, Flare was a natural fit.

By migrating from a two-product solution to Flare, which was specifically designed to serve as a Help authoring tool, we immediately recognized significant efficiencies that have led to a two-fold gain in productivity. Citect's decision to move to Flare was the result of an in-depth review of more than half a dozen products. We completed a very thorough evaluation that compared 30 different Help content requirements. In the end, Flare addressed more of those requirements than any other product we reviewed. It also has a modern, forward-looking architecture, which stands out from the older designs of other solutions whose older architectures have been updated for today's Web-based Help demands.

Working with MadTranslations, we have beat every estimated project date with impressive accuracy, responsiveness, and advice on terminology for different locales. MadTranslations has consistently provided us with high quality translation and localization, responsive service, competitive pricing, and an understanding of our authoring environment.

Flare’s top navigation has really helped us to provide a more intuitive, seamless web experience for users, who love the look and feel of the new online Help and the consistency across the different centers.

Flare’s responsive design feature is terrific. With a single output, we can deliver a properly proportioned view of our online Help regardless of the user’s device.