How do users use your products?

When designing product functions, how can you design them according to objective user needs and behavioral analysis results? Rather than assume: "Well, I think this feature is very good, so users must also like" ...

Fullstory's idea is that only by recording the user's path on the site can a real objective reaction be made to their true ideas, because they say that the demand is often not what they do. So fullstory provides embedded code, embedded in the Web page, it can automatically for the user's behavior screen, easy to product koi in the online or iterative new features to understand the user's feedback.

Of course, fullstory in addition to recording screen, but also provide users with a single point of action record data, such as users browsing the page when the click, slide, jump behavior, and fullstory can also be linked to these single point behavior, comb out the user's behavior path logic.

In fact, many people have done this kind of tracking tools, we have previously reported that the YC hatching heap also want to track the user trajectory, but there is no video screen function.