Volbohel

Hi, one of the makers of RecipeUI. Happy to hear this is something you liked! We're still finding edge cases when it comes to parsing cURL commands, so if you find any that we missed please file an issue or send us a message (here or discord).

Also glad to hear any other feedback you have :)

Will follow up tomorrow! Our initial product had import OpenAPI schema, but we temporarily removed it after finding a few bugs.

Will follow up tomorrow! Our initial product had import OpenAPI schema, but we temporarily removed it after finding a few bugs.

Desktop App is better because it directly makes the request!

Web app will have a custom proxy filter or just allow you to make the request if CORS is not an issue soon. We’ll add this to a settings panel.

Thanks for being this up, we’ll make this more specific on our GitHub

GraphQL is in our timeline for the next 2 weeks! Let us know if you have a favorite GraphQL API so we can add it in our public collection.

Currently, we're not convincing enough for the team use case that tackles many of the things you're describing (especially auth). Thanks for the feedback!!!

We're closely working on an API Storybook that'll be more native to a codebase and a service. Would love to reach out and hear more about your Postman experience!

Looking forward to your feedback when you use it! Currently we validate with mappings from TypeScript to JSONSchema. OpenAPI is definitely a gold standard, but I think JSONSchema is fairly strong as well.

We're still considering better typing solutions like ZOD or OpenAPI wrappers, but our focus right now is core feature parity as an API tool.

We'll do a better job with written documentation! We forgot that video isn't always a medium that people prefer.

Hoppscotch is great! We have the same mindset as the founder that most API tools are outdated and were built a long time ago.

Many API tools are lightweight reskins of Postman and we truly wanted to offer something different. Which is why we're leading with a type-safety angle and we're looking to innovate with other ideas! +1 to @easygenes comment's below

Really nice embarrassing catches, thank you for flagging and debugging!!! Patch fixed both of these :)

Storing secrets in the cloud has been a top concern for me, which is why we don't do it and one of the main reasons why the code is open sourced.

Currently secrets are just stored locally on desktop and web via IndexDB. I'd love to hear people's thoughts on this as well!

We're thinking of a way to sync this with git or some link to a schema somewhere (e.g an OpenAPI yaml spec).

For now, you'll have to manually write the TypeScript interfaces but we'll support sharing APIs soon!

I was almost convinced to use electron because it uses the same language as the frontend (JS) and has "better" support for production apps.

Ultimately went with Tauri because more people need to push the needle with alternatives and wanted to be there. Most ppl that build electron apps can definitely use Tauri because they're probably not writing much backend code.