Feature Request: Deep Links as an alternative to some Wallet Connect features.

[AbandonedLand]

My Thought Process:

I dislike wallet connect from both and end user point of view and a developer's point of view. It feels like wallet connect is an unnecessary step for the tasks I want to accomplish like taking an offer, maybe even making and submitting offers.

My Desired Workflow Example:

I would like to be able to "Go Shopping" on dexie / mintgarden / etc. I would like a "Add to Cart" feature that would send the offer file to a new section of the sage wallet.

These offers would end up in the new section of sage:

The Cart section should:

• Display offer terms clearly (offered and requested should be in terms of what the user is paying and receiving)
• Only show offers that can be accepted
• Have multi select enabled so you can accept all the offers at once (Using the existing sage rpc for offer joining)
• Have filter and sort options
• Have a way to remove unwanted offers

End User Experience:

As a user, I click add to cart button on any website. Sage already knows how to handle the uri and adds the offer to my cart. I can go to my cart at any time to view what is in there and accept the offers i want and remove the ones I don't.

Web Developer Experience:

I can create an anchor tag that follows the rules for the deep link. This would simplify my workflow as a developer significantly. I don't need feedback from the user's wallet because I can just watch my developer's wallet to see if the offer is taken.
Example:
<a href="sage://add_offer/offer1qqr83wcuu2rykcmqvpsf40h3y2...">

Other Potential:

It might be nice to add other deep links for things like:

• Create_offer
• Review_sign_spend_bundle

These should have some sort of pending state where they are sent and wait for the wallet user to approve them.

[AbandonedLand]

The Create_offer endpoint should also accept a url for where to submit the offer file.
Something like:
sage://create_offer?offered_asset_id=abc123&offered_asset_amount=1000&submit_to="https://api.dexie.space/v1/offers"

Sage probably just needs to assume all submit_to are POST to the endpoint and accept
'{ "offer": "offer1......"}'

But being able to somehow describe other parameters might be nice to have, but that seems like something the website operator can figure out on their own.