Is there any sort of interface/idiom for representing "A Bubbletea component"?

[andyhaskell]

I noticed that in Bubbles, many components have methods that are similar to the ones implementing a Bubbletea Model, with the key differences between them being:

• There is not an Init method.
• Since Bubbles components don't implement the Bubbletea Model interface, their Update methods return the type of the component itself, rather than a Model.

Something I think would be useful is if there was an interface, or common idiomatic approach for representing a component. For example to represent things like:

• Test code that works with multiple types of components
• Building a Focusable interface on top of the Component interface
• Building a Group component that manages focus state between components, and renders them together with something like the Lipgloss JoinHorizontal/JoinVertical functions

One approach I am experimenting with, based on Model, is

type Component interface {
	Update(msg tea.Msg) (Component, tea.Cmd)
	View() string
}

then building a Focusable interface like:

type Focusable interface {
	component.Component

	Focused() bool
	Blur()
	Focus() tea.Cmd
}

and wrapping Bubbles components to use this interface like:

type Table struct{ table.Model }

func (t *Table) Update(msg tea.Msg) (Component, tea.Cmd) {
	tbl, cmd := t.Model.Update(msg)
	t.Model = tbl
	return t, cmd
}

func WrapTable(m table.Model) Component { return &Table{m} }

Has anyone heard of other approaches for this?