undefined | Better HN

0 pointsrecursivedoubts3y ago0 comments

hyperview is a hypermedia that exposes native mobile features directly within the hypermedia

you wouldn't create an internet out of hyperview-apps, rather it is a way for you, a developer of a mobile application, to get the benefits of a hypermedia approach (e.g. versioning becoming much less of an issue, vs. app-store updates) while not giving up on native mobile behavior

it is open source, and I think it's one of the most innovative uses of hypermedia I've seen in the last decade:

https://github.com/instawork/hyperview

0 comments

4 comments · 1 top-level

wvenable3y ago· 3 in thread

It's an app builder not a hypermedia client. It's a pretty slight semantic difference but when we're talking about REST APIs for 3rd party clients then hyperview isn't really relevant to the discussion.

recursivedoubtsOP3y ago

I don't see how you can say it isn't a hypermedia client: it is a client that interprets hypermedia, just like the canonical hypermedia client, a web browser.

It's not an internet hypermedia client like a browser, with general access to a broad network of different sites/applications, but the core mechanic satisfies REST and the format being transferred is a hypermedia.

wvenable3y ago

Because it's doesn't have general access to a broad network of different sites/applications it's not a hypermedia client. It's a client for a single service that uses hypermedia is an implementation detail.

An HTML client that can only view Facebook is not a browser, it's a Facebook client.

The point of the article is about how REST should contain all the information needed to traverse a service. But hyperview is for a building a single client/server application where the developers always know the entire interface. So that is the way that it's irrelevant to the discussion.

recursivedoubtsOP3y ago

I dunno man, I don't see anything about "a broad network of different sites" requirement here:

https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arc...

A hyperview-based application has the exact same defining characteristic of a RESTful web application: there is a single URL that is entered, and beyond that all actions are afforded through hypermedia controls. All the information needed to traverse the service is encoded in responses, and no knowledge of the entire interface is needed by the client. Seems relevant to me.

I certainly agree it isn't a general purpose browser, but web browsers are only an instance of a hypermedia client, not the definition of one.

1 more reply

j / k navigate · click thread line to collapse

0 comments

4 comments · 1 top-level

wvenable3y ago· 3 in thread

recursivedoubtsOP3y ago

I don't see how you can say it isn't a hypermedia client: it is a client that interprets hypermedia, just like the canonical hypermedia client, a web browser.

wvenable3y ago

An HTML client that can only view Facebook is not a browser, it's a Facebook client.

recursivedoubtsOP3y ago

I dunno man, I don't see anything about "a broad network of different sites" requirement here:

https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arc...

I certainly agree it isn't a general purpose browser, but web browsers are only an instance of a hypermedia client, not the definition of one.

1 more reply

j / k navigate · click thread line to collapse