31–34 of 34 posts
I want a self-hosted version. Badly. Seriously, if you sold this as software that I could run anywhere, it would absolutely make my day. The libraries you guys have written are seriously impressive. You could use this kind of technology for a more meaningful way to teach code - when you're done, you've written yourself a website. Also, providing an external "API to rule them all" would be pretty cool, as well.
May I suggest you give the tutorials a solid proof read? There are quite a few typos in the first few pages.
"This APIs is really simple" "Webshell make it simpler."
Also, waaaay too many smiley faces.
Also, with only eight services available having both Latest and Popular tabs in the API Explorer is probably premature. Until all the services need a second screen/page down just show Everything.
Use the hover event to show some sort of highlights box about the API, otherwise make the service icons smaller so more fit for page and at least use the Bootstrap tooltip component to show the service name.
Once you have more than that perhaps add tabs and show the four most recent additions as Latest as the second tab.
Once there are more than 30 or so Popular might be a useful third tab.
Price: What is this going to cost? Can't be free for all uses forever, even if that's true now so at least state that it's 'free while in beta' or similar. Most HNers will agree that a service that's useful is worth paying some amount for to ensure it stays around, after all.
Robustness: You aim to have developers build in a dependency on Webshell but have nothing posted about your infrastructure, uptime or security policies, not even links to privacy policy and terms of service pages.
Bottom line for me is that I think this is very interesting and potentially very useful but beyond using as a playground there's a lot of work yet to do before IMO there can be serious adoption.