Show HN: Sqreen, a Web application protection platform
sqreen.io
sqreen.io
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.
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!
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].
We also announced our 2.3M$ seed funding round today.
Congratulations on your seed funding news. I wonder how did you guys manage the launch and closing a round simultaneously?
Right now it feels as if I have to keep looking at yet another dashboard for something to blip across the feed.