How to compare two phones without drowning in specs
A side-by-side table makes two phones look like a list of numbers to be totalled up. Four questions settle almost every comparison, and none of them appears in the table.
Put two phones beside each other and you get two columns of numbers, which invites you to count how many lines each one wins. That method produces the wrong answer regularly, because the lines are not worth the same and several of them do not predict anything you will experience. A phone with a higher number in nine rows can be the worse phone to own. What settles a comparison is a much shorter list: how each one behaves when the light goes, how long it lasts on the day you use it hardest, how long it will be supported, and how it feels in one hand. Here is how to get at those.
Start with the two or three things you will do most
Before opening any comparison, write down what you actually do with a phone, in order of how often. Photographs of people indoors. Two hours of video on a commute. Navigation on a bike. A work account and a personal one. That list is short and it is personal, and it converts a table of forty rows into four rows that matter. Most comparison fatigue comes from treating every specification as relevant; almost none of it is relevant to any one person. The phone that wins your four rows is your phone, whatever it does in the other thirty-six.
- Write the list before you look at any phone, so the table cannot shape it.
- Three or four items is the right length. Ten means you have written a specification sheet again.
Judge cameras by pictures in the light you shoot in
Camera rows in a table are the least predictive part of it. The sensor count, the megapixel figure and the lens list do not tell you how a photograph will look, because the result is assembled from several frames by software that makes choices about colour, shadow and sharpening. Two phones with the same sensor produce visibly different pictures for this reason. The only reliable method is to look at full-size photographs taken on each phone in the conditions you shoot in — a lit room in the evening, not a garden at noon — and to pick the one whose choices you prefer.
Battery: ask about your hardest day, not the capacity
Capacity is a tank size and tells you little by itself, because what empties it is the screen, the radios and the processor, and those differ. The figure worth finding is screen-on time under the kind of use you actually have, which reviews report and specification tables never do. Then take the harder question: what does a bad day look like — navigation, hotspot, camera, a weak signal — because that is the day you will remember. A phone that handles your worst day is worth more than one that handles your average day slightly better.
- Screen-on time under real use predicts your day; capacity does not.
- A weak signal is one of the largest drains there is, and never appears in any table.
Support length is the row that decides year three
How long a phone will receive updates, and security updates in particular, is a published commitment and the single most consequential row in any comparison, because it decides whether the phone is sensible to keep. Two phones that look identical today can be two and five years from their last update, and that gap is worth more than every camera difference combined. It is also the row most often left out of comparison tables, which is reason enough to go and look it up on each maker's own page before deciding.
Hold both, because size is not a number
The dimensions in a table do not tell you whether you can reach the far corner of the screen with your thumb, whether the weight tips forward in your hand, or whether the shape digs in. These are the things that decide whether a phone is pleasant two years later, and five minutes holding both settles them more reliably than any amount of reading. If you cannot hold them, the next best thing is to compare their weight and width against the phone you already have and know, rather than against each other in the abstract.
What to try, in order
- Write down the three or four things you do most with a phone, before you look at either one.
- Find full-size photographs from both, taken in the light you actually shoot in.
- Look up screen-on time from a review rather than battery capacity from a table.
- Check each maker's published update commitment, in years, on their own page.
- Hold both if you can, or compare their weight and width against the phone you own now.
- Ignore every row in the table that does not appear on your own short list.
What to take from this
A comparison table invites you to add up wins, and the rows are not worth the same. Four questions settle it: which one handles the two or three things you do most, which takes pictures you prefer in the light you shoot in, which survives your hardest day, and which will still be getting updates in three years. Hold both if you can. Everything else in the table is detail you are unlikely ever to notice.
Common questions
Does a faster processor make a phone feel faster?
Up to a point, and then it stops mattering. Beyond a certain level the thing you notice is memory, storage speed and how much background work the software does, not the peak speed of the chip. A phone that feels slow after a year is usually short of memory or storage, not of processing.
Is a higher refresh rate screen worth it on a phone?
It is one of the few table rows you genuinely feel, because scrolling and animation are most of what you look at. It also costs battery. Most phones let you cap it, so the honest answer is that it is worth having and worth turning down on a long day.
How much does software support really matter?
It decides whether year three is comfortable or anxious. A phone without security updates still works, and it stops being a sensible place for banking and work accounts. Of all the rows in a comparison, this is the one that changes what the phone is for.
