NINA - Guide users step by step inside your product.

@varun1jan Congratulations. And happy product launch.

Mohsin is asking the load bearing question and it has not been answered yet.

Selector anchoring is the most fragile thing you can build on. I write browser automation against other people's interfaces and class names churn constantly, sometimes inside a single session. A quarterly redesign is not really the threat. Tuesday is.

What has held up for me is anchoring on semantics rather than structure. Accessible name plus role survives a restyle, because a redesign usually keeps the button called Save even when every class around it changes. CSS classes are decoration, and they get treated like decoration.

If you want it genuinely durable, the honest version is a contract rather than magic: ask customers to put stable test ids on the elements NINA walks through. Less impressive on a demo, far less likely to break silently in production six weeks later.

What does it anchor on today?

Congrats on the launch, Varun and team! The gap between documentation and helping someone at the exact moment they’re stuck is very real.

I especially like that NINA keeps guidance aligned as the product changes. How do you evaluate whether its guidance actually helped a user complete the workflow, beyond reducing support tickets?

How does NINA handle personalized workflows for different user roles (e.g. admin vs end user) within the same product?

Can your product be integrated into any Android or iOS application and will it be effective (if there are sources for context, of course)? Otherwise, you write about B2B and SaaS.