API Castor

@adamowenit Well sheetsu is purely Google spreadsheets right now, and is going after a slightly different use case. That of being able to mock things out quickly. So I think its initial intention is slightly more technical. Our initial intention was more to test whether any of this spoke to more non-technical people. So (a) be more universal, hence CSV to start... (b) more hand holding and generated docs in more of a prose form than technical docs form. We also wanted to specifically test whether people wanted the ability to add a paywall in front of their data. We were hunted before we were ready to test that latter aspect so the copy on the homepage isn't very strong around that at the moment. That being said, it wouldn't take much of a pivot for us to be doing the same thing. I love what @michaloblak has done with sheetsu. I could see a future where we collaborated. What do you say @michaloblak?

@hilem @adamowenit hi guys. @adamowenit: thanks for mentioning me :) @hilem adding ability of a paywall on the front seems good. That's exactly what Danielle Morille was talking about here https://medium.com/@DanielleMorr.... Sure, I think we can collaborate. Nicholas, feel free to message me if you want to do some collaboration.

@haseeb Blockspring is more for pulling, this was meant more for pushing. One of the differentiators that is planned to be released is adding a stripe paywall so our users can make $ exposing their data. This needs to be conveyed stronger on the homepage.

@hilem @haseeb Great. I will look further into the product. Saving it

@exexzian Large dataset tests are being worked on. Will release results soon.

@hilem @exexzian I'm glad the experience was enjoyable!

@chrisgscott That's great news! I'd love to hear more about your use case. Feel free to reach out anytime or if you create an account we'll email updates shortly.

@orliesaurus import.io is serving a different user, the motivations behind the interface design decisions down to even their name are aimed towards API consumers, we're aiming for producers which will be more obvious as we release more functionality. So our initial functionality may seem redundant but as we mature our bet is that our average user won't overlap much with the average import.io user.