Why is Borges (or Seaside) coupled to an html/browser interface?

It seems that the Component model (composable logical 'panes' with
application logic) and the modelessness and free 'Back' button
functionality, could both be useful outside the context of an HTML browser.

It seems that Components, rather than generating HTML through a renderer,
could generate some kind of logical 'Interactor' descriptions. Different
Renderers could then map this differently:

  - HTML renderer:
     - map to (a part of) an html page, or to some sequence of (part of)
html page
  - Other UI renderer:
     - different mapping e.g. to native widgets

A little bit like XForms.

Sound feasible? Worth investigating?