[O1111OOO]

Just wanted to comment on the clarity and effectiveness of the home page. Love it! So many user-friendly checkboxes are ticked off. Nice look, great description, plenty of examples, advanced usage section that's very easy to take in, credits at the bottom with some backend tech used, a welcoming contact link...

All of this accomplished (landing page and documentation) in just a few scrolls of the mouse. I went from novice to expert in a minute. There was a real effort to communicate with the end-user from an (empathic) end-user perspective.

Even the parsed json page listing a default 30 images (with credits) is easy to navigate with all the pertinent information available - including urls that open in a new tab (so a user doesn't lose their place on the origin page).

You mentioned in another comment that 400 million images are served per month. Yet... it has the feel (and performance and care) of a small static site.

[hliyan]

Exactly. It took me under 30 seconds of scanning through the page to understand most of the API. No fancy badges, abstract graphics or buzzwords, just a direct demonstration of the value. This is how product pages should be.

[dmarby]

Thank you for the kind words!

[yingw787]

This is what API homepages, or at least "Getting Started" pages, should feel like.

[necovek]

It was indeed good.

One minor nitpick is the use of "random" where they mean "arbitrary". :)

Also, it's still a bit unclear how caching of images would work when you append an arbitrary parameter: text implies none of the images would be cached (presumably because of cache headers or browser behaviour), but I'd prefer it if they were indeed cached by browsers as distinct images instead (iow, soft-reloading X/Y?something=foo will give you the same image).

Basically, I'd like them to figure out all the caching semantics and behaviour, and just do the right thing ;)

[vectorEQ]

seconded. very clear and easy to use. good design and nice idea!