A customer emailed at 2:37am. We shipped their list by teatime.
One of our early merchants sent a numbered feedback list at 2:37 in the morning. It caught a real bug we'd missed. Most of it shipped the same day. Being small is the whole point.
The email arrived at 2:37 in the morning. One of our early merchants was two and a half hours into testing their new shop, and instead of going to bed they wrote us a numbered feedback list. Numbered. At that hour I can barely number my own thumbs.
Before I get to the list, a confession. We'd gone quiet on them for about a week beforehand. Heads down building and not saying much. So our reply opened with an apology, not a changelog. If you've ever emailed a support inbox and watched a week go by, you know how it feels from the other side. We'd rather own the silence than pretend it didn't happen.
Then we read the list. It was excellent. It was also mildly humiliating, which is how you know feedback is the good kind.
Item one: the currency bug
Their store was set to USD in Stripe. Their product pages showed GBP. Not converted, just wrong. Confident little pound signs on a shop that had never seen a pound in its life.
We dug into it that morning. The currency column in our database never synced from Stripe. It sat there holding its default value, looking plausible and being wrong. Here's the bit that stings: we found that bug in the code on the same day the customer found it in their shop. They'd had the product for two and a half hours. We wrote it. 🤦♂️
Fixed the same day. Currency now syncs from Stripe, as it always should have.
The rest of the list
No way to re-order products. They wanted their headline game at the top of their shop, and there was no control for that anywhere. Fair. By the afternoon there was a Shop order toggle with move arrows. Click, the product moves up, done.
Sync spinners that spun at nothing. A spinner is a promise. Some of ours were promising work that had already finished, or had never started. Fixed.
The hidden transparency trick. They'd discovered that our colour fields accept 8-digit hex, the kind with opacity baked into the last two digits. It worked. We had never told a single soul it worked. Congratulations to them on finding a feature we forgot to mention. It's now documented and properly supported, rather than accidentally supported.
Why this was even possible
Mytho is a very small company. Small enough that the person reading your feedback email is the same person who wrote the bug you're describing. There's no ticket queue where good ideas go to age. A morning email turned into shipped features by teatime because nothing stood between the reading and the doing.
Big platforms can't work like this, and that's fine. Their process exists for good reasons at their scale. But you're not at their scale and neither are we. At our size the deal is simple: fewer layers between your feedback and your fix, because there are no layers.
And let's be honest about what happened here. A tester who stays up past 2am with your product and writes down everything that bothered them is doing free QA, and we know it. That list was worth more than most of our test suite. Especially the part of the test suite that was meant to catch item one.
Send us your list
If something in Mytho bugs you, email [email protected]. Numbered lists welcome. Timestamps of questionable hours welcome. A human reads every message, usually the same human who caused the problem, and occasionally your fix ships before lunch.