Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve UX / Semantics of Ngrok Options in App Settings #2112

Closed
tonyanziano opened this issue Mar 18, 2020 · 0 comments
Closed

Improve UX / Semantics of Ngrok Options in App Settings #2112

tonyanziano opened this issue Mar 18, 2020 · 0 comments
Labels
Enhancement New feature or request to evolve an additional feature

Comments

@tonyanziano
Copy link
Contributor

The following options in the application settings for Ngrok behave in a way that isn't very clear to the user upon reading the descriptions:

image

  • "Run ngrok when the Emulator starts up" will always use Ngrok regardless of whether the "Bypass" option is enabled or disabled.
    • This is not very clear to the user; one would expect the Emulator to still honor the "Bypass" option
  • Since the "Bypass" option is basically rendered useless when the "Run ngrok on startup" is enabled, the UI doesn't accurately reflect that to the user

Solution:

There are two suitable solutions:

  • We rework the underlying logic so that the "Run ngrok on startup" option doesn't cause the Emulator to ignore the "Bypass" option and instead just does what is described and starts Ngrok on startup to be used with remote bots

OR

  • We change the wording of the "Run ngrok on startup" option to be something like "Always use ngrok to communicate with bots" and enabling the option disables the "Bypass" option

Personally, I'm in favor of the former.

@tonyanziano tonyanziano added the Enhancement New feature or request to evolve an additional feature label Mar 18, 2020
@OEvgeny OEvgeny closed this as not planned Won't fix, can't repro, duplicate, stale Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request to evolve an additional feature
Projects
None yet
Development

No branches or pull requests

2 participants