I watched Kipp Bodnar and Kieran Flanagan make a simple claim that hit me hard: the next great phone may not be a phone at all. They argued that if an assistant can do the work, we don’t need tiles of apps or even a big screen. I agree—and I’ll go further. The screen-first smartphone is an idea past its peak. The next wave will be small, voice-first, and task-native. That shift will change how we build products, how we market them, and how we live with them.
AI Will Shrink The Phone
The point was plain: if chat can do the job, the UI can shrink. That means fewer taps and less hunting through icons. It means a device that is more helpful and less needy. As Kipp and Kieran framed it, you should be able to ask and get it done.
“You don’t need apps… you just need to ask the chat or the AI to do something for you.”
That flips the hardware question. If a pocket assistant handles tasks by voice or short prompts, the slab of glass is overbuilt. A tiny device on your desk, in your pocket, or clipped to your jacket is enough. As they teased out, it could be “something smaller… completely different shape.”
Function beats display. The iPhone set the template. An AI-first device will break it.
Why A Chat-First Device Wins
I’ve built tools and content on the web for decades. I’ve seen interfaces get in the way of outcomes. A chat-first device removes that drag. It focuses on intent, not clicks. That is a better path for speed and output.
- Tasks move from “find the app” to “say the goal.”
- Multistep flows become single requests.
- Context carries over, so the assistant learns your style.
- Hardware gets lighter, cheaper, and more durable.
This is not just nice for users. It also changes how brands reach people. If the assistant is the gatekeeper, then the best answer wins. Not the flashiest ad. Utility beats aesthetics. That should scare lazy marketers and energize builders.
The Real Friction Isn’t Tech—It’s Habit
There are fair doubts. People like screens. We scroll to pass time. We enjoy visuals. True. But the core jobs of a phone are still calls, messages, notes, navigation, and quick tasks. For that bundle, chat wins. Voice wins. Small wins.
We moved from keyboards to touch when the benefit was clear. We’ll move from touch to ask when the result is faster and more personal. This shift will start with focused use cases and grow from there. Think travel, scheduling, support, and content creation on the go.
“You don’t necessarily need the same sort of visual aesthetics to actually interact with all of this data.”
I don’t need a glossy interface to book a table. I need it done right, fast, and confirmed. That’s the job.
My Playbook For Builders And Marketers
I see three moves that matter now. You do not need to wait for new hardware to begin.
Design for intent. Map your product’s top jobs. Reduce them to plain language requests. Build API hooks that turn “book a demo at 2 pm” into action with one call.
Optimize for the assistant layer. Your brand must be the best answer the assistant can give. That means structured data, clear offers, fast fulfillment, and strong follow-up. If your flow breaks, you lose by default.
Shift from interface to outcome. Measure by result, not clicks. Time saved. Tasks done. Errors reduced. Those are the metrics that will win the new gatekeeper.
What This Means For Daily Life
Less phone time and more done. That’s the promise. A smaller device that listens, acts, and updates you—without the feed sucking you in. For creators and entrepreneurs, it means faster research, instant briefs, and cleaner handoffs. For teams, it means fewer tools, tighter loops, and better focus.
There will still be screens for deep work and media. But your “phone” can stop being the center of your day. That’s healthy—for attention, for privacy, and for results.
The Call: Start Building For Ask, Not Tap
The message from Marketing Against the Grain was blunt and right. The app grid is a habit, not a law. The future device can be “something smaller… more elegant.” I’m ready for that shift. You should be, too.
Here’s what to do this week: write the top 10 user requests your product should handle in plain English. Wire them into your stack. Test them with real users. Cut two steps for every flow. Then market the outcome, not the UI.
The next great phone won’t ask for your attention—it will give you back your time. Build for that, and you won’t just keep up. You’ll lead.
