Live data from Hacker News

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

news.ycombinator.com

1–10 of 51 posts

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

#1
Hi HN! We’re Alvin and George, the founders of Airship (https://www.airshiphq.com). We built Airship to help companies roll out new features carefully, instead of blindly deploying.

You may have seen that a million users are revolting over Snapchat's redesign, dropping their App Store rating below 2 stars. You might also remember when Digg launched a redesign in 2010 that caused a 30+% dip in usage in a matter of days. To avoid unpleasant surprises, companies like Facebook and Airbnb have developed their own sophisticated tools to carefully roll out their new features, test and measure their impact incrementally, and roll them back when signs of trouble appear. This way they can be informed about how users receive the features, and can fix mistakes without jeopardizing their entire user base. Then they can publicly release the new feature with reasonable confidence about its likely reception and effects.

Alvin and I discovered the importance of controlling feature launches and monitoring them carefully when we worked at Zenefits together. Many companies would like to be able to mitigate risk through controlled feature rollout and rigorous testing, but don't have the resources to do it. This approach is proven to work, but remains expensive, since only companies that can afford in-house tooling, and often a dedicated team to maintain it, can do it. It struck us that there was a need here for a product, so we started Airship to build it and make feature rollout accessible to everyone.

To use Airship, you install one of our SDKs. Then you can flag or gate code with if/else blocks calling a single function provided by our SDK. This automatically gets wired up to controls in the Airship dashboard which allows you to control targeting rules, rollout percentages, and whitelists/blacklists.

Key features of Airship: - Gradually roll out and A/B testing of entire features, not just copy and superficial changes - No performance hit (checking whether a customer has a feature takes We'd love to hear your feedback and hear about your experiences, ideas, and needs in this area!

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

#4

How is this different from LaunchDarkly?

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.

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

#5
post #4

How is this different from LaunchDarkly?

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?

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

#6
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?

There's a bunch of feature toggles libraries out there for pretty much every web language you can think of. Doing it statically is pretty easy, you can rewrite a similar library in a day or two. One Ruby[0] and Python[1] example below, but there are tons.

What you don't get out of those libraries alone is a couple things. One is a metrics pipeline if you want to actually A/B test and gather metrics on the success of different features. That's a hard problem because A/B metrics collection pipelines are something pretty much something everybody reinvents from scratch right now to fit their combination of language/logging tool/cloud host/data warehouse/BI tools/whatever.

The other big one is the managed configuration deployment - a UI that you can toggle features on and translate those to appropriately flipped toggles in all of your clients (mobile, web backend, web frontend, whatever). That's a pretty big task to do and requires a hosted service one way or another. Flipper (below) looks like it integrates into a rails service and so has a UI, which is kinda neat (first time I've noticed an OSS solution that does that part - looks like theres a number of options that do this now), but you'd still need to reinvent tooling for mobile apps and such with it.

[0]: https://github.com/jnunemaker/flipper [1]: https://github.com/disqus/gutter

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

#8
post #4

How is this different from LaunchDarkly?

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.

I'd also add that what we're interested in is not just feature flags, but the use of feature flags for A/B testing - which translates to a few key differences in how you build and optimize the product.

A few things:

1. More sophisticated targeting; i.e., different types of objects, combinations of attributes, and groups.

2. Airship's pricing model is aligned with customers' incentive to grow. Our architecture emphasizes local computation, so performance and cost scale very well (better than things like MAUs) - savings that we pass onto customers.

3. Airship will integrate with existing analytics tools (like Segment) so you have A/B testing capabilities without doing set up work. You can even set up an A/B test retroactively (after the feature has shipped), because Airship can annotate the events & metrics you already track.

4. Airship focuses on non-engineering teams as well (PM, Data, Growth), and making the dashboard intuitive for those use cases.

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

#10
Wanted to drop in a quick review of Airship (disclaimer: I got to know the founders through the experience of being early users).

We, at Repl.it, started using it for a very risky rewrite of a core part of our product -- the IDE (https://repl.it/site/blog/ide) -- and it helped us roll it out safely, turning it off when we needed to, when we get a user bug report Airship could quickly tell us if that user has the feature on, etc.

Since then we've been using it for virtually every feature release and experiment. We couldn't be happier with how smooth the service is:

- The service is reliable and fast.

- The UI is simple and instant.

- The SDK is simple and easy-to-use.

Post reply on HN