A phone is a bundle of four separate purchases — the radio and its band support, the compute and memory, the battery and charging path, and the software support window — and almost every bad buying decision comes from overpaying for one and ignoring the other three. Get the band list right for your carrier, match RAM to how many apps you keep alive, accept that the battery is a consumable, and count the years of security updates before you count the cameras. Everything below is the reasoning behind those four, in the order the decisions actually cost you money.
Network support is the first filter, not the last
Check the exact model number against your carrier's band list before you look at anything else on the spec sheet, because a phone that lacks your carrier's primary bands is a phone that drops to a slower network indoors and in rural areas no matter how good the rest of it is. Manufacturers ship regional variants of the same name — the same phone sold in Europe and in the US can differ in which bands the modem tunes for — and the model number in the listing, not the marketing name, is what tells you which one you're buying. Imported and grey-market units are the usual trap: they work, they attach to the network, and then you notice that data crawls inside buildings while a cheaper domestic phone on the same plan is fine.
eSIM support is a separate question from band support and it's where the terminology matters. An eSIM is the generic term for devices and eUICCs that support Remote SIM Provisioning as defined by GSMA, allowing mobile operator profiles to be securely downloaded, stored and managed without a removable SIM card. Remote SIM Provisioning is the GSMA-defined process for downloading, installing, enabling, disabling and deleting a subscription profile over the air. The eUICC is the embedded chip itself — the GSMA architecture that lets a single embedded SIM securely store and manage multiple mobile network operator profiles.
The practical consequence: an eSIM can hold multiple operator profiles, so a traveler can keep a home line active alongside a local data plan without swapping plastic. The consumer specification you'll see referenced is GSMA SGP.22, the Remote SIM Provisioning architecture for consumer devices, currently at specification version v2.6.1; the M2M and IoT variants are SGP.02 and SGP.32 and are not what your phone uses. Where eSIM costs you: carrier support is uneven, moving a profile between phones sometimes means a call to support rather than a SIM tray swap, and if you break the phone you can't pull the SIM and drop it into a spare. If you change phones often or keep a backup handset, a physical tray plus eSIM as a second line is the flexible arrangement.
Compute and memory: buy for the apps you keep, not the benchmark
RAM determines how many apps survive in the background, and that number matters more day to day than peak processor speed. A phone with generous RAM holds a messaging app, a browser with several tabs, a maps session and a camera roll without reloading any of them when you switch back; a phone with too little reloads the browser tab you left and loses your place. Mid-range chips handle messaging, video and navigation perfectly well — the visible penalty of a cheaper chip shows up in camera processing time (the pause after you press the shutter), in games, and in how quickly the interface stays smooth over several years of software updates. Pay for the chip only if you actually use the thing that needs it.
Storage is the decision people regret. There is no expansion on most current designs, and the operating system plus preinstalled software occupies a meaningful slice of the advertised capacity before you've taken a photo. If you shoot video regularly, keep offline maps, or hold a large music library, buy one tier above what feels sufficient — the cost of the storage upgrade at purchase is almost always less than the cost of replacing the phone early. Cloud storage is not a full substitute: it needs connectivity at the moment you want the file, and video files are large enough that uploading them on a mobile plan is impractical.
The trade-off is real in the other direction. Paying for the top storage tier and the fastest chip on a phone you use for calls, messages and a banking app is money that would have been better spent on a longer software support window or a battery replacement later. Match the spend to the workload.
Batteries degrade on a schedule; plan the replacement, not the spec
Battery capacity in the spec sheet tells you less than the charging behavior and the replacement path. Every lithium battery loses capacity with charge cycles and with heat, and the two things that accelerate the loss are charging to full and holding there while warm, and discharging deeply and often. You'll notice it as a phone that used to reach evening with margin and now needs a top-up mid-afternoon — typically after a couple of years of daily use, sooner if you game or navigate while charging.
What actually helps: keep the charge in the middle of the range when you can, avoid charging under a pillow or on a dashboard in sun, and use the phone's built-in charge limiting or optimized-charging feature if it has one — those hold the battery below full overnight and finish just before you wake. Fast charging generates heat, which is the cost of the convenience; it's fine occasionally and less fine as a nightly habit.
The buying decision hiding here is serviceability. A phone with a battery that can be replaced at a reasonable price in a shop extends its useful life by years; a sealed design with an expensive or unavailable replacement turns a worn battery into a reason to buy a whole new device. Before you buy, find out what a battery service costs for that model and whether there's a repair option near you. If you keep phones for a long time, that number belongs in the purchase price.
Software support is the real lifespan of the phone
Count the years of security updates before you count anything else, because a phone that stops receiving patches is a phone you should stop using for banking, email and anything else that matters — regardless of how well the hardware still runs. Security patches are the line that matters; feature updates (new interface versions) are nice and stop earlier on most devices. The gap between the two is where people get caught: a phone that received its last major interface update two years ago may still be perfectly safe, while one that stopped getting patches last month is not.
The practical test is to find the manufacturer's published support commitment for the specific model, not the brand's general reputation, and to add those years to today's date. A device launched a while ago but still sold new may have most of its support window already spent. Buying last year's flagship at a discount is often the best value in the market — provided the discount reflects the support years you're giving up. Buying a cheap phone with a short window is fine if you plan to replace it on that schedule; it's a bad deal if you plan to keep it.
There is a second-order cost that doesn't appear on any spec sheet: app developers stop supporting older operating system versions, and eventually the banking app or the transit app you rely on simply won't install. That cutoff arrives without warning and is the moment a functional phone becomes inconvenient.
Cameras, screens and the parts you'll actually notice
Sensor size and lens aperture do more for low-light photos than the megapixel count printed on the box, and processing — how the phone combines multiple exposures into one image — does more than either. The honest way to judge a camera is to look at sample images shot indoors and at night, not in daylight, because daylight photos from almost any current phone are acceptable. The pause between pressing the shutter and the photo being captured is the other thing to check: on slower chips it's long enough that you miss the moment, particularly with moving subjects, and it's the single most common reason people upgrade from a budget phone.
Screens: brightness matters more than resolution. A display that can't get bright enough is hard to read outdoors, and that's a daily annoyance in a way that a slightly lower pixel density never is. High refresh rates make scrolling feel smoother and cost battery; most phones let you cap it. OLED panels give true blacks and better contrast; LCD panels avoid the burn-in risk that static interface elements can cause on OLED over long periods. Neither is wrong — it's a preference with a longevity trade-off attached.
Then the parts that get ignored until they fail: water resistance ratings (a rating is not a warranty — submerged phones are usually excluded from coverage), the quality of the speaker and microphone for calls, and whether the phone has the physical controls and ports you use. Losing the headphone jack or the expandable storage is a real cost if you relied on them, and it's worth deciding whether you're willing to pay it before the return window closes.
Buying used, buying last year's model, and when to walk away
The best-value purchase in smartphones is usually a previous-generation model bought new or a well-kept used one, and the thing that decides whether it's a good deal is the remaining software support window plus the battery's condition. A used phone with a worn battery and two years of patches left is a worse buy than a cheaper new phone with a longer window, even if the used one was the more expensive device when it launched.
If you buy used, ask for the battery service history or the phone's reported battery health, check that the device isn't carrier-locked or reported stolen (a blocked IMEI means it won't activate on any network), and confirm the model number matches the variant that supports your carrier's bands. Meet in person where you can, test the camera, the speakers and the charging port before money changes hands, and be suspicious of a price well below the market — the most common reasons are a locked device, a replaced screen of poor quality, or water damage that hasn't surfaced yet.
When to walk away entirely: if the phone you're considering has no published security update commitment, if it lacks the bands your carrier uses for its primary coverage, or if the battery replacement cost is close to the price of the device. Any one of those turns a cheap phone into an expensive one over the years you'll own it.
| Decision | What to check | What it costs you if you get it wrong |
| Network and SIM | Exact model number against carrier band list; eSIM support (GSMA SGP.22, spec v2.6.1) | Weak indoor and rural coverage; awkward line moves without a physical tray |
| Memory and storage | RAM for your background app load; storage one tier above your current use | Constant app reloads; early replacement because storage filled |
| Battery | Replacement cost and availability; charge-limiting features | A worn battery becomes a reason to replace the whole phone |
| Software support | Published security-patch commitment for that exact model | Unsafe for banking and email; apps stop installing |
| Camera and screen | Indoor and night samples; shutter lag; outdoor brightness | Missed shots; unreadable screen in daylight |
| Used market | Battery health, IMEI status, carrier lock, variant | A device that won't activate, or one that fails soon after purchase |
What SGP.22 actually governs, and what it doesn't
SGP.22 is the consumer RSP specification, and it is the only one of the three that describes the phone in your hand — SGP.02 covers M2M and SGP.32 covers IoT, so a spec sheet citing either of those is telling you about a fleet module, not a handset. What SGP.22 defines is the provisioning architecture: how a profile is downloaded over the air, installed on the eUICC, enabled, disabled and deleted. It does not define how many profiles you can keep resident — an eSIM stores multiple operator profiles — and it does not oblige your carrier to let you move one without a phone call. The specification being at v2.6.1 tells you the plumbing is standardised; it tells you nothing about the carrier's activation flow, which is where the friction lives.
The trade-off worth naming: because the profile is bound to the eUICC rather than a removable card, a dead phone takes the line with it. A physical tray costs you a swap; it buys you a fallback.
Why the M2M and IoT identifiers matter when you buy a module
If you're buying a connected device rather than a phone — a tracker, a meter, a vehicle unit — check for SGP.32, the IoT specification, before you assume phone-style eSIM provisioning applies. SGP.02 is the older M2M variant and SGP.32 is the newer IoT one; neither is a consumer profile flow, and a device built to one of them won't accept the QR-code activation you'd use on a handset. Ask which specification the hardware implements, not whether it "supports eSIM."