Show HN: Turn JS visualizations into data products anyone can use
1–10 of 23 posts
Re: Show HN: Turn JS visualizations into data products anyone can use
#2It's a JS visualization library. I don't see any special "anyone can use it" features. The demo sure seems to require the user to program in JS.
What am I missing?
Re: Show HN: Turn JS visualizations into data products anyone can use
#3It's a JS visualization library. I don't see any special "anyone can use it" features. The demo sure seems to require the user to program in JS. What am I missing?
Hmm, so maybe our blogpost was unclear about that.
The BlockSpring library just lets people post their own work onto the BlockSpring home page (www.blockspring.com).
Our library just lets you specify variables in your code that a user should be able to input. Then when you push it to BlockSpring, we generate a forms and other inputs so users can change these variables.
Truth is the BlockSpring library works just as well with non-visualizations. We just figured it was more obvious to have people changing colors in a graph, then adjusting some other input in a js script.
Does that make sense? We're still working on how to phrase this idea :)
Re: Show HN: Turn JS visualizations into data products anyone can use
#4It's a JS visualization library. I don't see any special "anyone can use it" features. The demo sure seems to require the user to program in JS. What am I missing?
Hmm, so maybe our blogpost was unclear about that. The BlockSpring library just lets people post their own work onto the BlockSpring home page (www.blockspring.com). Our library just lets you specify variables in your code that a user should be able to input. Then when you push it to BlockSpring, we generate a forms and other inputs so users can change these variables. Truth is the BlockSpring library works just as w…
I'm on the same page as the parent comment. It literally looks like any other Javascript graph framework.
There seems to be no additional tools added to make it intuitive for non engineers. You want them to run web servers, save text documents and edit JSON markup. Not a single one of my non engineering coworkers would ever make it through this on their own. Further, if they make a mistake in the JSON syntax they're going to be ruined. Absolutely no chance that they figure out what's wrong. JSON syntax is pretty straightforward for engineers, but others aren't going to understand the requirement of quotes, escaping, etc. The JSON markup has a ton of parameters that aren't explained and aren't super obvious.
I understand what you're trying to provide by what you've just stated, but this product definitely isn't that, unfortunately.
Re: Show HN: Turn JS visualizations into data products anyone can use
#5It's a JS visualization library. I don't see any special "anyone can use it" features. The demo sure seems to require the user to program in JS. What am I missing?
I think the missing piece is BlockSpring won't help you code your visualization, but using the API auto-generates a UI so non-engineers can load in their own data, customize, etc.
Here's a link to a finished product: https://www.blockspring.com/graph_templates/83
Re: Show HN: Turn JS visualizations into data products anyone can use
#6Earlier quoted context omitted.
Hmm, so maybe our blogpost was unclear about that. The BlockSpring library just lets people post their own work onto the BlockSpring home page (www.blockspring.com). Our library just lets you specify variables in your code that a user should be able to input. Then when you push it to BlockSpring, we generate a forms and other inputs so users can change these variables. Truth is the BlockSpring library works just as w…
I'm on the same page as the parent comment. It literally looks like any other Javascript graph framework. There seems to be no additional tools added to make it intuitive for non engineers. You want them to run web servers, save text documents and edit JSON markup. Not a single one of my non engineering coworkers would ever make it through this on their own. Further, if they make a mistake in the JSON syntax they're…
Got it - just updated some language in our blog post since this was clearly confusing :)
Also added a link to the main page.
When an engineer does all that code, it gets posted to the front page of blockspring.com. That front-page definitely does not require code to use.
Thanks for pointing this out
Re: Show HN: Turn JS visualizations into data products anyone can use
#7Earlier quoted context omitted.
Hmm, so maybe our blogpost was unclear about that. The BlockSpring library just lets people post their own work onto the BlockSpring home page (www.blockspring.com). Our library just lets you specify variables in your code that a user should be able to input. Then when you push it to BlockSpring, we generate a forms and other inputs so users can change these variables. Truth is the BlockSpring library works just as w…
I'm on the same page as the parent comment. It literally looks like any other Javascript graph framework. There seems to be no additional tools added to make it intuitive for non engineers. You want them to run web servers, save text documents and edit JSON markup. Not a single one of my non engineering coworkers would ever make it through this on their own. Further, if they make a mistake in the JSON syntax they're…
You've completely missed the point. The site is for developers who make visualisations to be able to allow users to use the visualisations with their own data. It requires you to first create the vis code, then use the Blockspring API to wrap the data source, then the website auto-generates a data upload form that populates the plot.
Re: Show HN: Turn JS visualizations into data products anyone can use
#8Earlier quoted context omitted.
Hmm, so maybe our blogpost was unclear about that. The BlockSpring library just lets people post their own work onto the BlockSpring home page (www.blockspring.com). Our library just lets you specify variables in your code that a user should be able to input. Then when you push it to BlockSpring, we generate a forms and other inputs so users can change these variables. Truth is the BlockSpring library works just as w…
I'm on the same page as the parent comment. It literally looks like any other Javascript graph framework. There seems to be no additional tools added to make it intuitive for non engineers. You want them to run web servers, save text documents and edit JSON markup. Not a single one of my non engineering coworkers would ever make it through this on their own. Further, if they make a mistake in the JSON syntax they're…
Blahah got it right! Sorry but it's our bad. We're updating the post right now to clarify.
Re: Show HN: Turn JS visualizations into data products anyone can use
#9I think this is a cool idea, and the blog post made sense. This is a really nice way of making visualisations reusable.
Judging by how others have missed the point though, you might want to work on simplifying the pitch. How about starting the post with a simple diagram explaining the flow like:
(code your visualisation) -> (add the BlockSpring API) -> (we generate a web interface for your visualisation) -> (now anyone can use their data with your visualisation)
Re: Show HN: Turn JS visualizations into data products anyone can use
#10Earlier quoted context omitted.
I'm on the same page as the parent comment. It literally looks like any other Javascript graph framework. There seems to be no additional tools added to make it intuitive for non engineers. You want them to run web servers, save text documents and edit JSON markup. Not a single one of my non engineering coworkers would ever make it through this on their own. Further, if they make a mistake in the JSON syntax they're…
You've completely missed the point. The site is for developers who make visualisations to be able to allow users to use the visualisations with their own data. It requires you to first create the vis code, then use the Blockspring API to wrap the data source, then the website auto-generates a data upload form that populates the plot.
As someone unfamiliar with the product entirely, this point was very non-obvious. Especially since nothing on the original page linked to the main ui.