marvinsu on Nostr: “ In many cases, these apps should use crypto as little as possible. Accept credit ...
“
In many cases, these apps should use crypto as little as possible.
Accept credit card payments.
Abstract away as much wallet complexity as possible while letting users retain their username.
Cover gas fees.
Don’t issue a token.
Don’t decentralize governance.
Don’t make grand roadmap promises.
Just let the users use the product for the thing the product does best, with the added benefit that they can up and leave to the next product on the protocol and bring their connections and data with them.”
a great read from:
https://www.notboring.co/p/small-applications-growing-protocolsPublished at
2023-05-10 01:18:12Event JSON
{
"id": "818b0aec1f1b69817c02d9a733b0cc3322eb79aec1f8cd3ca852c134d4f1fb55",
"pubkey": "cdf7f2d5b1b3140de605604652fc3cad8db195877cfc558d8ee8295ef0ff636e",
"created_at": 1683681492,
"kind": 1,
"tags": [],
"content": "“\nIn many cases, these apps should use crypto as little as possible. \n\nAccept credit card payments. \n\nAbstract away as much wallet complexity as possible while letting users retain their username. \n\nCover gas fees. \n\nDon’t issue a token. \n\nDon’t decentralize governance. \n\nDon’t make grand roadmap promises. \n\nJust let the users use the product for the thing the product does best, with the added benefit that they can up and leave to the next product on the protocol and bring their connections and data with them.”\n\na great read from:\n\nhttps://www.notboring.co/p/small-applications-growing-protocols",
"sig": "bfb1283ab6b8852c03ae5c2d48f57d27e973b6e76ef8d7c3b23aa3dd1916d982589b068ddb29c5e60fb8c9817db64fe6bbf0cb5710a532fc30117a81169d3779"
}