Show HN: Sqreen, a Web application protection platform

Re:Show HN: Sqreen, a Web application protection platform by brudgers on Friday April 29, 2016 @09:33AM (#11595578)

I had to dig several pages in to the "how it works" page until I saw that Sqreen is a gem and inferred that it is for Ruby applications and perhaps Rails only.

My recommendation is to put the use case on the front page...better yet in the "Web application protection platform" level description. An added benefit would be to reduce the amount of "what Sqreen is not". It would help people determine "not for me" more quickly and helping people is what your company is trying to do.

Good luck.

[ Parent | on HN ]

Re:Show HN: Sqreen, a Web application protection platform by jbaviat on Friday April 29, 2016 @10:13AM (#11595810)

Hi brudgers,

I'm surprised since it does appear on the home page (https://www.sqreen.io), under the second section "^Made (by | for) developers".

Anyway, thanks for your feedback, we'll improve on this!

[ Parent | on HN ]

Re:Show HN: Sqreen, a Web application protection platform by brudgers on Friday April 29, 2016 @12:36PM (#11596853)

I suspect the surprise is grounded in familiarity with the product and its content. You're an expert on sqreen. Potential customers are not.

A screenshot of a generic text editor juxtaposed against explanatory text probably should be considered burying the lead. The heading doesn't seem like a natural place to put technical requirements/limitations/implementation_details in the content hierarchy.

I'd add that the idea that the software is made by developers is something better shown implicitly than stated explicitly. It's mostly line noise to other developers looking at developer tools [I mean name a developer tool that wasn't made by developers].

[ Parent | on HN ]