Escape the attention economy. Reclaim your focus.

The Leaf That Wilts: Why We Can't Stop Checking Our Phones

Why does scrolling feel empty afterwards? A story told by a user, a partner, and the data analyst who designed the loop that keeps them coming back.

compulsive phone checkingvariable ratio reinforcementgamification habit loopnotification off

Editorial Note: This is a work of fiction. The characters, app, and workplace scenarios are invented to explore how engagement mechanics can shape attention and relationships. The story draws on research into behavioral reinforcement and digital habits, but its events and outcomes are fictional.

A story about attention, streaks, and the space between two people


1. Why the First Thing She Does Every Morning Is Check Her Phone

Wren's hand woke up before her eyes did.

She hadn't focused on the water stain on the ceiling yet when her fingertips found the warm glass on the nightstand. Unlock. Fingerprint, first try. The screen pushed a small rectangle of light into the dark and lit half her face.

The first thing there was the feed. She pulled down.

A college classmate posted brunch, plated carefully, half an avocado on the rim. A former coworker announced a promotion in three paragraphs and finished by thanking the team. Her cousin's dog had been neutered and wore a cone like it had been personally betrayed by the world. Someone was selling a used camera. Someone reposted a joke she didn't get.

She read all of it. None of it involved her. None of it asked her to do anything.

When she finished, something hollowed out in her chest. Like swallowing a mouthful of cold air.

So she pulled down again.

Wren was thirty-one, a freelance illustrator taking commercial work from home. She hadn't been in a conversation with more than three people at once in four months. Her calendar held delivery dates and tracking numbers. The only place her name still appeared inside other people's lives was this screen.

She knew she wasn't looking for information. She was confirming something: nobody had removed her from anyone's list, nobody was quietly angry at her, her seat was still warm. The check took about forty seconds, cost her nothing, and paid out in a light kind of relief — the feeling of patting your pocket for your keys before you leave the house.

On the second pass she found a classmate she hadn't spoken to in three years, posting cardboard boxes from a move. Wren tapped the heart.

The elegance of the heart was that it required no words. She didn't have to explain where the last three years had gone, or answer how have you been, or carry the weight of a conversation. The line stayed warm. Low heat, but warm. Three seconds later she could go back to doing nothing at all.

She set the phone face-down and rolled over. In the kitchen, the kettle began its low rumble. She heard it. She stayed put.

The notification traveled across the city, landed on somebody's phone, lit up, and went dark.

2. The Morning Standup Where the Retention Curve Got Explained

Renata's meeting ran out of a conference room in another city. She sat in a rented spare bedroom in Memphis with a white-painted brick wall behind her. Mic on, camera off.

Two curves were on the screen share.

"Day-two retention went up 1.8 points last week," she said. "Most of it came from paired Grove users."

Marcus, the product lead, said two of the new engineers had never touched that module and asked her to walk the room through how it worked.

Renata brought up a diagram.

"Grove is a progression loop sitting inside the feed," she said, in the flat tone of someone reading a spec. "Every day a person uses the app — walks, pays for something, watches content — they generate a resource called Sap. When Sap accumulates, a tree grows in their plot. When the tree finishes, the system actually plants a real tree in a partner forest, and the user gets coordinates."

"Three things matter," she said, and held up three fingers.

"One: Sap expires. It used to be ninety-six hours. Last week we cut it to seventy-two. If you don't come back and collect, it's gone."

"Two: streaks. Longer streaks pay better. Break it and the count restarts."

"Three: pairing. The system puts two users together to grow one shared grove. You can water their side. You can also take a portion of their Sap before they collect it. They can do the same back. Rare seeds drop at random, and whoever's lucky gets them."

She paused.

"Stack those three and you get: the user has to come back once a day or lose something; once they're back there's a random reward, so they want to look one more time; and pairing puts another person in the loop, so showing up stops being only about themselves."

Somebody asked whether that was just social.

"It's social," Renata said. "But it's social we engineered. We aren't serving a need that already existed. We created an obligation that has to be handled daily, and the need is a byproduct of the obligation."

