Github 中的 Chrome 扩展程序而不是 Chrome Store

发布于 2024-11-30 03:50:10 字数 320 浏览 1 评论 0原文

我开发了一个对 Google Reader 粉丝非常有用的 Chrome 扩展程序,允许将单个项目标记为已读(例如 Gmail)。

我不想支付 5.00 美元,所以我决定将我的 Chrome 扩展上传到 Github(一个免费的网络存储库)。

你认为这会有什么问题吗?有人可以向我解释一下吗? (也许是某些 Chrome 扩展的开发人员)

任何帮助都将非常感激。谢谢!

编辑:我在此处上传

I've developed a Chrome extension really useful for Google Reader fans, allow to mark individual items as read (like Gmail).

I don't want to pay US$5.00 right know, so I decided to upload my Chrome extension to Github, a free web repository.

Do you think that is going to be any problem with that? Anyone can explain me more about this please? (maybe some Chrome Extension's Developer)

Any help would be really appreciate it. Thanks!

EDIT: I uploaded here

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

羁拥 2024-12-07 03:50:10

如果您想最大限度地提高您的扩展程序的可见性,我认为这 5 美元是值得的。但如果你不关心有多少人下载它,也不太关心反馈和统计数据,那么将它托管在 Github 上也很好。

一些优点和缺点:

在 Chrome 网上应用店托管您的扩展程序:

  • 优点:
    • Chrome 用户可以轻松搜索并找到您的扩展程序
    • 自动更新是自动进行的(无需在某处托管更新 XML 清单文件)
    • 半可定制的功能页面,适合商店中的所有其他扩展程序
    • 用户评论、星级评分和安装计数
  • 缺点:
    • 花费 5 美元
    • 必须遵守 Google 的 Chrome 网上应用店政策

在其他地方托管您的扩展程序:

  • 优点:
    • 不需要 5 美元
    • 按照您的意愿创建您自己的专题页面
    • 不必遵守 Google 的 Chrome 网上应用店政策
  • 缺点:
    • 您必须指定并托管更新 XML 清单文件以启用自动更新功能,并将 PEM 文件安全地保存在某处(没什么大不了的,但需要额外的工作)
    • 没有多少 Chrome 用户会找到您的扩展程序并提供反馈(如果您还没有自己的社区或广告,则可能会出现这种情况)

在其他地方托管时,您必须通过 包装处理,然后将 CRX 文件托管在某处供用户下载,并且还必须(可选)保留 更新清单托管在某处并保持最新,以便您的扩展程序可以为已安装它的用户自动更新。

但如果您使用 Chrome 网上应用店进行托管,则不必担心这一点。您只需创建扩展文件的普通 ZIP 文件,然后将其上传到商店,就完成了。商店会为您处理自动更新的内容。

If you want to maximise your extension's visibility, I'd say it's worth the $5. But if you don't care about how many people download it, and aren't too fussed about feedback and statistics, hosting it on Github is fine, too.

Some pros and cons:

Hosting your extension on the Chrome Web Store:

  • Pros:
    • Chrome users can easily search for and find your extension
    • Autoupdating is automatic (no need to keep an Update XML Manifest file hosted somewhere)
    • Semi-customisable feature page that fits in with every other extension on the Store
    • User reviews, star ratings and install counts
  • Cons:
    • Costs $5
    • Have to adhere to Google's Chrome Web Store policies

Hosting your extension elsewhere:

  • Pros:
    • Doesn't cost $5
    • Create your own feature page how you'd like
    • Don't have to adhere to Google's Chrome Web Store policies
  • Cons:
    • You have to specify and host an Update XML Manifest file to enable autoupdating functionality, and keep a PEM file safely somewhere (not a big deal but is extra work)
    • Not as many Chrome users will find your extension and give feedback (potentially, if you don't have your own community or advertising already in place)

When hosting elsewhere, you have to go through the packaging process, then host the CRX file somewhere for users to download, and also have to (optionally) keep an update manifest hosted somewhere and keep that up to date, so that your extension can auto-update itself for users that have installed it.

But if you're using the Chrome Web Store to host, you don't have to worry about this. You just create a normal ZIP file of your extension's files and then upload it to the Store, and you're done. The Store takes care of the auto-updating stuff for you.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文