Re:I made nodb, a RESTFful API to store and fetch JSON
by primitivesuave on Saturday May 27, 2023 @06:25AM
(#36093532)
First let me say that the minimal interface you've designed for the dashboard is lovely. But also consider that as you talk to potential customers for this, the hardest sell is "send your data to a third party" and the easiest sell is "here is something that will save your developer's time". The biggest problem it seems like most people are facing now is getting their data transported between services.
[ Parent
| on HN ]
Re:I made nodb, a RESTFful API to store and fetch JSON
by bjornsing on Saturday May 27, 2023 @09:26AM
(#36094639)
> The biggest problem it seems like most people are facing now is getting their data transported between services.
Could you elaborate a bit?
Re:I made nodb, a RESTFful API to store and fetch JSON
by primitivesuave on Saturday May 27, 2023 @11:56AM
(#36095750)
Pretty much every tech company is built on a stack of SaaS products (Google suite, CRM tool like HubSpot, etc), and it seems like a lot more innovation is going into integrating/standardizing their APIs.
If you're just focusing on making a pure developer tool, a good example of successful execution is cronitor.io.
Re:I made nodb, a RESTFful API to store and fetch JSON
by mk0y on Monday May 29, 2023 @02:35PM
(#36116596)
Thanks! And I fixed some bugs in the meantime. Yes, and the API should maintain its simplicity without making it super complex. And I'm still considering moving token to the headers instead of query params, as stated in one of the comments here. There are obvious pros and cons.