[petetnt]

While I'd love to test out Airship, not being able to do that without signing up is pretty much a non-starter for me. When I say pretty much, I can often be persuaded with having at least the documentation available without signing up. For example Logrocket (https://logrocket.com/) needs signing up, but the documentation is all there and I can immediately see the effects it will have on my app if applied.

[rahilsondhi]

+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?

[alviny]

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

[Techonomicon]

Why hide it? Me signing up gains you nothing, I can just use some throwaway account, or make some [e-mail] 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.

[platypus-d]

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.

[petetnt]

That’s awesome, thank you!

[mritchie712]

How about a video that shows what the actual product looks like and does? That usually works for me and I prefer it to flashy videos that don't even show the real product in action.

[platypus-d]

A video sound like a great idea. We'll look into it!