Overall Satisfaction with Appcues
Appcues is used within SaaS web applications that our business provides to internal users and customer users alike. The main problem Appcues addresses are the ability to implement user onboarding features, feature tours and help tooltips on-the-fly directly into your production web application. This mitigates from having to effectively hardcode these user-oriented features into your Development, QA, and Production environments and lets you make changes to them immediately, without having to push changes through each environment. Appcues also lets you target these features (tours, tooltips, user onboarding, etc.) to specific users, groups of users, customers, etc.
- Implement application/feature/release tours for web applications.
- Make changes directly on production without the need to stage them in Dev or QA.
- Target tours, tooltips, and onboarding messages to users, groups of users, customers or any developer defined criteria.
- There are certain limitations of where tooltips can be placed, depending on the application is built.
- The way 'appcues' are organized in the management console can be a little more user-friendly.
- Appcues has allowed us to quickly deploy user help features that target specific users, audiences, even customers with very little effort.
- Appcues has helped gain user traction by providing helpful tooltips, tours, and other rich content, reducing the first-time user learning curve.
Appcues is well suited for web applications with small development teams that don't employ continuous integration to make updates to their application. If your application release methodology employs continuous integration, then Appcues may not be as useful because making changes to production can be expedited in the event of a typo or issue with the tooltip(s) or other user onboarding feature, but in my opinion, it's useful even in CI environments.