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

[Feature Request] - Hide Suggestion button on app page based on app.json #379

Open
martijnpoppen opened this issue Dec 11, 2024 · 4 comments

Comments

@martijnpoppen
Copy link

Please add a option in the app.json (like donations) to hide the suggestions button on the app page. This is a feature which should be toggle-able for developers so they can decide where they want to be contacted

@WeeJeWel
Copy link

We have a few competing ideas for this:

  1. Hide the 'Suggest' button when a developer specifies this (either by app.json or toggle in the Developer Tools)
  2. Instead of a form in the 'Suggest' popup, redirect the user to the Homey Community Forum Topic (when specified in app.json)
  3. Show a 'Reply' button + form in the Homey Developer Tools which will send an e-mail to the suggester.

My preference would be #3 because it's by far the most user-friendly (albeit not the best developer-friendly) solution.

What are your thoughts?

@OlivierZal
Copy link

My preference would be for #2 or #1 (in this order), or even a combination of both or the three options – letting the developer choose which option he wants (from either app.json or dev tools UI).

@martijnpoppen
Copy link
Author

I think all 3 options are fine. However I understood from Herman Meerlo that option 3 would be hard as the dev will be sending the mail from a noreply email address.

@WeeJeWel
Copy link

I think all 3 options are fine. However I understood from Herman Meerlo that option 3 would be hard as the dev will be sending the mail from a noreply email address.

Yes, but the Reply-To field will be the developer's e-mail address.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants