James Moschou

🛠 Founder of @getcriteria ( — the collaborative tool for designing APIs

❤️ API design, tools and product strategy

Former Product Mgr, Eng
🏳️‍🌈

[James Moschou @jcmosc]

@landonepps Once the code works :) I haven't actually run it and I had to learn C++ as I went.

[James Moschou @jcmosc]

@landonepps I'm not building anything to do with a user interface, but there are enormous parallels. Instead of SwiftUI -> DisplayList -> pixels, you can think of it as [Name TBD] -> Emit Instructions -> source code bytes

[James Moschou @jcmosc]

@landonepps I'm building a no-code app builder that will use an incremental computation engine, and I think the type system and expressivity of Swift is unmatched for what I want to be able to do.

[James Moschou @jcmosc]

For any Wordle fans out there, I created a similar daily puzzle...

Find the number sequence in as few guesses as possible
https://t.co/VjPIZ2gjOq

[James Moschou @jcmosc]

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 --> https://t.co/1yi8HBae1M

[APIMatic.io @APIMatic]

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

https://t.co/3IXpjhc28A

[Niklas Begley @NiklasBegley]

Friend of mine @jcmosc has built a really cool tool for building flow diagrams that integrate with your OpenAPI spec 👀

Take a look at https://t.co/mHvCCvHfmn

[James Moschou @jcmosc]

Try it out and let me know what you think! (And watch this space)

[James Moschou @jcmosc]

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
https://t.co/GKlHtQNwyp

[James Moschou @jcmosc]

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.

[Criteria @getcriteria]

🚀🚀🚀
Here's a quick roundup of what we released this May:

1. Sync Spectral rulesets
2. Configure API styles
3. Import Swagger 2.0 documents

Keep reading on...

[James Moschou @jcmosc]

@PatThePM I've seen design teams conduct time-on-task studies, and work out the cost savings or efficiency improvements for the customer. Say a task used to take x minutes and now takes y minutes, and it's done 20 times a week. What does that add up to over the year for the customer?

[James Moschou @jcmosc]

@Erwin_AI yeah fair. Though you could be like "hey when you get a minute I would love to chat about what you're working on" and let them get back to it

[James Moschou @jcmosc]

@Agustarson It definitely helps, but you have to be good at compartmentalising. You're job is to let the team arrive at a solution themselves, which means biting your tongue a lot.

[James Moschou @jcmosc]

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?

[James Moschou @jcmosc]

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.

[James Moschou @jcmosc]

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.