Show HN: JSON For You – Visualize JSON in graph or table views (github.com)
After two years of improvement, I think it's time to share it with you all. Here’s a quick overview:
- Common features include validation, formatting, minification, and more.
- Visualize JSON in a graph or table view.
- Structured comparison with fallback to text comparison.
- Navigate though JSON using JSON pointer.
- Supports jq.
Would love to hear the community's questions, thoughts and comments!
87 comments
[ 2.8 ms ] story [ 181 ms ] threadI figured it was a link to documentation though
Does anybody know of any good components or libraries for that?
The other opensource json visualizer I found operates on the similar model as OP's project, but it also doesn't provide a standalone component.
https://github.com/AykutSarac/jsoncrack.com
https://github.com/egeozcan/json-tail/tree/master/data
also has storybook but no online demo I'm sorry :(
edit: ha, I also found the plain js/css/html version there, a surprise from past me https://github.com/egeozcan/json-tail/tree/master/data/legac...
It’s unclear what service requires the expense on your side that justifies a monthly cost. I think explaining those benefits on the pricing page would help you a great deal.
Additionally, people usually buy something for the value it has now, or a promised value which might materialize in the future and they consider realistic. So, if your tool has a legit reason for a subscription, people might pay for it. This means, server-costs on your side, which are realistic for the demanded price. Or a roadmap of fancy features which are actively worked on.
But paying for something regularly, where there are no ongoing costs on the sellers side, and no foreseeable positive changes in the value of the tool...this makes it really hard to reason about the cost&benefits. I mean, the tool will not change, the value is static, why pay for it again and again and again? This is like Walmart asking for a subscription for silverware..
Can I conduct a small survey? I previously considered offering a feature to store users' JSON in the cloud, but I didn't see the need since there's GitHub Gist, and you can always use that, so I didn't implement it. From your perspective, would you need such a feature?
I'm not sure how this would work well with the privacy-aspect and everything running locally, even if you upload them encrypted. And storage is cheap these days.
> From your perspective, would you need such a feature?
Personally, no. As a developer, I have many tools which need access to my data. And I also have many other files outside of JSON. So I need to have centralized place which all my software can equally easy access. So I don't really see the value in one specialized tool with specialized storage for me.
Maybe, people working mobile or in teams might have some value for this, but this is a very specialized group of customers. And I would think they will prefer something like Dropbox, Google Drive or OneDrive for sharing files. Maybe integrating this has more value for your customers. But then again, this is probably not an ongoing cost for you which would justify a subscription.
As you have processing as a selling-point, maybe you should try this and offer automatic remote-processing. People use tools like Zapier, IFTTT and Node-red for automating web- and service-related tasks or for business logic. Maybe you can find a special corner in terms of ability, price and/or simplicity, which is not covered well enough by the big tools. Some companies are really crazy with paying for hyper-specialized services just to let some laymen do their stuff.
Any plans to make an editor on top of this?
While I was looking at the image and trying to understand, the carousel moved to the next image. It's too fast, and I can't get back to the first image without it immediately switching me to the second image. I can't get it to sit still either and NOT switch to the next image. Some carousels pause themselves when the cursor is hovering over it, but this one did not pause when I did that. The only way I had enough time to digest the information was by right clicking on the image and opening it in a new tab.
This is why I use JQ, which I have seen tackle gigabyte-size files.
Disclaimer: I am the author and I regularly test it on JSON documents hundreds of MBs large.
I want the table view to support not just regular array but also complex object structures (like nested structures). The latter results in an irregular structure of tables within tables, and I currently don't have a good approach to implement this using a virtual list.
You will get a better ROI if you replace the pricing with a link to your socials/ website.
You’re competing in a very crowded market of generally free tools. Unless your offering is VERY good you’re going to struggle selling at all… $5-10 maybe? That’s about as much as I’d be willing to pay for a hyper-specific tool like this if it makes one of my tasks at hand a little easier.
If the only motivation for this product is money, then it will die in no time. Comparing the value I’m getting to the 7€ / month on Amazon prime, or the 10€ for Apple Music – that’s the value perception you’re competing against.
If you tell me you need 120€ a year from multiple customers to maintain and improve a json app good luck. One time purchase – get access – done. You can later upsell me with even more features in a v2 or whatever. I also doubt this tool has a lot of running costs to warrant this much.
Maybe if you work in SF and you make 300k a year so 10 bucks don’t mean much, but for the rest of the world 10$ is a lot of money / month.
1. The price is too high.
2. Dislike for subscription-based payments.
I have no problem with the first point, but I'm curious why everyone dislikes the subscription model so much? Or at the end of the day, is it really because the price is too high?
Because _everything_ is a subscription today, and even more of them make people angry. When a tool doesn't have any "infrastructure" costs per se, it rubs people the wrong way. Most don't want yet another subscription to manage
- With a buyout system, users perceive that they own the item after payment.
- With a subscription system, users perceive that they are renting the item after payment.
When there's a mismatch in expectations (I pay to own, but you only let me rent), users feel deceived and angry. The same issue occurs with the ownership of accounts in online games, where some game companies state in their terms of service that the game account belongs to them, not the user, naturally leading to user outrage.
OSS is dead.
Snappy, a lot of features. The diff tool seems useful.
The vis tool was neat but I don't often have that need.
I did get it to crash when I dumped a JSON file containing data on every programming language ever made.
Here's my user test: https://news.pub/?try=https://www.youtube.com/embed/ERpyG_f2...
Are you using CodeMirror for the left panel?
I wouldn't use GUI for this simply because piping data and mouseless env are more convenient to me. These are my other use cases:
- validation & auto fixing: fix-busted-json (python)
- tabular view : visidata (vd) can do this directly on json files. it has tons of other features like histogram, charts, sort, filter, edit, etc
- summarizing and querying: duckdb. Example: select sum(price), count(*) from 'orders.json'
- conversion: json2csv, it works both way
- diff: simply diff, but sometimes jq for ordering keys is required
This guy posted in some forum accusing you of attacking him. But Chinese coders roasted him so well, he deleted his original post. You might need some translation, but it's satisfying!
1. JSON Crack focuses more on visualization, whereas JSON For You aims to be a all-in-one JSON toolkit. This is why you'll find many buttons on JSON For You's page, leading to decreased readability and increased user learning curve (though I've tried my best to optimize this).
2. JSON Crack supports visualization for multiple data types including TOML and YAML, but JSON For You does not support this, nor does it plan to.
3. I've noticed JSON Crack offers AI functionalities to manipulate JSON data, but JSON For You will not pursue such features. Instead, it provides this through local tools like jq.
4. When it comes to comparison features, JSON Crack seems to provide graph-based comparison, which JSON For You does not do (nor is it its goal). Additionally, JSON For You offers text comparison, which JSON Crack does not.
Maybe I should provide a comparison table on the homepage to help everyone better understand the differences between the two products :)
You ought to call him out on social media, juxtaposing a screenshot of his website with yours for comparison.
His original reply:
> Belittling competitors is not a good competitive strategy, the community is smart and won't be fooled by it (https://news.ycombinator.com/item?id=32626873). If you want to promote something under my post, that's fine, people will make their choices. But if you're going to unjustly discredit JSON For You by ignoring the facts, I find that unwelcome and offensive. I suggest we compete by improving our products, rather than by smearing each other or engaging in price wars :)