Two seconds of quiet, then someone laughed and said that sounded like a villain's line. Renata didn't laugh. She closed the slide and went back to the curves.

Then she covered the other half: variable-ratio reinforcement. Rewards arrive after an unpredictable number of actions, so a person may keep checking because the next attempt could bring a rare seed — or nothing at all. The principle resembled the reinforcement schedule used in slot machines, though the app's social and digital rewards were not identical to gambling rewards. She also discussed the triggers. Sometimes it wasn't the content that brought people back, but boredom, waiting, or the dead minutes before sleep. Those moments could become cues in a habit loop, alongside notifications and the expectation of social feedback.

Marcus asked what was next. Renata pitched one thing: a nudge sent to pairs who hadn't interacted in a while, telling them their partner was waiting for water. She expected interaction volume to climb, because once a conversation starts, reciprocity carries it — you water me once, and it's hard not to water back.

The meeting ended. Coworkers dropped off one by one.

Renata didn't close her laptop right away. She opened her own account and looked at the home screen. Three hundred and something days on a streak. A green leaf icon in the middle of the screen, its edges already going yellow. Her Sap was about to expire.

She knew exactly which line of logic made that icon appear on schedule every day. She knew where the thresholds sat, where she fell in the distribution, and that she lived in the bucket labeled high-retention.

She tapped collect. The leaf went green again.

Then she shut the laptop and went to make coffee.

3. How Two Strangers Watering a Tree Every Day Start to Feel Close

When Malik came off the night shift, the Memphis air was wet, like a towel nobody had wrung out.

He stopped at a red light, took his right hand off the wheel, and reached for his phone. He hadn't decided to do that. His body had.

In Grove there was a small grove he and Delia had been growing together for the better part of a year. He watered, she watered, and both progress bars crept forward. The tree in the middle had a name they'd chosen together. It was a stupid name. Neither of them would change it.

Delia was a stranger the system had paired him with. He had never seen her face; her avatar was a blurry photo of a leaf. He'd heard three voice messages from her. He knew her sentences dropped at the end, and that she inhaled before she laughed. He knew it rained a lot where she was, because she always came online when it rained.

Their conversations had a private vocabulary. He called her the Tree Boss. She'd sent him a rare seed once; he'd repaid her with three waters, she'd answered with five, so he'd gone to seven. That exchange had run for two months. Neither of them kept score, and both of them remembered the numbers.

The light turned green. He put the phone away and drove on.

Malik was thirty-four and worked logistics dispatch, on shifts. His job was putting a hundred and some containers in the right place at the right time, and mistakes turned into phone calls. He got home when Wren was usually asleep, and left in the morning before she woke. The time they genuinely spent talking in a day often came in under twenty minutes.

The twenty minutes in Grove were whole. Uninterrupted. Somebody was waiting.

He pulled into the driveway, killed the engine, and sat in the dark without moving.

Then he opened the chat box and typed a line. It wasn't in the game. It was a direct message.

Hot today. How's it over there?

He had time to think before he sent it. He didn't.

4. Three Hundred Acquaintances and the One Person Who Stopped Asking

A few weeks later, Wren started noticing small things.

Malik set his phone face-down on the table when he came in. Before, he tossed it anywhere, screen up. He carried it into the shower now; he hadn't before. When he smiled at the screen, he didn't turn it around to show her the way he used to.

Once, while she was inking a sketch on the couch, she looked up and saw his profile lit from below, and a small expression on his mouth that did not belong in that room.

She didn't ask. What she thought instead was this: she had three hundred-plus feeds to scroll, three seconds each, zero cost, and none of those relationships would lapse. And she hadn't asked Malik how the shipment went, or whether the night shift had handed him three more complaint calls, in a long time.

Keeping three hundred weak ties was far cheaper than keeping one intimate one. A weak tie cost a tap. An intimate one cost her lifting her head, opening her mouth, and accepting that he might not want to answer.

She put the pen down. Picked it up.

