You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Change "scoped" description to something more impactful
I don't think that "scoped" description has the same impact as the "verified" description.
Homebridge plugins that are marked as verified have been reviewed by the Homebridge project team to ensure they meet various requirements that encourage best practices and a trouble-free user experience.
The blurb is very straightforward about why a user should consider a verified plugin over a non-verified plugin.
Scoped plugins improve long-term reliability and ensure consistent maintenance by combining centralized oversight from the Homebridge team with continued involvement from the original maintainer.
Keeping in mind that some of the Homebridge users' first language may not be English, "improve long-term reliability" feels a little bit too ... indirect. Something along these lines is a bit more direct:
Homebridge plugins that are marked as scoped are administered by the Homebridge team to ensure consistent
and ongoing maintenance, by continued involvement from the original maintainer, or by finding a new maintainer.
The first sentence says the meat of what the most users care about: Homebridge plugins that are marked as verified have been reviewed by the Homebridge project team
the rest is TL;DR
So here the first sentence says the meat of what the most users care about: Homebridge plugins that are marked as scoped are administered by the Homebridge team
the rest is TL;DR
Change "scoped" label
Change the plugin label from "scoped" to supported or endorsed or something similar (or "Homebridge supported", "Homebridge endorsed")
"Verified" has immediate impact. The user doesn't need to read further to get the gist. With "scoped", it isn't immediately clear why the user should care about a plugin being "scoped". The user has to read the blurb to understand what it means and most people don't read: "TL:DR, didn't read, must not be that important".
Be honest, how often do you skip reading the boring instructions?
Update:
"scoped" is how Homebridge plugin management is implemented. The moment the implementation changes, the label becomes meaningless.
The text was updated successfully, but these errors were encountered:
justjam2013
changed the title
Change "scoped" label and description to something more impactful
Change "scoped" plugin label and description to something more impactful
Jan 10, 2025
Feature Description
This enhancement recommendation has two parts:
Change "scoped" description to something more impactful
I don't think that "scoped" description has the same impact as the "verified" description.
The blurb is very straightforward about why a user should consider a verified plugin over a non-verified plugin.
Keeping in mind that some of the Homebridge users' first language may not be English, "improve long-term reliability" feels a little bit too ... indirect. Something along these lines is a bit more direct:
The first sentence says the meat of what the most users care about:
Homebridge plugins that are marked as verified have been reviewed by the Homebridge project team
the rest is TL;DR
So here the first sentence says the meat of what the most users care about:
Homebridge plugins that are marked as scoped are administered by the Homebridge team
the rest is TL;DR
Change "scoped" label
Change the plugin label from "scoped" to
supported
orendorsed
or something similar (or "Homebridge supported", "Homebridge endorsed")"Verified" has immediate impact. The user doesn't need to read further to get the gist. With "scoped", it isn't immediately clear why the user should care about a plugin being "scoped". The user has to read the blurb to understand what it means and most people don't read: "TL:DR, didn't read, must not be that important".
Be honest, how often do you skip reading the boring instructions?
Update:
"scoped" is how Homebridge plugin management is implemented. The moment the implementation changes, the label becomes meaningless.
The text was updated successfully, but these errors were encountered: