🛠 Founder of @getcriteria (https://xitter.cf/t.co/BdmaPedtYW) — the collaborative tool for designing APIs ❤️ API design, tools and product strategy Former Product Mgr, Eng 🏳️🌈
Melbourne, AU
Joined November 2012
- Tweets422
- Following442
- Followers180
- Likes238
For any Wordle fans out there, I created a similar daily puzzle...
Find the number sequence in as few guesses as possible
producthunt.com/posts/sequen…
I'm so excited to attend #apidays Australia next week as a speaker!
My topic is "Mapping your business model to API design". Whether you're a tech person or from business, there will be something in it for you!
Register here --> ticket.apidays.global/event/…
James Moschou retweeted
Date and time information is so common in APIs that they can make or break your API's developer experience - evaluate different approaches based on your use case from @getcriteria
hubs.li/Q01ZxpXF0
James Moschou retweeted
Friend of mine @jcmosc has built a really cool tool for building flow diagrams that integrate with your OpenAPI spec 👀
Take a look at diagrams.criteria.sh/
ALT A screenshot of Criteria diagrams showing an authorization flow between the user, a web application, and an authorization server.
I've been a bit quiet on here, bootstrapping a collaborative design platform is definitely not easy...
So I'm going to pivot away from collaboration and release some mini products where folks can get value in seconds, starting with...
Criteria Diagrams
diagrams.criteria.sh/
Because the focus is on API workflows, you can import an OpenAPI file and autogenerate flows much more rapidly than general-purpose tools allow.
Since diagrams are intended to be published in public docs, they have a much more polished and professional appearance.
Been thinking about the future role of AI automation in APIs.
I think we're gonna see AI write code on the consumer side first. The provider side of API development is still very much led by humans.
3. AIs are excellent writing boilerplate code.
This makes AIs great at writing API clients and "glue" code.
Zapier says it takes about 2 weeks for a tool to integrate into their platform. An AI-powered Zapier could onboard any tool immediately.
Soon a large proportion of your API's consumers will not be developers, but AIs.
We'll be writings docs, not for developers, but for language models.
Maybe it's time to start using #aiexperience instead of #developerexperience?
I'm looking back at my old notes from customer conversations and I've got the digital equivalent of "can't read my own handwriting".
What automated transcription tools do people like that work with Google Meet?
#indiehackers
Thinking about writing about how to migrate an API platform from a code-first approach to an API-first/docs-as-code workflow. Based on experience.
Would this be useful to folks?
That feeling when you notice new signups to your startup 😃
Then you notice they're from your main competitor 😬