That night she walked past the kitchen and his phone lit on the counter. She caught a green leaf icon, edges yellowing, with a small countdown ticking beside it.

She pretended not to see it and went to get water.

From that night on, she paid attention. Paying attention cost nothing. It was just moving the same attention from one screen to another.

5. What the Numbers Looked Like After the Nudge Went Live

In the first week after the nudge shipped, the numbers moved fast.

Renata sat with the dashboard for a long time. Pair interaction volume was up forty percent, and the share of late-night sessions had climbed with it. The timing was consistent with the nudge increasing engagement, though the dashboard alone couldn't establish how much of the change it had caused. She wrote it up with three charts and sent it to Marcus. He replied nice and a flame emoji.

She should have been pleased. For a few minutes she was.

Then she started looking at shape instead of totals.

Most pairs grew in a flat, symmetrical way, like two people taking turns with a watering can. A small cluster didn't. Their curves were steep, their sessions slid later, concentrated after midnight, and when one side went quiet the other side's visits got dense immediately. The pattern didn't prove what anyone was feeling, but it suggested that something beyond tending a tree might be keeping them engaged. It looked less like maintaining a game than waiting for a person.

She couldn't see the contents of in-app messages. That permission wasn't hers. Behavior she could see. She sliced the data by region.

The Memphis row came up, well above the city average.

She looked at it for maybe ten seconds, then closed it and went back to the overview.

She knew what her job was. Take millions of lives, cut them into aggregate curves, read the patterns, turn the patterns into the next feature. She read patterns, not people. That distinction was real, and it was something she had to reconfirm for herself most days.

At the bottom of the doc she added one line: Late-night conversation share rising. Recommend monitoring.

Marcus said it was out of scope for this release. She left the line in. She didn't delete it.

6. "We're Just Growing a Tree" — Emotional Affairs and Micro-Cheating Online

Once the direct messages became a daily thing, Malik found himself a very stable explanation: they were just growing a tree.

The explanation had receipts. Their grove had a co-planted certificate, a shared anniversary, an area that only the two of them could unlock. All of it was real, issued by the system, verifiable. So we're just growing a tree didn't sound like an excuse. It sounded like a fact.

That was how his guard came down.

In the real world, Wren asked him about bills, about whether to call someone about the roof leak, about whether he could take two fewer night shifts this month. Every one of those questions was reasonable, every one carried weight, and every one required an answer.

Delia asked nothing. She said it was raining again where she was. She said she was tired today. She asked how he was. He told her, and she listened. Nobody had ever let him finish a whole complaint like that without asking him to do something about it.

The comparison happened inside him on its own. Nobody made it for him. He simply arrived, slowly, at the conclusion that this person understood him better.

One morning he found that part of a day's Sap had been taken. The system said Delia had done it, while he was asleep. By the rules of the game he should have been annoyed — that was a full day of accumulation. He stared at the notification for a few seconds and felt something close to amusement, and something close to being noticed: somebody had touched his things while he wasn't there.

He repaid her with three waters. She answered with five. He went to seven.

That was how the investment stacked up. Water counts, an anniversary, a shared name, a private vocabulary, resources taken and given back. Each piece was small. Added together, he found it hard to say the thing didn't matter — because saying so would mean the last nine months had been for nothing.

Then Delia sent a message:

How long have you been with her?

Malik sat in the car and didn't answer right away. He typed a few words and deleted them. Typed another line and deleted that too.

In the end he told the truth. Four years.

Something changed after he sent it. He couldn't name what. He only knew that from then on, every time he opened the app, he stopped for half a second first.

7. The Same Night, Three Screens

One night, three rooms, three screens.

Wren was awake. She lay in bed with the phone held up in front of her face, the screen throwing a pale square onto the ceiling. Malik was in the living room with his back to her, sitting very straight. She watched the light from his phone move along his jaw. She watched a message preview slide in and get swiped away. She watched him not put the phone down after swiping it away.

She didn't get up. She didn't say anything. She pressed her screen off and the room went black again. In the dark she could hear her own breathing, slower than usual.

