The plate that used to sit on the table: food apps, gig work, and the quiet renegotiation of the urban Indian family meal

On 11 July 2026, Scroll.in published a long, quiet piece of reporting from some of India's busiest metropolitan kitchens — not the kind with industrial stoves, but the kind where a woman has, for thirty years, decided what the household eats on a Wednesday. Reporter Aarefa Johari's investigation, "Eating out-eating in: How food apps have changed family bonds in urban India," argues that the platform economy has not simply changed where Indians order dinner. It has reorganised the negotiation inside the home: who is permitted to be tired, whose labour counts as labour, and which family members get a vote at mealtime.

The thesis is unfashionable for a tech-press used to celebrating the sheer throughput of Indian food delivery. Scroll's reporting suggests that the apps have not merely added an option to the urban Indian kitchen. They have shifted the burden of an old social compact — that someone, usually a woman, would cook — and replaced it with a transaction that the rest of the household can treat as frictionless. The convenience is real. The trade is also real, and rarely named.

Where the kitchen used to be

The piece roots the change in a familiar Indian domestic pattern. Scroll's interviews with women in Mumbai, Bengaluru and Delhi describe a pre-app household in which the woman of the house — mother, wife, daughter-in-law — held the de facto veto over what was eaten. Cooking, even for a working woman, was treated as non-negotiable. Ordering in was an occasional event, almost always outside the home, almost always a treat rather than a substitute.

What the platforms introduced, in this reading, was permission. Permission, in the first instance, for the woman herself to opt out of cooking on a weekday. Permission, in the second, for the rest of the family to treat that opt-out as a normal outcome of a hard day rather than a failure of duty. The piece quotes younger women describing a low-grade guilt that has migrated — out of the kitchen and into the wallet, where it is at least easier to price.

This is not an unambiguous loss. Several of Scroll's interviewees describe the change as liberation. A working mother in Bengaluru tells the outlet that the apps have given her back an evening she used to spend chopping onions. A retired father in Mumbai says he now eats dinner at a time that suits his digestion rather than his daughter-in-law's shift schedule. Those voices are real, and the piece takes them seriously.

Where the platform sits

The structural frame, rendered in the piece without academic scaffolding, is familiar to anyone who has watched consumer internet businesses over the last decade. Platforms route a vast number of small transactions through a thin layer of software; the marginal cost of the next order collapses toward zero; the platform captures the data, the diner captures the convenience, and somewhere downstream a kitchen — often a cloud kitchen, sometimes a women's co-operative, sometimes a single cook with a tiffin — absorbs the volatility.

What Scroll adds to that familiar story is the demand side. The Indian food-delivery market has matured past the subsidy war. The platforms no longer need to lose money on every order to acquire the next user. They have already acquired her. The question is what they have trained her to do on a Tuesday.

The piece is careful to note that this is not a story unique to India. The same restructuring has played out, with local variations, in China, in Southeast Asia, in parts of Latin America. The Indian texture is specific: the joint family, the gendered expectation of who cooks, the particular weight that an urban middle-class household puts on a sit-down meal as a marker of order. The apps have not so much broken that marker as re-priced it.

The cost on the other side of the screen

Scroll also reports on the supply side, and the picture there is harsher. The piece profiles a cloud-kitchen operator in Mumbai who describes the unit economics of a single dish — the cut taken by the platform, the cut taken by the aggregator, the cut taken by the delivery partner, and what is left for the cook. The maths, as the piece sets it out, is tight. Margins compress further when a platform runs a discount. The operator absorbs it.

This is the part of the story that the consumer-facing apps are least keen to be photographed next to. The same transaction that looks like convenience from a household in Andheri looks like precarity from a kitchen in Kurla. Scroll does not romanticise either side. It simply insists that both sides exist in the same sentence, and that a serious reader should hold them together.

There is also a quieter labour story the piece touches: the women, often older, often migrants, who prepare the meals that other women's families then order on a weeknight. The piece does not chase this thread all the way down the rabbit hole — it is a feature, not an investigation — but it flags that the labour is gendered in both directions, and that the apps have done little to make either set of workers visible to the other.

What the family meal was for

The strongest section of Scroll's piece is the part that asks what, exactly, the family meal used to do that the food-app dinner does not. The answer it assembles — from interviews with sociologists, nutritionists, and ordinary households — is that the meal was a small daily institution. It was the place where a household quietly took stock of itself. Who was home. Who was tired. Who was angry. Who was missing. The piece argues, with appropriate caution, that when the meal becomes a transaction, the institution thins out. The information that used to surface over a shared dish now has to surface somewhere else, and often does not.

This is an arguable claim, and reasonable people will disagree with it. Plenty of households eat at home every night and never say a word to each other. Plenty of households order in and have their best conversations over a shared biryani. Scroll is not making a universal claim. It is reporting what its interviewees said.

Counterpoint: choice, dignity, time

The piece is honest about the counter-narrative, and it would be lazy of any summary to leave it out. Indian women have entered the workforce in record numbers over the last twenty years. The double shift — paid work and unpaid domestic labour — is well documented, and it is grinding. If a food app gives a working mother an extra hour with her children, or an extra hour of sleep, the case for the app does not require any nostalgia for the kitchen as a site of feminine virtue. The piece quotes women who are unsentimental about this. They are glad the option exists.

The structural critique, in other words, is not that the apps have given women choices. It is that the apps have given households a way to treat the labour of feeding a family as a problem to be outsourced rather than a task to be renegotiated. That is a real distinction, and it is the one the piece is trying to draw.

What the evidence does not settle

Scroll's reporting is descriptive rather than statistical. The piece does not claim to measure how many urban Indian households now order in on a weeknight, nor does it adjudicate whether the net effect on women's wellbeing is positive or negative. It offers portraits and quotations. The reader has to do some of the work.

What the piece does establish is that the renegotiation is already underway, that it is uneven across cities and income brackets, and that the platforms are not neutral parties to it. They have a stake in the transaction becoming routine, and they have the data to know when it has.

Scroll's piece arrives at a moment when Indian food-delivery platforms are no longer growth stories but mature businesses, and when their effect on the household is a question that the public-health literature, the labour literature, and the gender-and-development literature have only just started to take seriously. Monexus treats the piece as reportage, not as advocacy: the question it raises — what the family meal is for, and who pays when it becomes a transaction — does not have a clean answer, and this publication is not offering one.