Hotjar vs. Angular Feature Flags

Hotjar is good for a first pass at understanding user sentiment or locating potential usability issues. There are features such as "rage clicked" which shows recordings or instances when a user rage clicked or had an issue with your site. Hotjar has also been helpful to launch intercept surveys on mobile, desktop, and app, which not all competitor software allow. Hotjar recordings are fun to watch. "Watching Hotjar like Netflix" is a favorite pastime at work.

Incentivized

Feature Flags are well suited for apps which are being developed across numerous teams in order to extend and basically enable/disable whatever areas of the app you want. It's not really necessary for an individual developer or perhaps even a single team of developers, depending.

Incentivized

• Heat mapping is great on Hotjar. It is a good place to start when you are looking at the UX & CRO on your website. You can see the % of people clicking on elements on a page, how far they scroll, and mouse movements.
• Hotjar is great for session recordings. These record the mouse movements, clicks, pages and scrolls of a user in video format. You can watch these to investigate what works well on a site and identify potential roadblocks and bugs.
• Hotjar is great as it ensures that users details are anonymous; for instance, if you are watching a session recording, you cannot see what a user types in a form field, as Hotjar blanks this out.
• Hotjar has a poll function, so you can have polls on your website.

Incentivized

• Allows for easy configuration of what you may define as features
• Allows for a customization layer to utilize Feature Flags

Incentivized

• Hotjar is primarily used for web-based experiences. Not that easy to use on mobile apps.
• I'd love to see Hotjar integrated with Google Analytics for an even deeper view.
• Hotjar is primarily used by smaller organizations...pricing can get steep quickly for larger organizations.

Incentivized

• Would be nice if there were a built in route guard and more end to end solution out of the box I suppose

Incentivized

Even though the heat maps and user recordings were useful, our website was significantly slowed down after we installed Hotjar, so much so, that it took over a minute for our blog to load. The data that we gathered was not worth the length that it took our website to load.

Incentivized

So easy and simple to use! Straightforward anyone in the team is able to easily go in and set up anything in Hotjar. The UI is really simple. Whenever you give feedback to Hotjar they continously take on board the feedback and improve the tool.

Incentivized

Hotjar is a SaaS-based company, and as such has a good support service. Users can quickly submit support tickets through Hotjar's online portal. Enterprise customers get access to additional support members and have SLAs to support their larger, more complex needs. Overall, Hotjar is extremely reliable and I've never had to reach out to customer support.

Incentivized

HotJar was selected for a few reasons:

• Video Capture - HotJars video capture of user sessions is nothing short of amazing. It is so useful (not to mention cool) to see, in real time, how users interact with our software. It makes our jobs so much easier and more enjoyable to get this type of d
• User Surveys - The ease and flexibility of surveys we can make available on our website are an awesome tool to get additional data.
• Simple implementation - Adding a very small amount of code to our website gives us the ability to use all of HotJars features without having to touch our code again.

Incentivized

We still utilize Git as our source control system but Feature Flags allow us to use Git in a less complex and more efficient way for our development needs.

Incentivized

• We have fixed many issues, for example, checkout usability problems with the video recording feature. You can catch bugs and get an overall idea of how a particular page is working.
• Polls have helped us pair intent with the video sessions, so we can understand better why certain users answered different things. You get greedy and try to ask everything but that won't work. Keep it simple and it will give you small but important insights.

Incentivized

• I would say a large ROI considering the reduction in branching and merging we need to perform and also the ability to use common, up to date code across teams. There's a lot of shared code we make use of, particularly with identity and authentication and our entire identity platform which is essentially used by each feature.

Incentivized