OK, then that's the core disagreement: I think the uniform interface and the benefits of a RESTful network architecture are useful even if the software you are using isn't a "browser". In the case of hyperview, a major benefit is that you can update your mobile application without redeploying the client, exactly because of that uniform interface. That's why the creator went with the RESTful approach over a more traditional mobile app network architectures.
There's nothing new about that model; having a client interpret an application from a server is as old as computing itself.
> I think the uniform interface and the benefits of a RESTful network architecture are useful even if the software you are using isn't a "browser".
Except it can't be used for anything other than a "browser" either a real browser or something like hyperview. That's fine but it hardly suggests that it should be necessary.