In another city, Renata was working late. The dashboard was still open. She'd been about to shut down when her eye caught the row she'd closed the week before — the Memphis cluster had doubled again, and most of it sat after midnight.

She put her hand on the mouse and didn't click.

She knew exactly what she could do: turn the pattern into a feature, hand it to the next experiment, make it bigger, sharper, easier to reproduce. She also knew exactly what she couldn't do: she wasn't in that room. She didn't even know which room it was.

In the end she did nothing and closed the laptop.

In the living room, Malik's phone buzzed.

Your partner hasn't watered in 24 hours.

That was the system's deadline. At seventy-two hours the resource would rot. He read the line and understood something he had never once considered: the deadline wasn't a law of nature. Somebody had set it in a conference room, so that he would sit here at this hour, looking at a yellow icon.

Three screens. Three hands rising.

Wren's hand rose and pressed her screen off.

Renata's hand rose and closed the laptop.

Malik's hand rose and stopped above the glass, and did not come down.

8. Three Small Changes — Digital Minimalism, Turning Off Notifications, and Breaking the Streak

The next morning Wren did something very small.

She turned off the feed's notification badge. Not an uninstall, not a detox — just the number that kept calling her back. Then she gave herself two windows: one in the morning, one at night. Nothing in between.

The first two days were rough. Her hand went to the nightstand on its own, found the glass, and stopped. The hollow feeling came back, sharper than usual, because this time she didn't fill it immediately. She let it stay empty for a while.

On the third day she didn't scroll. She messaged a friend she hadn't spoken to in five years and asked how she was. The reply came two hours later and ran long. Wren read it and sat in her chair for a while without moving. That stretch of time was longer than a hundred feed items put together.

That same week Malik did something smaller.

He put his phone on the kitchen table, screen up, opened Grove, and slid it across to Wren.

"This is a tree I've been growing with someone," he said. "I don't know what it counts as."

Wren looked at the grove for a long time. She didn't cry and she didn't raise her voice. She asked one question: what had they talked about. He told her. Halfway through he stopped and said he didn't know which step it had turned at.

That night his streak broke. The next morning the system sent a reminder asking if he wanted to buy his way back.

He didn't.

That week Renata added a line to the experiment doc:

Pair interaction volume rose after the nudge shipped, alongside an increase in late-night conversation share and revisit density when one side goes quiet. Recommend testing whether these changes are attributable to the nudge, adding a boundary prompt and a one-tap exit path in the next release, and monitoring high-frequency late-night pairs separately.

Marcus replied: not for this release, revisit next quarter.

The line stayed in the document. It stayed in the version history, where anyone who opened the file could see it. Renata knew it wasn't a win and barely counted as progress. But it was there, and that was a fact.

She took one last look at the dashboard.

The curve was still climbing.

At the far right edge of it, a small cluster of users had stopped. They turned off badges, or let streaks lapse, or slid a conversation onto a table between two people. Their departure was invisible in the aggregate — a wobble small enough to be smoothed away as noise.

Renata screenshotted that little segment and saved it in a folder only she knew about.

Outside, the Memphis sky began to lighten. A barge moved slowly down the river, and the sound carried a long way.


Continue Exploring


References

  1. Maza, M. T., et al., 2023 Association of Habitual Checking Behaviors on Social Media With Longitudinal Functional Brain Development https://doi.org/10.1001/jamapediatrics.2022.4924

  2. Meier, A., 2022 Studying problems, not problematic usage: Do mobile checking habits increase procrastination and decrease well-being? https://doi.org/10.1177/20501579211029326

  3. McDaniel, B. T., Drouin, M., & Cravens, J. D., 2017 Do You Have Anything to Hide? Infidelity-Related Behaviors on Social Media Sites and Marital Satisfaction https://doi.org/10.1016/j.chb.2016.09.031

  4. Rus, H. M., & Tiemensma, J., 2017 “It's complicated.” A systematic review of associations between social network site use and romantic relationships https://doi.org/10.1016/j.chb.2017.06.004

This story was published in Unplugr Stories.

← Back to Stories