Hello! I’ve published a relatively niche watchface that is getting some usage, and have already received a few support requests for it. That’s great, I’m glad people are using it - but it also creates a private support channel that I didn’t sign up to manage.
GitHub repos already have public issues and discussions trackers. If I receive requests there, I can answer them in public so that others can read them in the future, which creates a public knowledge base over time, and others can help answer and contribute. Right now I have to answer each request over and over again in isolation.
My request is to remove the “contact developer” feature entirely from the iOS app.
If the developer wants to field support requests, they can enable Issues or Discussions on their GitHub repo.
Other ideas:
- Fold this into forum.repebble.com, so that each app gets its own channel
- Build out a public Q&A feature on the apps.repebble.com watchface/app detail page, so that the developer can field questions once.
- Make this configurable in the Pebble Developer Dashboard - for each watchface/app, allow the developer to enable/disable private support relay and/or route support requests to the repo.
Thank you for listening!
EDIT: I see now that there’s a Settings > “Allow Pebble users to contact you about your apps” toggle in the Pebble Developer Dashboard! I think that should resolve this issue for me, but leaving this post here as I propose that the private feedback/support channel should be removed entirely in favor of building out a public support channel for each watchface/app.