A smartphone is a bundle of irreversible decisions — the modem and band support, the bootloader policy, the update commitment, the repairability, and now the eSIM provisioning standard — and almost none of them can be changed after you pay. The specs that matter are the ones you can't undo: which cellular bands the radio covers, whether the bootloader can be unlocked, how many years of OS updates the vendor has contractually committed to, and whether the SIM is a tray or an eUICC soldered to the board. Everything else — storage, color, camera tuning — is a preference. The rest of this page is about telling those two categories apart before you spend money.
How the radio decides whether your phone works where you live
Buy the phone for the bands your carrier actually transmits on, not the bands in the marketing header. A modern handset lists dozens of LTE and 5G NR bands, and the list is not a compatibility guarantee — it's a menu of what the radio can tune to, subject to carrier certification and firmware. The failure mode is specific and easy to recognize: you get full bars on LTE but data crawls, or 5G shows up only on one block of town, or calls drop to 3G-quality audio indoors because the phone lacks the low-band frequency your carrier uses for building penetration. Carriers publish their band plans; cross-check the phone's list against them before you buy, especially for imported models, which often omit the low bands a domestic carrier relies on for coverage in rural areas and inside large buildings.
Two radios matter more than the band count. First, the modem generation: a phone on an older modem will hold a weaker signal at the cell edge and drain more battery hunting for service, which you notice as a warm pocket and a dead battery by evening in a marginal-coverage area. Second, carrier aggregation and dual-SIM behavior — if you run a physical SIM and an eSIM together, one of them typically drops to a lower data standard while both are active, and the phone may not tell you clearly which. If you travel and keep a home line plus a local data plan, test the combination before you depend on it.
The honest trade-off: a phone with a narrower band list is often cheaper and perfectly fine if you never leave dense coverage. The moment you drive through farmland, work in a basement office, or switch carriers, the missing bands become the whole story. Band support is the single most expensive thing to get wrong because no software update adds an antenna.
eSIM is a provisioning standard, not a feature — and the standard number tells you what you're getting
An eSIM is not a chip you buy; it's an eUICC — an embedded Universal Integrated Circuit Card — plus the GSMA Remote SIM Provisioning process that downloads, installs, enables, disables, and deletes operator profiles over the air. The phone ships with the chip soldered down, and the carrier relationship arrives later as a profile. That distinction is the whole point: the hardware is fixed at manufacture, the subscriptions are not.
The specifications split by device class, and the identifier on a spec sheet tells you which one a product implements. Consumer phones use GSMA SGP.22, the Remote SIM Provisioning architecture for consumer devices, currently at specification version v2.6.1. Machine-to-machine deployments use SGP.02, and the newer IoT profile, SGP.32, targets constrained devices that need remote management without a user in the loop. A phone is an SGP.22 device. If a product's documentation cites SGP.02 or SGP.32 for something you're buying as a handset, that's a sign the vendor is repurposing an IoT module or hasn't done the consumer certification work — ask questions.
An eUICC can hold multiple operator profiles, which is the practical benefit: you can keep a home line and a travel data profile resident and switch between them in software instead of fishing a tray out with a paperclip at an airport. The catch is that "can store multiple" does not mean "all active at once." Enabling one profile typically disables another, and the switching is deliberate, not seamless. Deleting a profile is also not the same as cancelling service — the carrier still bills you until the line is closed on their side, and a deleted profile can't always be reinstalled without a new activation from the carrier. Treat profile deletion as irreversible until you've confirmed otherwise.
What goes wrong in practice: you buy an unlocked phone expecting eSIM support, and the carrier's activation flow only recognizes IMEIs from phones they've certified, so the QR code fails at the "contacting server" step. Or you transfer a profile between phones and the old device keeps a stale profile that intermittently grabs the network. Or you factory-reset with profiles installed and lose one that wasn't backed up. The fix is boring — activate on Wi-Fi, keep the carrier's app installed, and don't delete a profile until the new one is confirmed working — but people skip it because the setup looks like a two-minute QR scan.
Update commitments are contracts, and you should read them like one
Count the years of OS and security updates the vendor commits to in writing, and compare that number to how long you intend to keep the phone. This is the second irreversible decision, because a phone that stops receiving security patches is a phone you should stop banking on. Vendors now publish commitments in years from launch, sometimes split between full OS upgrades and security-only patches — a phone can be out of feature updates and still be safe, and that distinction matters when you're deciding whether to keep it another year or replace it.
The practical test is the calendar, not the marketing. Note the launch date, add the committed years, and see whether that date falls before or after you'd realistically replace the device. A phone launched two years ago with a shorter commitment may already be near the end of its patched life when you buy it new at a discount — the savings are real, but you're buying a shorter runway. Check the vendor's own support page for the specific model rather than the family name, because commitments often differ between a flagship and its cheaper sibling even when they share a launch event.
The trade-off: long update commitments cost money up front and often come with slower hardware than a cheaper phone with a shorter promise. If you replace phones frequently, the commitment is worth less to you than raw performance. If you keep phones until they break, the commitment is the most valuable line on the spec sheet, and it's the one that determines whether the device is still safe to use for banking and email in its fourth year.
Bootloader policy, repairability, and the cost of lock-in
Check whether the bootloader can be unlocked before you buy if you care about running the phone past its vendor's support window. An unlockable bootloader lets you install a community-maintained operating system after official updates stop, which extends the useful life of the hardware by years — but it also voids warranties on many devices, trips banking and payment apps that refuse to run on unlocked or rooted phones, and requires technical comfort most buyers don't have. Some vendors allow unlocking only on certain models or after a waiting period; others have removed the option entirely. This is a genuine fork in the road, not a feature to tick.
Repairability is the other half. A phone glued shut with a battery that requires heating and prying to reach is a phone that becomes e-waste the moment the battery degrades, which it will. Look for published repair guides, availability of genuine parts, and whether the vendor sells batteries and screens to independent shops. The cost shows up later: a battery replacement on a repairable phone is a routine expense, and on a sealed one it's often quoted close to the phone's resale value, at which point people replace the whole device. Neither approach is wrong — sealed designs are thinner and more water-resistant — but you should know which one you're buying.
Software lock-in is quieter. Cloud photo storage, proprietary messaging, and account-bound backups make switching expensive in time rather than money. Before you commit, export a test batch of photos and contacts to a neutral format and see how painful it is. If the answer is "very," that's a cost you'll pay at every future upgrade, and it's worth choosing a phone that makes export easy even if it costs a little more now.
Cameras, screens, and batteries: where the spec sheet lies
Megapixels are the least useful camera number on the box. Sensor size, pixel binning, lens aperture, and — above all — the image processing pipeline determine what your photos look like, and none of those are captured by a headline figure. The reliable way to judge a camera is to look at full-resolution samples shot in the conditions you actually photograph in: indoor lighting, backlit windows, moving children, night streets. A phone with a large main sensor and modest resolution will beat a phone with a tiny high-resolution sensor in low light almost every time, because the larger pixels collect more light before any processing happens.
On screens, brightness and refresh rate matter more than resolution past a certain point. A display that dims aggressively in sunlight is unusable outdoors regardless of its pixel density, and a variable refresh rate saves battery in ways a fixed high rate doesn't. Look for the peak brightness figure quoted for full-screen content rather than a small highlight area, because the two numbers differ substantially and only one reflects how the phone behaves when you're reading in the sun.
Battery capacity in milliamp-hours is a rough guide at best; the modem, the display, and the software's background behavior decide the real runtime. The useful question is charging speed and heat: a phone that charges fast but runs hot will throttle, and a battery that lives hot degrades faster. If you charge overnight on a nightstand, heat is your main enemy, and a phone that supports a slower overnight charge mode will last longer than one that doesn't.
The buying sequence, and what each step costs you
Start with the carrier and the band plan, because that decision constrains everything else and can't be fixed later. Confirm the phone covers your carrier's bands, confirm it's certified for their network, and confirm whether you need dual-SIM behavior and how it degrades when both lines are active. Then confirm the SIM form: if you want eSIM, verify the phone implements GSMA SGP.22 and that your carrier supports it for that specific model, not just for the brand.
Next, pin the update commitment to a calendar date and compare it to your replacement cycle. Then decide the bootloader and repairability posture — locked and sealed versus open and serviceable — and accept the trade-off you chose. Only after those four are settled should you compare cameras, screens, and storage, because those are the decisions that are actually reversible: you can buy a case, add cloud storage, or live with a camera you don't love, but you can't add a band or a security patch.
| Decision | Reversible? | What it costs to get wrong |
| Carrier band support | No | Dead zones, dropped calls, no fix short of a new phone |
| eSIM support (GSMA SGP.22) | No | Carrier activation fails; travel plans unusable |
| Update commitment | No | Unpatched device within your ownership window |
| Bootloader policy | No | No path to community OS after support ends |
| Repairability | No | Battery replacement priced near resale value |
| Storage, color, camera tuning | Yes | Preference, not a functional loss |
The order matters because the top rows are permanent and the bottom rows are not. Most buyers do it backwards — they pick the camera they like, then discover the phone lacks a band or an update promise — and that's the expensive mistake. Work down the table, not up it.
What the SGP.22 version number actually constrains
Ask which SGP.22 revision a handset's eUICC firmware implements, not just whether it supports eSIM. The consumer specification is at v2.6.1, and older implementations exist in phones still on sale — the profile download, enable, and delete flows behave differently enough that a carrier's activation app can fail at the server handshake on a device that looks fully compliant on the box. The symptom is a QR scan that hangs, then times out, with the carrier blaming the phone and the vendor blaming the carrier. A firmware update can close the gap; nothing else can.
Why profile slots are a travel feature, not a dual-line feature
An eUICC stores multiple operator profiles, but the count tells you almost nothing about simultaneous use. Enabling a travel data profile typically disables the home line's data path while leaving it registered for calls, and the phone's status bar rarely makes that swap obvious — you find out when a two-factor code never arrives. The reliable pattern is to keep the home profile enabled for voice and switch the travel profile on only when you need data, then check the carrier settings menu before you trust it. The trade-off is friction: a few taps each time you land, in exchange for knowing which line is live.