chadtmiller.com/hud
A remote MCP server that shows atproto records as interactive UI inside MCP Apps hosts
place.hud.hudkit 0.3.0 Latest 5 packages
0
0
A remote MCP server that shows atproto records as interactive UI inside MCP Apps hosts
place.hud.hudkit 0.3.0 Latest 5 packages
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'ssignIn), the account menu (frame.account), story pages (a route'spagerandunder), deep links and tapped notifications opened as routes, and the theme from the app file'slook.Grain wrote it for iOS:
ios/Grain/on grain'sfeature/hudis ~2,230 lines (Shell.swift784,StoryPager.swift412,SignInSheet.swift365,LevelScreen.swift347,Config.swift173,GrainApp.swift149), nearly none of it Grain's own. Its Android app on hudkit needs the same again. The web has this already:@hud/shelldraws an app from its app file, and Grain'snext/only hosts it.What's missing is a turnkey shell in each kit, as
@hud/shellis on the web:HUDApp(appFile:)in SwiftUI andHudApp(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.