1. We do believe that this is a big opportunity, but it's quite a developed market (it's formally known as Digital Adoption Platforms). In order to compete in the space, there are a few more critical features that we need to develop. We would like to provide this for our customers so they can use the same guides throughout the early customer experience.
2. Yes. You can accomplish this by triggering guides to appear on pages matching certain patterns (such as url). You can also use guides to link between each other.
3. If that update results in an update to the UI, then it can be captured with DOM serialization.
Yes! Although the feature is pre-beta right now, we're excited to release it to our customers in 2 weeks. Our current customers have requested it to personalize demos for individual prospects / customer segments, or to update old dummy data in their account.
We've taken different approaches to this in the past. Through serializing all network requests (from js bundles to api requests), you can reassemble an application on the client in the same way that it would typically appear. This allows you to use any browser tech like canvas / WebGL as normal. From a DOM serializing perspective, although less interactive, you can convert canvas elements into static images (.toDataURL()). This has proved to be good enough for most use cases so far, but we're continuing to experiment with new methods!
Good questions. Chris here. Before learning about the space through user interviews (and from Neil and Randy), I had the same thoughts!
For companies that want to build this internally, there's a couple of things to think of from an engineering perspective. A) Restore state: If users can manipulate data in the app, is there a "restore state" so that they don't modify the same data for other visitors. B) Privileges: you probably want special, more-restrictive privileges for users just experiencing a demo and not setting up a typical user account.
So you are correct, that setting up a static version of a team's app could solve these problems and that's exactly what we help facilitate! It's a trickier problem to implement internally than you might initially think (imagine calling "indeterministic" web APIs like Date.now() for a time-series chart or Math.random() for uuids.) Through our customer interviews, we found that it's difficult to win the engineering team's time for such a task.
Our no-code editor also allows you to update the overlays dynamically and easily update the (now) static demo to keep it up-to-date with your application.
Interesting read. I've spent a lot of time thinking about ttfb in the browser and have enjoyed exploring the space of web performance "hacks". Obviously people are thinking about measurements like this for mobile apps too, it's just not an area I read about a lot
In compliance with the new CCPA Data protection laws, companies that make over $25 million per year or collect data from more than 50,000 people are required to provide their users access to their data.
After poking around, I discovered that companies don't make it a very user friendly experience to request access to, delete, or request not to sell your data. Sometimes you need to fill out one form - sometimes several. Sometimes you even need to send an email to a privacy team with a picture of your driver's license.
I thought it would be useful to make a simple resource I could share with friends and family that makes the process more straightforward. It's not a comprehensive list of companies, but if it's seen as a useful, I'll continue to add resources/information to the site.