~ knotless Search/
↑↓ move↵ open⇧↵ all results

chadtmiller.com/hud

A remote MCP server that shows atproto records as interactive UI inside MCP Apps hosts

0
0

An app on HUDKit or hudkit has to write its own shell around the kit

Open
Open chadtmiller.com opened this issue 0 comments

What happened

An app built on HUD's native kits has to write its own shell around them. HUDKit (ios/HUDKit) and hudkit (android/hudkit) draw a resolved tree and read an app file's routes and push, but the app around them is each operator's to write: the frame (tabs as a bar, a rail or a sidebar), each tab's nav stack of tool results, sign-in by handle and its sheet (the app file's signIn), the account menu (frame.account), story pages (a route's pager and under), deep links and tapped notifications opened as routes, and the theme from the app file's look.

Grain wrote it for iOS: ios/Grain/ on grain's feature/hud is ~2,230 lines (Shell.swift 784, StoryPager.swift 412, SignInSheet.swift 365, LevelScreen.swift 347, Config.swift 173, GrainApp.swift 149), nearly none of it Grain's own. Its Android app on hudkit needs the same again. The web has this already: @hud/shell draws an app from its app file, and Grain's next/ only hosts it.

What's missing is a turnkey shell in each kit, as @hud/shell is on the web: HUDApp(appFile:) in SwiftUI and HudApp(appFile) in Compose, drawing the whole app from its app file (frame, stacks, sign-in, account, pager, links, push), with hooks for what an app adds (a camera, its own sheets). Grain's iOS shell and its Android counterpart then move into the kits, and an app's native client is its app file, its icon and a few lines.