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

User Feedback UI widget #4270

Open
armcknight opened this issue Aug 9, 2024 · 6 comments
Open

User Feedback UI widget #4270

armcknight opened this issue Aug 9, 2024 · 6 comments
Assignees

Comments

@armcknight
Copy link
Member

Description

Build the interface widget an end-user would tap to present the feedback capture form

@brustolin
Copy link
Contributor

IMO, a UI widget is overkill. I believe a public API to open the feedback form is enough. The user can be responsible for creating the button, link, or action that opens the form, as each app has its own visual identity.

@philipphofmann
Copy link
Member

@brustolin, I think that's the main point of this new feature. If I'm not mistaken, people on the web love it, but I'm also unsure if folks on native mobile apps would use it. @bruno-garcia or @armcknight, maybe you can elaborate on why it's worth the effort to build a UI widget.

@brustolin
Copy link
Contributor

@philipphofmann I believe the main point is the form screen isn't it?

@philipphofmann
Copy link
Member

@philipphofmann I believe the main point is the form screen isn't it?

Yes, but I guess many iOS developers don't want a Sentry-flavored form screen but rather design their own. That was the main reason why we didn't add it in the past.

@armcknight
Copy link
Member Author

There will be a way for customers to BYOB (bring your own button) and hook it into the integration. They would be completely responsible for displaying that button, we just use the touch event to display our form.

I hadn't yet considered an option where we take a button from them, but manage displaying it. That could be another nice option, so they get their branding, but don't have to worry about the mechanics.

In any case, it's not a requirement to use the widget. It's another option, there may be people out there that feel differently than you about this. It doesn't make sense to withhold the option from them just because someone here doesn't like it. Ideally we can attach analytics to it and we can see how many people use each method in practice.

@philipphofmann
Copy link
Member

@armcknight, yes, that makes sense. Thanks for explaining 😀.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

3 participants