How Can We Improve Mockingbird for Better Developer Experience?

Hello DEV community!

I’ve been working on Mockingbird, a tool designed to enhance API development workflows by providing features like multiple responses for each route, presets for easy scenario switching, Git integration, and more. My goal is to make Mockingbird a seamless and powerful tool for developers.

I’d love to hear from you all:

1. What features would you like to see in Mockingbird that would make it more useful for your projects?
2. Are there any pain points you currently experience with mock servers that Mockingbird could address?
3. How important is the support for WebSocket and gRPC in your workflow, and what specific functionalities would you need?

Your feedback and suggestions will be incredibly valuable in guiding the future development of Mockingbird. Thank you!

Comments

[Fraser Young]

Very initial take is that the intro to the readme could use a bit more clarity. Takes a bit of time to understand just what it does that might be different than alternatives.

[ozkeisar]

Thanks!
You mean like an comperation section?

[Enoch Osarenren]

Hello everyone, I hope you're all doing well. I recently launched an open-source project called GraphQLPlaceholder, and I'd love your support. Please check it out and give it a star on GitHub github.com/enochval/graphql-placeh.... Your support would mean a lot to me and help immensely in the project's growth.

Thank you.