4 ms·
I meant a user friendly client, not something aimed at API developers. Sure you can create something which is aimed at Developers, but it's not presenting the d
by richardwhiuk 10y ago
I meant a user friendly client, not something aimed at API developers. Sure you can create something which is aimed at Developers, but it's not presenting the data in a way any user would understand, or in a way that a UX expert can flex.
Fundamentally, your display logic should not be linked to your API schema, but HATEOAS essentially enforces that, because you can't predict what links will be available.
- icebraining 10y agoyour display logic should not be linked to your API schema Why not? The whole point of HATEOAS is to design your API schema in function of your application flow. You know, just like we do on websites.
- lucideer 10y ago> I meant a user friendly client, not something aimed at API developers. Sure you can create something which is aimed at Developers Just for clarity, are you talking about API Developers or API Client Developers? I would see the primary beneficiaries of HATEOAS being developers consuming your API - i.e. client developers.