Live data from Hacker News

Launch HN: Airship (YC W18) – Controlled rollouts of new features

news.ycombinator.com

41–50 of 51 posts

Re: Launch HN: Airship (YC W18) – Controlled rollouts of new features

#41
post #35

Congrats on launching! Regarding your pricing page: I feel the "10,000 API calls" and "75,000 API calls" limits on the Hobby and Growth plans would deserve some context. Is it 10k API calls per day or month? How fast do I exhaust it? You comment mentioning that you emphasize local computation was helpful and the pricing page might benefit from including it.

Agreed. It's hard for me to buy a service that limits the number of API calls when I possibly can't control this directly. What about changing this to the number of MAU (monthly active users), or features, or some other unit I can grok when I think about my product and how I'd use your product?

Re: Launch HN: Airship (YC W18) – Controlled rollouts of new features

#42

Earlier quoted context omitted.

what are the open-source alternatives, if you don't mind me asking?

This site has a pretty good survey of the open-source options in various languages: http://featureflags.io/feature-flags/ (you have to pick a language from the menu to get to the page specific to that language, as the page I linked to is more of an overview of the concept, and there doesn't seem to be one page that lists them all).

FeatureFlags.io is owned and operated by the CTO of LaunchDarkly. It’s not a survey, it’s an infomercial / microsite for LaunchDarkly. It states “contributed by LaunchDarkly” at the bottom, but considering it’s owned by them that doesn’t seem to adequately sum up the situation. Not sure why they wouldn’t just call it as it is.

Re: Launch HN: Airship (YC W18) – Controlled rollouts of new features

#43
post #41
post #35

Congrats on launching! Regarding your pricing page: I feel the "10,000 API calls" and "75,000 API calls" limits on the Hobby and Growth plans would deserve some context. Is it 10k API calls per day or month? How fast do I exhaust it? You comment mentioning that you emphasize local computation was helpful and the pricing page might benefit from including it.

Agreed. It's hard for me to buy a service that limits the number of API calls when I possibly can't control this directly. What about changing this to the number of MAU (monthly active users), or features, or some other unit I can grok when I think about my product and how I'd use your product?

If you're interested, let's talk. Outside of the published tiers we already do something different. Can reach us at hello@airshiphq.com.

Re: Launch HN: Airship (YC W18) – Controlled rollouts of new features

#44

Congrats on the launch. Couple questions 1. Is this another A/B testing framework? Or is it for feature enablement? 2. What level of granularity(user, cohort etc.) does the platform support?

1. Feature enablement leads very naturally to A/B testing so we're tackling both.

2. Actually fairly granular, especially if you have properties or attributes you want to filter populations on.

Re: Launch HN: Airship (YC W18) – Controlled rollouts of new features

#45
post #33

Earlier quoted context omitted.

+1. With this kind of product, I want to see docs and code snippets immediately. What kind of code do I have to write to use your product?

Thank you, really good suggestion. We'll see if we can put snippets on the main page to help with this.

Why hide it? Me signing up gains you nothing, I can just use some throwaway account, or make some RandomDude32@usa.com which you gain zero from. But to the op's point, I'm not going to go through those hurdles, I'm just going to move on.

One of the biggest draws for this sort of thing from the dev side is "how far am I going to have to bend over to use this".

Freely available documentation sounds like a no-brainer.

Re: Launch HN: Airship (YC W18) – Controlled rollouts of new features

#46
post #33

Earlier quoted context omitted.

Thank you, really good suggestion. We'll see if we can put snippets on the main page to help with this.

Why hide it? Me signing up gains you nothing, I can just use some throwaway account, or make some RandomDude32@usa.com which you gain zero from. But to the op's point, I'm not going to go through those hurdles, I'm just going to move on. One of the biggest draws for this sort of thing from the dev side is "how far am I going to have to bend over to use this". Freely available documentation sounds like a no-brainer.

We thought that the onboarding flow should take you through the product first, where the docs is readily available. In hindsight, making the docs more publicly available makes sense.

Here is the docs: https://airship.readme.io/v1.0/docs. We'll also link them in our home page in the next iteration.

Re: Launch HN: Airship (YC W18) – Controlled rollouts of new features

#48

Is there a reason your pricing jumps straight from $0 to "Contact Us"? Surely there's a $50/month plan or thereabouts that would be relevant to a lot of smaller companies? Congrats on the launch!

Right now, we're working with each each company, even small ones, to find out the right price point for them. If you have any questions on pricing, email us at hello@airshiphq.com

The lack of published pricing immediately makes me think it is too expensive for me. I pay for plenty of services, but "contact us" pricing either means "Enterprise" expense, or pushy sales people.

Re: Launch HN: Airship (YC W18) – Controlled rollouts of new features

#50
post #4

Earlier quoted context omitted.

There's room for more than one player in the market here, it's a super important sort of tool where the open source versions are all pretty mediocre. OSS solutions tend to be statically configured, which non-engineers don't tend to have access or ability to configure. That's not to say you couldn't OSS something here, but it'd be a real effort to host.

what are the open-source alternatives, if you don't mind me asking?

I built one for elixir/ecto called molasses https://github.com/securingsincity/molasses.
Post reply on HN