4 ms·
Hello, I'm the author, and this is my attempt at explaining why just slapping a "link" property in your JSON response doesn't make for a REST-ful architecture.
by recursivedoubts 4y ago
Hello, I'm the author, and this is my attempt at explaining why just slapping a "link" property in your JSON response doesn't make for a REST-ful architecture.
I think this should be considered good news for JSON API developers: they can set aside REST, HATEOAS and all that noise, and just focus on building good, rich data APIs.
- bradgessler 4y agoLots of people get tripped up by limitations of web browsers. https://hyperview.org/ https://hyperview.org/ should be held up really high to show what’s possible if we think outside of the browser. It looks like it’s optimized for Material UIs, but we can imagine what it might look like for other UIs like Apple, etc. Apple has given us a glimpse of that with Apple TV Markup https://developer.apple.com/documentation/tvml https://developer.apple.com/documentation/tvml. While it’s not a hypermedia client, it does show us what UIs are possible via markup. https://native.live/ https://native.live/ is another glimpse, though the financier of this project has said on Twitter that his company is strongly incentivized to keep it “Elixir only”, so I’m not sure where it puts that project with respect to a SwiftUI hypermedia client.