Browzer bootstrap related question

Support General Questions
1

I’ve recently enabled Ziti BrowZer Runtime (ZBR) for my demo environment and am planning to enable it for production soon. However, I’d like to streamline the user experience by disabling a few options to make it more intuitive for end users.

Questions:

  • Making ZBR Button Invisible:
  • How can I make the ZBR button invisible for end users in production? I understand its utility for development, but it’s not required in a production environment. Why is there no option to disable this button for specific environments?
  • Customizing Bootstrap Message:
  • Is there a way to customize the bootstrapping message displayed in the UI? If so, could you provide guidance on how to implement this customization?
  • Origin Trial Token Concerns:
  • While I understand the Origin Trial token improves the user experience in Chrome, the need to manually renew the token every three months feels cumbersome. Is there a more streamlined way to manage or automate this process?
2

I expect the JSPI Origin Trial token renewal to be a short-term chore. The W3C is reviewing the JSPI feature and is now in the last (4th) review phase. Once formally approved, all browsers will support JSPI out of the box, and we can retire the Origin Trial mechanics from browZer.

Making the browZer button invisible, and customizing the bootstrap msg is not currently possible, but I'll add tasks to my backlog for these features.

NetFoundry customers can always influence priority paths.

1 Like
3

@curt Thanks for the response. could you share me the link to refer about JSPI review page?
And it would be great if you have fix for above requirements sooner would be better for us.

4

Hi Vinoth. This link should help: Chrome Platform Status

5

It would be really helpful if we disable that button atleast i can release it to my customers.

6

Hi Vinoth. Can you elaborate on why the presence of the browZer button is a blocker for release to your customers?

7

@curt From an end-user perspective, our customers are primarily healthcare professionals who are not particularly tech-savvy or equipped to handle technical troubleshooting. While I understand that the BrowZer button is a useful tool during diagnostics, in regular use cases, its presence might be distracting and could negatively impact the overall user experience of our product.

Here are my expectations for this feature:

Default Behavior in Production:

  • Allow the BrowZer button to be hidden by default in production environments.
  • This ensures a clean, intuitive interface for healthcare professionals, providing a seamless user experience without unnecessary distractions.

On-Demand Access with Hotkeys:

  • Add functionality to toggle the visibility of the BrowZer button on-demand using a hotkey (e.g., Alt + F12 or a customizable combination).
  • This allows technical teams or administrators to access the button easily during troubleshooting, without affecting the user experience for non-technical end users.

Configuration Option:

  • Include a setting that allows this feature to be enabled or disabled based on the deployment type (e.g., troubleshooting vs. production).

Why This Matters:

  • For Healthcare Professionals: A clean and distraction-free interface is critical to ensure ease of use and productivity.
  • For Administrators: Quick, on-demand access to troubleshooting tools is essential without imposing unnecessary elements on the end users.
  • For Developers: A flexible, user-centric approach enhances usability and aligns with Zero Trust principles, making the system more adaptable to various environments.

Correct me if my understanding is wrong on feature usage.