Truly Madly: Review

So the wife and I both decided to sign up on the dating app TrulyMadly, she to conduct research for her matchmaking service, and me as part of my research for the book that I’m currently revising. Based on our collective usage of our respective apps for about an hour, here are some pertinent observations.

  • Sexism: The wife can see salaries of men she is getting matched with, while I don’t get to see salaries of women being recommended to me. Moreover, women are allowed to “lurk” (and not have a public profile) on the platform, but no such thing for men. I’m surprised no one has called out TrulyMadly on their sexism
  • Job board: To list on the app you need to indicate your profession and job, and how much you are making. So if you are a woman on this site, apart from getting to check out men, you get to check out what jobs pay how much, and it’s not inconceivable that you use the app to find yourself a job.
  • Judgments: This should possibly go down under sexism again. Anyway, the wife has mentioned her qualifications as “MBA”, and she is only being shown men who are graduates of top B-schools in India. No such thing for me – women shown to me had all kinds of qualifications. It’s like TrulyMadly has decided that women should only date men who are at least as well qualified as them. Moreover, the app also decides that men can only date women who are shorter than them, though there’s a setting somewhere to change this.
  • Age bar: Based on my age (which I entered as 34), the app decided that I should only be allowed to check out women between the ages of 26 and 34. These can be moved around, in case I have fetishes outside this age range, but I’m shocked that they are not aware of the N/2+7 rule – based on which the lower limit should’ve been set at 24 (34/2+7) and not 26.
  • Gender imbalance: The app gave up on me after I rejected some half a dozen women, after which I deactivated my account and deleted the app. The wife’s app, however, continues to go strong, as she might have rejected some two or three dozen men by now (apart from having done research on what jobs pay how much). Just goes to show the gender imbalance on the app. I can imagine this leading to a lot of frustrated people, of both genders.

Ok that’s it for now. Any more insights you can read in my book (I hope to get it out in the next month or two)!

Moral of the story: Product management pays better than category leader.

To app or not to app

The difference between using an app and a website is in terms of the costs. The app reduces the per-transaction cost, thanks to customisations and additional user information it possesses. There is a fixed cost in using the app, though, in terms of time, memory and bandwidth incurred in installing it, and user data that the app collects.

The costs of using an app versus using a website, as a function of the number of transactions, is illustrated in the figure here (this is simplified but not far from the truth):

app webThis is the graph you need to keep in mind when you are trying to take your product app-only or web-only. Labels from the graph have been removed on purpose.

For low levels of usage, there is no point in installing an app (unless the reduction in marginal cost is dramatic), for the fixed cost is not going to justify the benefit that the app offers. When the usage is high, it makes sense for the user to install the app, since the fixed cost will amortise over the larger number of transactions.

When a service goes app-only (as is the fashion in India nowadays), it loses the long tail of low volume users who see no value in incurring the fixed cost of keeping the app. On the other hand, a web-only service is likely to lose power users since they have to incur the higher marginal cost each time.

So if you are starting a new service and are wondering whether to launch the service on app first or web first, think of the frequency with which your customers will be using the service, and the incremental value you can add if they use the app (be realistic about these estimates). If it is either a high-frequency service (like email or news, for example) or a service where the value added through the app is massive (like Uber, which can read the user’s location), you better lead with an app.

On the other hand, if the service is low-frequency and the quality of experience in app and web need not be dramatically different, it makes sense to lead with the web offering and add an app later only to hold on to your power users.

From this perspective, I’m not convinced of the logic of Indian companies such as Flipkart and Myntra (which are shopping sites, which most users don’t use that often) to go app only. India being a ‘mobile-first’ nation is at best an excuse.


The above graph also explains why businesses offer attractive incentives to customers to install the app – to mitigate the high fixed cost of installation. The problem is that the fixed cost is borne not just during installation but also over time (app occupying phone space, snooping on you and sending you notifications), so smart users take advantage of these incentives and uninstall the apps after immediate use.