Half-baked idea. Would it make sense to use contractURI() to add Mini App metadata to a smart contract?

1. Provide users with the option to interact with the contract using a mini app. That's the definition of a dApp, right?

2. Let users subscribe to smart contract notifications: Vesting period is over, new liquidity pool, incentives, mint has started, etc.

Dad, geek, conversation liquidity provider. vrypan.net (home), @l--o--l (fun). devcoin:$lemon3

Why do you have to provide high assurances for something like this? 

What's the alternative today?
- Subscribe to email notifications
- Follow account on twitter, farcaster
How are they better?

Also, notifications are a small part of it. Providing a GUI to contract non-standard functions is probably more important.

riffing...

any transfers by addresses I follow
any transfers > $ threshold
any holdings changing by > X%
any holdings falling below a % threshold

how would you "guarantee" the notifications would actually get sent? one point of having it on a smart contract is that the world computer makes sure the code runs when it's called upon to run. A Mini App, or a dApp, is just some dude's static files, a little render function, and maybe a glorified reverse proxy