You can use it as an IDE but it’s not the Webshell’s job ! Our job is to make an “API mashup factory” for people which want to make fast applications based on APIs.
It would be impossible to make a lib which maintain all third party APIs (arround 8000 today), it’s for that we made it as a platform where everything is always working.
Please note that Webshell is an API too, and you can call scripts as a REST/JSON API.
“Sandbox API workflow” : we have a REPL prototyping part for helping you to see very fast a result of API scripting results, as for server side API (Facebook, Spotify...) as for Client side (GoogleMaps, Youtube player etc...)
After you have two choices.
- Make it again by yourself, with the different API protocols, Oauth1.0 or Oauth2.0 , manage rate limits and keep an eye for maintenance on all your APIs in your application.
- Or push the “create API” button on top right of the Webshell prototyping REPL, so generating a new API of your mashup, use it in production and share it with other developers which would like to use it too.
Our job is to keep an eye for you on API maintenance, easy Oauth integration, APIkeys and rate limit management, analytics.
We will be implement each feature step by step during the public beta.
Dependancy? We are an API like other APIs.
We behave like Back-end-as-as Service as Parse for example. You could do it yourself to not be dependant, but if you implement it fast for your application, with lot of integrated tools, you will keep it in production.
You can see us as a kind of API-as-a-service backend... ;)
I think you need more examples of something complex that is made easily accessible. And show some of the advantage involved in using you as an API around third-party APIs.
We are working on it.
We gived some explanations because each people wasn't not understanding the same value, we are in a step by step explanation of what we've done.
It would be impossible to make a lib which maintain all third party APIs (arround 8000 today), it’s for that we made it as a platform where everything is always working.
Please note that Webshell is an API too, and you can call scripts as a REST/JSON API.
“Sandbox API workflow” : we have a REPL prototyping part for helping you to see very fast a result of API scripting results, as for server side API (Facebook, Spotify...) as for Client side (GoogleMaps, Youtube player etc...)
After you have two choices.
- Make it again by yourself, with the different API protocols, Oauth1.0 or Oauth2.0 , manage rate limits and keep an eye for maintenance on all your APIs in your application.
- Or push the “create API” button on top right of the Webshell prototyping REPL, so generating a new API of your mashup, use it in production and share it with other developers which would like to use it too.
Our job is to keep an eye for you on API maintenance, easy Oauth integration, APIkeys and rate limit management, analytics. We will be implement each feature step by step during the public beta.
Dependancy? We are an API like other APIs. We behave like Back-end-as-as Service as Parse for example. You could do it yourself to not be dependant, but if you implement it fast for your application, with lot of integrated tools, you will keep it in production.
You can see us as a kind of API-as-a-service backend... ;)