Music, ride, food, lights: the everyday tasks the agent owns

The four most-opened apps in the average phone (after the messages app and the browser) are some combination of Spotify, Uber, DoorDash, and a smart-home app. Together they cover music, mobility, food, and home environment: the four most frequent everyday transactions in a connected adult's life. Each one of those four is a perfectly fine app. The friction is not the app; it is the cumulative cost of switching between four apps to do four small tasks.

This post is what changes when those four small tasks move into the messages thread. The apps stay installed; you just stop opening them.

Music

Spotify is the deepest of the four integrations. Full control: play, pause, skip, queue, transfer between devices, search, create playlists, add to library.

A representative sequence:

You: play that song i had on yesterday
 
Ajeris: Float On - Modest Mouse on the kitchen speaker.
        Last played at 9:42pm last night.
 
You: queue the rest of the album
 
Ajeris: Queued. 11 more tracks. ~38 min.
 
You: add this to my running playlist
 
Ajeris: Added to "Running 2026."

The agent's music memory is the unsung hero of this category. "Play that song I had on yesterday" is a query the Spotify app cannot answer; the agent can, because it has the play-history context.

Ride

Uber and Lyft, with one specific quirk: the actual ride booking happens via deep link rather than full API. The agent prepares the ride parameters (destination, pickup, ride type) and mints a deep link; you tap to confirm in the Uber app. This is by design: ride bookings should require an explicit user confirmation since they cost real money.

You: uber to the airport in 30
 
Ajeris: Pickup from home, ATL airport, leaving 6:42pm.
        UberX is $34. Tap to confirm: <link>
 
You: [taps]
 
[Uber app opens with ride pre-filled. User confirms.]
 
Ajeris: Ride confirmed. Driver assigned in 2 minutes.
        I'll send you a heads-up at the 5-minute mark.

The total interaction is 3 messages. The user did not open the Uber app from cold; the deep link landed them on the ride confirmation directly.

Food

DoorDash works the same way as Uber: deep link confirmation. The agent has tools for finding restaurants, saving "usuals," and re-ordering, but the final tap is yours.

You: order my usual chipotle
 
Ajeris: Reordering: Burrito bowl, chicken, brown rice, black
        beans, no salsa, guac, lime. Delivery to home, ~22 min.
        Tap to confirm: <link>
 
You: [taps and confirms]
 
Ajeris: Placed. ETA 8:14pm.

The "usual" is captured the first time you order something. The next time, you just say "my usual" or "reorder Chipotle"; the agent fills the cart.

Lights

Covered in the smart home post. The short version: Hue and LIFX integrations are deep, per-room scene control is one sentence, and the daily Hue-app open-rate falls to zero within a week.

What the four together feel like

The cumulative effect is what surprises users. After two weeks, the home screen of the phone looks the same; the apps are still all there. But the user does not open them anymore. They text the agent and the action happens. The phone is a launcher for one app: Messages.

For people who care about screen-time stats, this is visible: app-switching time drops by 50-80% for the everyday cluster. For people who do not care about stats, the felt experience is "the phone is calmer."

What does not work yet

Two honest gaps.

Specific-restaurant menus inside DoorDash. The agent can search and reorder, but ordering a totally new item from a restaurant the user has never tried is sometimes shaky (the menu API is inconsistent across restaurants). Reorders work. New orders mostly work. The edge cases get escalated.

Multi-stop ride bookings. Uber's API supports them; the agent's tooling is shallower. For now, multi-stop trips are best confirmed in the Uber app directly.

What it changes about your routines

Three small shifts that compound.

The morning soundtrack starts before you reach the kitchen. "Play the morning playlist on the kitchen speaker." Said while still in bed. By the time the user is in the kitchen, the music is on. The Spotify app was not opened; the speaker connection was already there.

The Uber happens during a conversation, not before. "I'll need a ride at 6:42 to the airport." Said while in another text thread, in passing. The agent prepares it; the user confirms with a tap when ready. The mental load of "oh I need to book the Uber, let me switch apps" is gone.

The food order is a 5-second ask, not a 5-minute browse. "My usual Chipotle" is the entire interaction. The 5-minute browse-and-decide cycle that used to be Saturday-night dinner is replaced by reorder muscle memory.

Try it

Start with the easiest one: music. Tell the agent to play something. Watch how often you reach for the Spotify app over the next week.