One implementation detail that I worry about is how much friction would exist in the micro-transaction. For example, if I do this on my iPhone would it just go <ching> and then make the donation, or would it then pop up a little screen saying “pick your method of payment, then I double press the side button for apple pay, then it scans my face and I wait a beat”. I think it has to be the latter given iOS platform constraints (to stop scammers from just taking people’s money), but I think that might greatly reduce the “fun, friction-free” thing that I see as the draw here.
Oh dang. I definitely want it to be the former, not the latter. Maybe we can get around the iOS platform constraints somehow, e.g. when you press the button it doesn’t donate the money right away, but just adds it to an internal tally, and then once a quarter you get a notification saying ‘time to actually process this quarter’s donations, press here to submit your face for scanning, sorry bout the inconvenience’
I like this idea in the abstract.
One implementation detail that I worry about is how much friction would exist in the micro-transaction. For example, if I do this on my iPhone would it just go <ching> and then make the donation, or would it then pop up a little screen saying “pick your method of payment, then I double press the side button for apple pay, then it scans my face and I wait a beat”. I think it has to be the latter given iOS platform constraints (to stop scammers from just taking people’s money), but I think that might greatly reduce the “fun, friction-free” thing that I see as the draw here.
Oh dang. I definitely want it to be the former, not the latter. Maybe we can get around the iOS platform constraints somehow, e.g. when you press the button it doesn’t donate the money right away, but just adds it to an internal tally, and then once a quarter you get a notification saying ‘time to actually process this quarter’s donations, press here to submit your face for scanning, sorry bout the inconvenience’