Building on HF
3980.2 TFLOPS 97 followers ·
63 following None yet
reacted
to
their post with 🚀 1 day ago Most API tooling is stuck in 2010.
They still assume every API request is a form: with a fixed layout, fixed sections, fixed mental model regardless of how your API actually works.
But is UI useful? Why do we accept all this copy-pasting, clutter, and inconsistency as “normal”?
- Headers that are not needed.
- Bodies that are not used.
- Params scattered across requests
And somehow we call that “API documentation.”
Most API clients are optimized for filling out forms, not for designing, understanding, or maintaining APIs.
hashtag#Voiden was built around a different idea:mThat APIs are systems.
And since systems are modular, the API client should be modular as well.
In Voiden, everything is a Block: Endpoints, headers, query params, bodies, files. You assemble requests from parts, reuse them across projects, and version them like code.
No fixed forms, No fake simplicity, No pretending APIs are paperwork.
If you think API tooling should evolve past “better forms,” Voiden is worth a look.
Take a look here : https://voiden.md/
reacted
to
their post with 🔥 1 day ago Most API tooling is stuck in 2010.
They still assume every API request is a form: with a fixed layout, fixed sections, fixed mental model regardless of how your API actually works.
But is UI useful? Why do we accept all this copy-pasting, clutter, and inconsistency as “normal”?
- Headers that are not needed.
- Bodies that are not used.
- Params scattered across requests
And somehow we call that “API documentation.”
Most API clients are optimized for filling out forms, not for designing, understanding, or maintaining APIs.
hashtag#Voiden was built around a different idea:mThat APIs are systems.
And since systems are modular, the API client should be modular as well.
In Voiden, everything is a Block: Endpoints, headers, query params, bodies, files. You assemble requests from parts, reuse them across projects, and version them like code.
No fixed forms, No fake simplicity, No pretending APIs are paperwork.
If you think API tooling should evolve past “better forms,” Voiden is worth a look.
Take a look here : https://voiden.md/
posted an
update
1 day ago Most API tooling is stuck in 2010.
They still assume every API request is a form: with a fixed layout, fixed sections, fixed mental model regardless of how your API actually works.
But is UI useful? Why do we accept all this copy-pasting, clutter, and inconsistency as “normal”?
- Headers that are not needed.
- Bodies that are not used.
- Params scattered across requests
And somehow we call that “API documentation.”
Most API clients are optimized for filling out forms, not for designing, understanding, or maintaining APIs.
hashtag#Voiden was built around a different idea:mThat APIs are systems.
And since systems are modular, the API client should be modular as well.
In Voiden, everything is a Block: Endpoints, headers, query params, bodies, files. You assemble requests from parts, reuse them across projects, and version them like code.
No fixed forms, No fake simplicity, No pretending APIs are paperwork.
If you think API tooling should evolve past “better forms,” Voiden is worth a look.
Take a look here : https://voiden.md/
View all activity view post Most API tooling is stuck in 2010. They still assume every API request is a form: with a fixed layout, fixed sections, fixed mental model regardless of how your API actually works. But is UI useful? Why do we accept all this copy-pasting, clutter, and inconsistency as “normal”? - Headers that are not needed. - Bodies that are not used. - Params scattered across requests And somehow we call that “API documentation.” Most API clients are optimized for filling out forms, not for designing, understanding, or maintaining APIs. hashtag#Voiden was built around a different idea:mThat APIs are systems. And since systems are modular, the API client should be modular as well. In Voiden, everything is a Block: Endpoints, headers, query params, bodies, files. You assemble requests from parts, reuse them across projects, and version them like code. No fixed forms, No fake simplicity, No pretending APIs are paperwork. If you think API tooling should evolve past “better forms,” Voiden is worth a look. Take a look here : https://voiden.md/ See translation
List of Alternatives of Postman
