3 ms·

What I couldn’t understand was that there were times where something like ApplePay was a clearly superior way to pay. E.g. JavaScript says the user has it confi

What I couldn’t understand was that there were times where something like ApplePay was a clearly superior way to pay. E.g. JavaScript says the user has it configured and able to make payments, so one click payments were actually possible. At least publicly, Fast never addressed this, and insisted on requiring the user to log into Fast to make a payment even when it was a worse option. Browsers like Safari are explicitly designed to prevent people from remaining logged into third party sites like Fast. All this was just brushed under the rug and instead it was just a bunch bluster on how Fast was a revolution. At least Bolt allows payment via ApplePay, and seems more about doing whatever it takes to maximize each seller’s conversion, rather than having an ulterior motive to push its own brand everywhere.

samhw 5y ago
I briefly made an MVP of 'basically Fast', and had to deal with mobile Safari, so I can tell you (hell, I can give you the code if you want it). We had to load our own site in a zero-sized iframe, at a specific endpoint which ran a script that read the cookies and sent them over the Window.postMessage API to the merchant page, where our JS was running and intercepted the cookie contents. But that was an MVP, and I was uncomfortable about the security implications even so - not sure how Fast's engineers hacked it together, if they even did. The two of us ditched it when we realised how inhospitable the economics were, but even then we knew Fast's shitty play was bound to fail, and I heard the news from my prospective cofounder sending me a text ("we called it!") when it happened...