5 ms·
I'd have to assume "supporting Danish credit cards" is lower on their list of revenue-impacting issues than you expect. If Denmark were a US state, it wouldn't
by smt88 6y ago
I'd have to assume "supporting Danish credit cards" is lower on their list of revenue-impacting issues than you expect.
If Denmark were a US state, it wouldn't even be in the top 20 in terms of population. If you assume that Denmark has lower usage of Tinder than US, CA, or UK, and then you assume that not all Danish people are paying with Danish credit cards (many of them would be using Play Store subscriptions, which seems like it would bypass the issue you're describing), the affected population is probably really small.
Then you also have to consider that most of Tinder's paying users are heterosexual men, and they know that they can screw those men over without losing their business because Tinder is an irreplaceable marketplace to find women.
With all those assumptions, Tinder isn't being as stupid as they sound, but rather coldly rational.
- johannes1234321 6y agoThe question is what the cost of that fix would be. Once the ticket reaches the developer it's probably quickly done and pays for itself with a handful registrations. However getting from support to a developer is the complex part. (Support has to understand the issue and then it has to be routed to the correct team ...)
- smt88 6y agoI completely understand why you see this as a 30-min fix, and therefore they should just knock it out. That's not how they would likely see it. If their devs are 100% utilized (which I'm sure they are), then fixing any issue -- even a 30-min one -- is going to mean that a different issue is delayed. The question becomes this: at what point is fixing this issue more valuable to the company than any other issue the same dev could work on? And the answer is possibly "never", depending on what high-impact bugs, features, or technical debt they have on their priority list.
- varjag 6y agoYou rationalize dysfunction into a strategy. It's not like they are doing Moon landing there 24/7. It's a simple bug with direct impact on the revenue. They should take a half hour break and fix it.
- korla 6y agoI think you vastly oversimplify how easy this fix is likely to be. For all we know this may mean touching code in multiple repos, each with hard-coded lists of which cards are supported for some case or another. At least that is what it would mean to change something like this where I am now.
- varjag 6y agoOh wow, editing a hard coded list. Does one need a chisel for that?
- jedberg 6y agoThat is not how things work in the real world. Sure, the fix itself might take 30 minutes. But then you have to validate it. And run a canary. And crosscheck your revenue numbers to make sure it didn't have an adverse affect elsewhere. That's a lot of work for something that will probably mean very little extra revenue.
- varjag 6y agoI assume they already have the quality assurance pipeline in place at Tinder and don't need to reinvent it from scratch for every bug report.
- IggleSniggle 6y ago
- marta_morena_28 6y agoFixing an issue around being unable to pay with a credit card is likely anything but a 30 min issue, unless there is some triviality happening, like a config issue. But even then you need to add tests for this. A day or two is the absolute minimum and that would be if this is just a config issue. If it's not, then think of weeks.
- Symbiote 6y agoIt should be fairly trivial. From the issue as described, the value "visa" worked, but "visadankort" didn't. Denmark's earlier, national debit card system is called DanKort. Nowadays, almost all DanKort cards are issued through Visa, so they are "Visa DanKort" -- within Denmark, there's the option to bypass some sort of fee for a lower cost of processing. Presumably the value "visadankort" is there to distinguish these cards. However, they can be processed exactly as normal Visa cards. This is not unique to Denmark, there are a list of card prefixes like this (see 4571 for DanKort[1]), but perhaps the different processing fees in unusual. [1] https://www.stevemorse.org/ssn/List_of_Bank_Identification_Numbers.html https://www.stevemorse.org/ssn/List_of_Bank_Identification_N...
- mgkimsal 6y ago"features" is the wildcard there. People who have already demonstrated they're trying to give you money is a relatively known payoff when that bug is fixed. "New features" that may never see the light of day, or may actually have a negative revenue impact... those are somehow sexier and often manage to take priority over mundane issues like... hundreds of peoples' payments failing over a month.
- arcticbull 6y ago> That's not how they would likely see it. If their devs are 100% utilized (which I'm sure they are), then fixing any issue -- even a 30-min one -- is going to mean that a different issue is delayed. This has not been my experience. If you work at a company where it's possible, I strongly suggest shadowing a supporter for a day. You'll leave with a 5 page long rage-list of issues that weren't adequately captured (and would take you a few minutes to knock out) and a new relationship established that will help unblock that bottleneck of information flow. IME, this is in part because supporters aren't as familiar with the technical aspects and don't know how to frame the issues they encounter in a way that would get traction with either PMs or engineers. As such are not well prioritized relative to issues that are fleshed out technically. I've worked at a company where supporters were spending huge amounts of time resolving issues that I knocked out in 5 minutes after shadowing and materially improved their operational efficiency. In a word, what's missing is a culture of ownership.
- smt88 6y agoI think you mean "customer support" when you say "supporter". If not, please disregard. Tinder doesn't offer much customer support. They're definitely not spending a substantial amount of time on issues that affect the subset of users that use Danish cards, don't pay through the app, and have one of the cards that has this issue. If you told me the number of affected people was under 5,000, I would believe you.
- arcticbull 6y agoYep, the place I used to work referred to "customer support" as "supporters." I assumed the term was used more broadly than it appears to be, my bad. I'm curious who handles those emails. I'm putting myself in the position of a software engineer at Tinder, I personally would have gotten care-mad enough to fix it. I go out of my way to get to know customer support folks where I work so I can get better insight into how people are actually using the product and where the pain points lie.
- Tomminn 6y agoThis is absurd. The return on investment for a bug like this must be extraordinarily high. The OP can fix it themselves by changing a string in the developer console. A permanent new revenue stream from an entire country for the price of 1/16 of one employee's workday. What kind of fires are burning at Tinder for that to not be a no brainer? Side note: if there are any devs here from Tinder, I recommend you go fix this on your own initiative and get yourself some quantifiable money made for your employer for your next performance review.
- smt88 6y ago1. It's not an entire country. It's people who use a Danish card and can't/won't subscribe through the Play Store. That's probably a tiny number of people. 2. Fires are almost always burning when you're supporting an app with millions of users expecting instant functionality, including instant messaging. They're also constantly working against bots and spammers.
- raverbashing 6y agoIt's not "coldly rational" if your fix is simple enough that can be fixed on the browser console and charging CCs directly avoid the 30% fee of the store (though Tinder does seem to tack that to the app store price)
- reaperducer 6y agolower on their list of revenue-impacting issues Some companies do what's right. Some only prioritize based on revenue maximization. Locking out an entire country is clearly wrong. Only prioritizing for revenue maximization is only ambiguously right. It's not like fixing a bug is going to bankrupt Tinder.
- smt88 6y ago1. This isn't locking out an entire country. 2. Tinder is constantly at war with bots and scammers. You have no way to know that fixing a CC issue for a tiny fraction of users is more ethical than their other bugs.
- specialist 6y agoThat's like using poor ROI to argue against curb cuts. There are intangible, non-quantifiable benefits to doing things better. Our inability to concoct a price is not a defensible reason to let entropy and chaos win. Sometimes Freedom Markets™ just need some TLC.
- xmprt 6y agoCompanies spend thousands on things that have dubious impact on the bottom line. This is something that has a direct and measurable impact. If the solution for the parent commenter was as simple as changing something in developer console, then the change for tinder shouldn't take more than a few days or a week.
- anonunivgrad 6y agoThis kind of hyper-optimization misses the forest for the trees. You need to have some love for your product and if you do, you do not let issues like this fester. Your bean counters can’t capture the full complexity of the world. They can’t capture the general sense of “shittiness” that users feel when your product fails in stupid ways and you don’t fix it. They can’t appreciate how that feeling snowballs into the success of a competitor five or ten years down the line.
- fsociety 6y agoI dunno it’s more about the principle of not fixing the product. I think software teams would benefit greatly by setting principles that they follow instead of justifying everything by revenue. Not saying you support the revenue-only model btw :)