For a stretch when we were building Qysh Me, the industry still treated mobile as an afterthought: design for desktop, then squeeze it onto a phone. Our numbers told a different story. A large and growing share of our readers arrived on a phone, often a modest one, often over a shaky connection. The phone was not the secondary experience. It was the experience.
So we designed for it first, and let the desktop version follow.
What designing phone-first forced us to do
Designing for a small screen and a slow connection is a constraint, and constraints make you honest. When you only have a narrow column and a reader in a hurry, you cannot hide behind clutter.
- Ruthless hierarchy. The answer to the question came first. Everything else moved down or out.
- Readable type. Comfortable text and generous spacing, so a how-to was easy to follow on a small screen.
- Tap-friendly everything. Buttons and links sized for thumbs, not mouse pointers.
- Light pages. Fewer heavy elements, because every extra kilobyte was a reader lost on a slow connection.
- Single-column simplicity. Layouts that reflowed cleanly instead of breaking.
The constraint improved the desktop version too
Here is what I did not expect. Stripping a page down to what a phone reader truly needed did not just help on mobile. It made the desktop experience clearer as well. Once we had decided what mattered most on a small screen, the larger layout became calmer and more focused by default.
What I recommend
Design for your hardest case, not your most comfortable one. If a meaningful share of your audience is on phones and slow connections, start there and let everything else inherit that discipline. On Qysh Me, phone-first was not a limitation we tolerated, it was the decision that made the product simpler and better for everyone, and it shaped how I approach design to this day.