-
Notifications
You must be signed in to change notification settings - Fork 66
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
Make last confirmation step optional #213
Comments
Hey Philipp, thanks for testing the beta! That's something we're discussing over and over. While we all agree that we want to get rid of this extra step, we can't do it right now. The flow is currently:
While it is possible to move the Submit button to an earlier Screen, our testing showed that it feels out of place when the submit button appears on the "Screenshot" step. Most of the time it was pressed accidentally before the user was ready to submit. There's already too much information in this step. No need for a PR, we'll figure it out after the 1.0.0 release Regarding the visible metadata: That part becomes a redesign. If we allow to hide them is undecided yet. |
Thanks for the insights. I can imagine that the UX is a bit worse if the submit button comes earlier, so we'll stick to the current design with the extra step to confirm. Forking it just for the ability to hide that "show details" button kind of sucks though and it would be great if this was included. Basically, you guys can't prevent anyone from forking the sdk anyway, so trying to enforce some sort of "moral standard" seems pointless to me. If it's about legal liability regarding gdpr or Wiredash's brand image or smth, then it's a different story, but I haven't looked into the gdpr about this at all so I wouldn't know. |
I understand the problème when you have the screenshoot step. |
Basically, we'd like to skip the last confirmation step by replacing the "skip" button with a "submit" button in step 3 of 3.
For one, the last confirmation serves not much purpose if you don't open the "show details" panel.
Also, we'd like to deliberately hide the details panel, mainly because the custom metadata contains lots of debug info about subscriptions and we don't want our users to think that their subscription status has any meaning other than for debugging purposes.
Basically, we'd like use Wiredash as a tool to gather debug info. Example:
user has subscription issue -> we tell him to send a bug report from within the app -> we get lots of debugging info all in one place (currently we need to check a couple of places in the database manually and have to predict the actual app state sometimes).
Are you guys open to PRs regarding this? I would add a new property to the Wiredash widget and if it's set to true, then the skip button becomes "submit".
The text was updated successfully, but these errors were encountered: