Comment by cryptonector

> JSON rest api are just hypermedia rest api but with the data compressed. The compression format is json and the dictionary are the hypermedia relations previously passed in the client.

Yes.

> It’s 2025, the client don’t need to be generic and able to surf and discover the internet like it’s 2005.

No. Where the client is a user-agent browser sort of application then it has to be generic.

> The database is consumed via APIS distributed in two parts: first the client (a lib), second the data: json.

Yes-ish. If instead of a hand-coded "re-hydrator" library you had a schema a schema whose metaschema is supported by the user-agent, then everything would be better because

a) you'd have less code,

b) need a lot less dev labor (because of (a), so I repeat myself),

c) you get to have structured data APIs that also satisfy the HATEOAS concept.

Idk if TFA will like or hate that, but hey.