KMac pfp
KMac
@kmacb.eth
The volume of manifest-related issues in the ‘mini’ app dev chat is the clearest signal we’ve got: it’s not working. Well-intended? Sure. But rushed legacy thinking and now, it’s a blocker. Let’s not pretend the fix is just better docs or more fields. It’s a brittle interface. Instead of patching it, let’s re-architect it. Start from the protocol’s promise: permissionless, portable, composable, interoperable apps. Imagine if: Any client was able to load, index, & execute ‘mini’ apps like browsers do with websites Deep link routing between apps should just work wo coordination Shared ephemeral state (like react context or sessionStorage) should enable app chaining in a flexible context-container ***A registry layer*** should exist to power search, surfacing, and cross-app applications discovery. I buried the lead! Devs want distribution yes but guess what they also have every incentive create it. https://kmacb.eth.sucks/D58ABF46-1515-4FDE-B403-B08D9AB7C7AA/
2 replies
2 recasts
3 reactions

Samuel ツ pfp
Samuel ツ
@samuellhuber.eth
I wouldn’t do it now but see how going forward an FID -> Apps mapping (need multiple, not just one) would live on Snapchain
1 reply
0 recast
1 reaction

Samuel ツ pfp
Samuel ツ
@samuellhuber.eth
Didn’t expect the mini app linked to be a full blog post. Didn’t see a link and note of it 😅
1 reply
0 recast
1 reaction