Read on Twitter
Build in public.
Launch in public.
Fix in public.
When we launched yesterday and sent people to our swag store to try Fast Checkout for the first time ever, we knew there would be some bugs. It’s inevitable.
Launch in public.
Fix in public.
When we launched yesterday and sent people to our swag store to try Fast Checkout for the first time ever, we knew there would be some bugs. It’s inevitable.
And while it worked as intended for a majority of users, it didn’t work that way for everyone.
Some bugs we admittedly should have caught beforehand, while others were only going to be caught after we released Fast Checkout for the world to see.
Some bugs we admittedly should have caught beforehand, while others were only going to be caught after we released Fast Checkout for the world to see.
The benefit of doing it this way is that we’ve quickly identified 99% of the issues we need to address.
The downside is that some people felt frustrated by their first ever Fast Checkout experience.
The downside is that some people felt frustrated by their first ever Fast Checkout experience.
We’ve been heads down fixing bugs for the past 20 hours.
Issues like redirect in order-received emails, duplicate emails, form field errors, country postal codes issues, and a handful of others. Most of these issues have already been resolved, and some we’re still working on.
Issues like redirect in order-received emails, duplicate emails, form field errors, country postal codes issues, and a handful of others. Most of these issues have already been resolved, and some we’re still working on.
But don’t think for one second this will slow us down (quite the opposite actually).
We’re going to keep building for the world to see, launching for the world to see, and improving for the world to see. We’re Fast. It’s just who we are.
We’re going to keep building for the world to see, launching for the world to see, and improving for the world to see. We’re Fast. It’s just who we are.
