Onset Pricing Overview

Here are the cons of Onset:

1. UI & UX: You see this at the beginning, right? And it's one of the gorgeous UI and UX combinations I have ever encountered in a web app. It reminds me of XenForo. I love the attention to detail, smooth transitions and material design. Your subscribers will fall in love with such a release page.

2. Detailed stats: There are a lot of details that a subscriber can see. For instance, there's a hero image, release date, what's changed/depreciated and much more. You can pin important ones at the top. Plus, you can change the slug to match the title, which I am doing with Onset.

3. Easy to add subscribers: You need the subscriber's email address to add them. Plus, you have Mailchimp integration to add your subscribers to Onset. Or, you can add a widget to let them sign-up for release notes.

4. Integrations: Here's the best part. Onset supports a lot of integrations. You have Slack, which will notify you once a new version is released. You have git-based repositories like bitbucket and Gitlab to pick up releases automatically. Plus, there's Zapier to handle the rest. Still, if something is missing, you can request an integration.

5. Roadmaps: Roadmaps ensure that subscribers get the gist of what they can expect. Onset allows the user to upvote features so that you are aware of the most-wanted features. You can also mark backlogs, the percentage and lots more. Review collected by and hosted on G2.com.

Here are some cons:

1. Pricing: I think the pricing is on the higher side. Having a dedicated page of release notes is essential, but it becomes difficult for some developers, especially open-source ones, to pay for the subscription fees. It's not too high, but I think git-based software is getting much more capable, thus giving slightly more value for money.

2. API: I think new users will have difficulty understanding their API keys' use. Being their premium subscriber, I never found myself looking for an API key. Upon further research, I found that it's still in the drafts stage, which could have been mentioned on the API page itself, not on the API reference page. Review collected by and hosted on G2.com.