writing about tech

Tag: ios (page 2 of 2)

Apple approves and features “calculator” widget, then changes their mind

From six colors:

First there’s the maddening inconsistency: This is an app that was accepted into the App Store, and is even being featured in the App Store as I write this. And now, a few weeks in, someone at Apple has decided that the app is too… what? Too useful?

And the icing on the cake:

I just don’t understand this behavior from Apple, though maybe I’m just overly sensitive to it as a programmer myself. Don’t they realize a large reason for the success of the iPhone is the fantastic third-party developers who make their platform what it is? Either allow things or reject them, but don’t open your doors, welcome someone in, then slam those doors behind them and set the room on fire.

Update: Apple has clarified their position on Calculator Widgets, and it looks like PCalc can stay!

Why I use an Android phone, but still recommend the iPhone

A poster on The Verge’s forums asks:

So what am I missing? Where is the greatness in iOS?

Honestly, most “normal” people don’t need the power and flexibility that Android offers – they just need a reliable phone that calls and texts and runs apps and takes pretty pictures, and for that, the iPhone is pretty great. There’s also a lot to be said for the quality of Apple products – why bother to decide between half a dozen Android phones, each with their own limitations, when you can just buy Apple’s phone and call it a day? Sure, iOS isn’t necessarily as powerful or flexible as Android, but it’s also powerful enough that it be used for productivity, as long as you’re willing to mold your workflow to work the way Apple wants it to.

This was actually a topic of discussion on the Vergecast today, and the Verge folks said that the reasons to use an iPhone basically boiled down to:

  1. iMessage (including, in iOS8, SMS through Continuity)
  2. AirPlay
  3. Camera performance

It’s hard to argue with any of these, but for simplicity’s sake, let’s focus on iMessage. Android fans like myself can and will go on and on about the power and flexibility of Android, but most normal people never really see that power and flexibility. What they do see is that they can iMessage their friends and send texts from their computer with very little effort, and that’s huge.  This is what people mean when they talk about iOS’ ecosystem.

Can I send texts from my computer with third-party apps? Sure – but most Android users don’t, either because they don’t know about the apps that enable it, or they know but don’t care enough to go through the effort of making it work. There’s a huge value to be placed on making the barrier to entry as non-existent as possible.

PSA: If you downloaded iOS 8.0.1, here’s a fix for your issues

In case you haven’t heard, you probably shouldn’t have download iOS 8.0.1.  Fortunately, it’s already been taken down, so you can’t download it now on accident – but if you already downloaded it, The Verge has a great guide to fixing your issues:

Apple’s already said it’s investigating the issue, but if you’re one of the unlucky souls who downloaded and installed it, there’s a simple trick (via iMore) for getting your phone back up and running, without wiping anything.

Unfortunately, it requires iTunes, but you gotta do watcha gotta do.

I’m starting to understand why Google rolls out updates to their Nexus phones over the course of a few days, that way, any major issues like this are immediately discovered and the damage is contained.

You know, as opposed to potentially breaking 10 million phones.

What smartphone should I buy? – July 2014 Edition

Since I get this question fairly often – I’ve answered this question twice in the last week alone – I thought it might be worth doing a post about.  A few disclaimers:

  1. I don’t have a large amount personal experience with every device listed, though I’ve handled them all for at least a few minutes.
  2. If your question is “Should I buy a phone right now?”, the answer is almost always “No”, since there’s always something better coming.  This is meant as a guide for the person who needs or wants to update right away.
  3. This is written from a very US-carrier-centric point of view, although I still hate the idea of buying a phone through a carrier, and always recommend buying unlocked if it’s an option.  That way, you own your phone, and don’t have to deal with carrier bloatware or waiting for carrier approval before getting software updates.
  4. Try a phone yourself before buying it; no amount of rambling on my part will take the place of personal experience. You can even buy it if you want, and return it if you end up hating it, as long as you don’t do that too often.
  5. The size of the Pro/Con section doesn’t directly correspond to the quality of the devices, but rather my personal experience with them.  I’d recommend all of these phones almost equally, just to different people for different reasons.
  6. I only consider flagship phones, for the most part – in my mind, your smartphone is the most important piece of technology you own, so it shouldn’t be something you skimp on if you have the choice.  Splurge a little; you’re stuck with the thing for at least two years, after all.  If you want a cheap, unlocked, solid device, my advice ends with: just buy a Moto G or Moto E.

All of that said – there are, in my mind, four phones worth buying at this point, with a possible fifth and sixth.


The All-Rounders

The iPhone 5S

  • Available carriers: All
  • Pros: Let’s face it, the iPhone doesn’t need much introduction.  At this point, you probably know if you want an iPhone or…anything but an iPhone – and both choices are equally valid.  The iPhone is your best bet if you want a smaller-sized, one-handed phone with great performance.  The 8 MP camera is still nearly-unparalleled when it comes to all-around quality.  iOS is either a pro or a con, depending on what you want out of a smartphone.  Touch ID is brilliantly implemented, and thus far no phone has been able to match it.
  • Con: Both the size of the phone and iOS itself can be a con, depending on the user.  If you want a bigger phone, or if you want the freedom of Android, this obviously isn’t the device for you.  Honestly, if you’re okay with the size and with iOS, just stop reading now and get the 5S.  You won’t regret it.  Really, the only thing I can add is to not buy the 5C unless you really want a colored, plastic phone – the 5S is worth the extra $100.

The Nexus 5

  • Available carriers: AT&T, T-Mobile, Sprint.  Buy directly from Google if you can.
  • Pros: Although it doesn’t excel at any one thing, the Nexus 5 is above-average in most aspects that matters. The build isn’t as solid as the iPhone or the HTC One line, but I’ll take the Nexus 5’s plastic over Samsung or LG’s any day of the week.  The optically-stabilized 8 MP camera won’t blow you away, but it won’t often disappoint you, either – especially in HDR+ mode. The size is actually about average among other Android flagships, if not a bit smaller.  The software is Google’s idealized version of Android, which also happens to be my idealized version of Android – and it’s also guaranteed to be kept up-to-date for awhile to come.  Wireless charging is a great convenience, especially once you have a few Qi chargers scattered between work, home, and your car.   This feels, to me, like Google’s version of the HTC One X – which is the phone that made me an Android user, and also a phone I’d probably still be using today if it wasn’t for the 1 GB of RAM and the slightly-underpowered processor.  It’s also one of the cheapest ways to get a high-end, unlocked Android device.
  • Cons: The camera, while not the worst, could certainly be better.  I don’t even want more megapixels, I just want focusing and imaging performance on-par with the iPhone.  The build quality is above-average, especially given the price, but I wouldn’t mind if it was a bit sturdier.  Depending on your needs, the size could be a bit large.  Battery life can be unreliable, as the battery itself isn’t that big, meaning a rogue app or process can easily take off a decent chunk of battery before you realize what’s going on.  It’s not on Verizon, meaning a great many people in the US will never even have the option of owning the phone.


The Specialists

The HTC One (M8)

  • Available carriers: All
  • Pros: The M8’s most obvious and best features are its design and build quality, which may even rival the fantastic iPhone 5S.  HTC’s software is one of the few skinned versions of Android I can tolerate, and HTC has been very, very good about updating their software in a fairly timely manner, at least when compared to other non-Nexus, non-Motorola devices. The front-facing speakers continue to be absolutely unparalleled in the industry.
  • Cons: The biggest drawback here is the 4 MP “Ultrapixel” camera.  Some love it and some hate it, and unfortunately you may not know which category you fall into unless you try it yourself.  If you ever intend to print your smartphone photos, you should probably stay away – otherwise you may find that 4 MP is actually enough for your needs, especially if those needs are solely social media-related.  The physical-size-to-screen-size of the device is also worse than most other phones, mostly thanks to the front-facing speakers.  Finally, the phone can be a bit slippery and awkward to hold – again, try it yourself and you should find out quickly if it’s a problem.

The LG G3

  • Available carriers: All
  • Pros: This phone is all about being a spec monster.  While the build quality is above average at best, the screen resolution, processor, phone-size-to-screen-size ratio, and 13 MP optically-stabilized camera are all among the best of the best.  The software, while still not great, is far less offensive than it has been in years past.  It has a huge, long-lasting battery that is, unlike the other phones on the list, user-replaceable.
  • Cons: Despite the impressive phone-size-to-screen-size ratio, it’s still a 5.5″ screen, so it’s still a big device – perhaps too big for some people.  The software is, at best, inoffensive, and LG is not known for timely software updates – last year’s G2 took about 5 months to receive KitKat, even on unlocked International models.  Models purchased through a US carrier will take that much longer.  Despite the screen’s impressive (arguably unnecessarily-so) resolution, the colors can be a bit off and the screen won’t get as bright as some others.


The Runners-Up

The Moto X

  • Available carriers: All
  • Pros: The Moto X almost didn’t make the list, based solely on its age and the fact a successor is due soon, but now that it looks like successor might be noticeably larger, I decided to include it.  This is the phone to get if you want an Android device with a physical size close to the iPhone 5S, but with a screen .7 inches larger than the iPhone’s.  Motorola has taken stock Android and added to it in some fantastic ways with things like Touchless Control; these features are so good, in fact, that Google is gradually stealing them for stock Android.  The design fits perfectly in most people’s hands, and best of all, can be customized pretty heavily with Motorola’s unique Moto Maker.
  • Con: The only reason I’d advise against this phone are age and camera.  It was already slightly-under-spec’d when it came out a year ago, so I’m not sure it’ll age that gracefully over the 2-year period most people own a phone for.  The camera isn’t horrible, but it’s a notch below the Nexus 5, which is already a notch or two below the iPhone 5S.

The OnePlus One

  • Available carriers: AT&T and T-Mobile, but only available (sort-of) from OnePlus directly
  • Pros: This is, essentially, a larger Nexus 5 with better specs, a better camera, and CyanogenMod – the only flavor of Android that I might actually prefer to Google’s.  Unfortunately I haven’t had the pleasure of using one, so my praise has to stop there.
  • Cons: It’s still basically impossible to order one, thanks to OnePlus’ invite-only system.  It lacks the wireless charging of the Nexus 5, and the larger size compared to the already-not-small Nexus 5 could be a negative for some people.


The Rest

I didn’t include Samsung devices because, honestly, I don’t care for their software and hardware choices.  That said, the Galaxy phones have only gotten better since the S3, so if you liked the S3, you’ll probably like the S5 just fine.  If you’re on AT&T, the Active variant of the S5 might be worth looking at, too.  If you want a phablet, then you want a Note 3 – I wouldn’t even look at the others.

I’d love to include Sony devices, but as I’ve said, this is a US-centric post, and Sony phones almost never come to US carriers – or if they do, they come about 8 months after their international release.  If you’re willing to pay the full, unlocked price for one, though, the Xperia Z2 and the Z1 Compact are both great all-around phones with the added bonus of being waterproof.  If they weren’t so pricy unlocked, I would seriously consider getting one myself.


Final Thoughts

None of this is gospel, and all of it is (obviously) one guy’s opinion.  If I were to buy a phone today, I’d probably go with the Nexus 5.  Yes, there’s likely a successor on the way, but it’s a still fantastic deal and, I think, offers the best all-around Android experience, even if it doesn’t excel in any one particular area.

The mobile landscape is constantly changing, and the question “What phone should I buy?” is always a moving target. As the landscape changes, I’ll update this post accordingly.

Choosing, or losing, my religion

There’s been a lot of talk about how the ecosystem wars are heading up; walls are getting taller and moats are getting deeper, as both Apple and Google work to ensure you invest so heavily in their products and services that leaving becomes an overly-painful proposition.  The question was posed on The Verge’s forums:

I’ve been an Apple guy thus far. But I am waiting to see what comes out of the Moto 360, Nexus 6 and Android Silver launch later this year. We all pretty much know what iPhone 6, iOS 8 and OSX is bringing to the table, so no mystery there.

If I don’t switch from Apple now, I am not sure I ever will, so I want to give Android a serious look before making the decision. I want to wait till December and see how things shake out in the platform wars.

Anybody else taking the wait and watch approach before making their next big tech purchase – smart phone, tablet, smart watch etc.?

With all of this going on, I’ve been pondering just how invested I am in my current daily driver setup.  I know I have absolutely no desire to use anything but OS X on my primary computing device – everything else is certainly up for grabs, though. This year I’ll probably continue to coast with the Nexus 5 and 7, unless this year’s iPad refresh is truly remarkable. I love iPad hardware, and iOS is…fine, but I just can’t justify $400-500 for something that’s a luxury for me at best. I need a PC, and I need a smartphone…but my tablet use cases are generally limited to “electronic reader and light gaming machine”, and the Nexus 7 is perfectly adequate for that. Of course, I occasionally find myself tempted by the fairly impressive iPad-exclusive tablet game line-up, FTL being a high-profile example. Since price is my primary concern, maybe I’ll look into a used retina Mini at some point.

Phone-wise, I’m really reluctant to buy any more OEM or carrier phones, which at this point limits me to basically Nexus devices, an iPhone, or a Windows Phone. Only Nexus devices satisfy my desire to own a phone at a reasonable price, though; if I get an iPhone or a Windows Phone on contract, then I feel like I’m just renting my device from the carrier. Still, depending on how compelling 2015’s hardware is, I could certainly see myself moving off of Android.

That’s 2015, though – after my bump from an HTC One to a Nexus 5, this year is basically a mobile tech holding pattern, with the possible exception of the Moto 360 – which, of course, would further invest me in the Android world.  Either way, the next couple of years are going to be pretty exciting, and there’s some small comfort in knowing that it’ll be pretty hard to go wrong, regardless of what side you end up coming down on.

OK Google Everywhere – Touchless Control on the Nexus 5

For the last week, Google has been rolling out an update to their Google Now launcher that supports the “OK Google” command everywhere in the OS, not just the unlocked home screen.  This is rolling out gradually, so you may not see it yet – check your Google Now -> Settings -> Voice -> “OK Google” detection to see if it’s been enabled for you:

2014-07-03 16.42.20


If it’s not enabled yet, Android Police might have the solution for you.  I believe it requires Android 4.4 or higher, however.

This would be cool enough on its own, but certain devices now support “OK Google” even when the screen is off, as long as the device is charging – similar to iOS8’s “Hey Siri” command.  Neither device’s option is as powerful as the Moto X’s “OK Google Now” command, which works even when the device is unplugged, but it’s still remarkably useful – especially if you’re like me, and you have various Qi wireless chargers scattered between home, work, and the car.  Most of the day, my phone is generally sitting on a charging cradle near me.  Here are a couple of video examples I made this morning:

Personally, I find it’s more useful in the car, as that’s when hands-free operation is most essential.  The best part about this is that it will naturally continue to get more and more useful as Google expands their Voice Command API, which is sure to happen now that Android Auto – which by its nature is heavily voice-command centric – is on the horizon.  In its current form, it can already do quite a bit, but I can envision a time in the near future when I can just say (for example) “OK Google, continue podcast” and it will open up PocketCasts and hit play, or “OK Google, set Nest to away” could turn my A/C down when I leave the house.  The possibilities are almost more exciting than the current reality, and in some ways, it’s even making me question my need for a after-market Android Auto system, especially if I can get most of the same functionality from a Nexus 5, Google’s voice commands, and an AirDock.

The downside, of course, is that support is limited for certain devices, presumably because of processor limitations. Ideally, Google can eventually enable “OK Google” even when the device isn’t charging, depending on whether or not your phone’s processor supports that sort of lower-power mode.  Another minor issue I noticed is that sometimes the device takes a good 3 or 4 seconds to respond to the voice command, especially if you’re trying to demo it for some co-workers…cough, cough.

Between this functionality and the upcoming Trusted Bluetooth functionality in Android L, my Nexus 5 is finally adopting some of the best features of the Moto X.

What’s next for Microsoft in a world where Android is everywhere?

Yesterday, Google showed us a vision of a world where Android touches every area of your life.

Going for a run? Android on your wrist.

Going for a drive? Android in your car.

Having a party? Android on your TV.

What’s the hub for your smart life?  Android on your phone.

This is the world Microsoft has been aiming for, in some respects, since the introduction of their Metro design language.  Windows Phones look like Windows Tablets look like Windows Laptops look like the Xbox One – and that’s great.  Thanks to Microsoft’s cloud services, much of it plays nicely together, too – the problem is, right now, it doesn’t play nice enough together.  I can’t view or respond to my phone’s notifications on my tablet or PC, I can’t download the same app on my tablet and my phone and my TV, and there’s absolutely no sign of Windows on my wrist with only hints of Windows in my car.  Microsoft was perhaps the first to imagine a world where their products, services, and design give you a single, continuous experience regardless of your device and location (three screens and a cloud!), but at the current rate of iteration, Google is going to be first to realize that dream.

Microsoft didn’t have to let this happen; they’ve had all the puzzle pieces for awhile, they’ve just been too slow about putting them together.  Windows RT has been available since late October 2012, but I still can’t run Windows Phone apps on my tablet.  That feature is coming, but features are always coming – and this won’t be a new, unique feature to the platform, but another example of Microsoft reaching feature parity with its competitors.  They haven’t been been fast to iterate on Windows Phone, either; as great as the Windows Phone 8.1 update is, there was a year and a half between release of WP8 and WP8.1, which is an eternity in tech years.  Even then, WP8.1 is mostly about bringing feature parity, rather than bringing something new to the mobile world.  The execution on some ideas may be better (Cortana), but those ideas are all still things we’ve seen before.  Microsoft is busy playing catch-up with its phone OS, while Google is getting ready to put their “phone” OS everywhere.

Android’s development pace, in comparison, has been breakneck; look at how much Android changed in any given year and a half period since its release.  Now, some of that was out of necessity; for the first few years, Android needed drastic improvements to its design and performance, whereas Windows Phone 8 came out the door fast and stable.  Regardless of the reasons, though, it creates a mobile landscape in which Microsoft appears to be standing still next to Google’s dead-sprint, and Apple’s steady, relentless jog.

The only place Microsoft has the definitive advantage is in laptops and hybrids; Google can trumpet the success of Chrome OS all they want by pointing at the Amazon sales rankings, but Microsoft can point to actual sales figures.  There’s a long, long way to go before Chrome OS is a serious threat to Microsoft’s desktop world – but that desktop world is where Google has its trojan horse in the form of the Chrome browser.  Much of what Chrome OS is doing with Android can be done almost as well by the browser – just look at MightyText, which already lets me see and respond to text messages, or PushBullet, which already mirrors my phone and tablet’s notifications.  Google may never own the desktop, but with their strategy, they don’t really have to.  Their vision of Android being everywhere doesn’t require you buy a Chrome OS machine; it just requires you download the Chrome browser.

Apple, for what its worth, seems to have seen much of this coming, and have countered Google’s strength of open software and cloud services with their own strength – vertical platform integration.  iOS in the car was announced before Android Auto.  iOS8 and OS X 10.10 will bring iOS and OS X closer together with Continuity.  The iWatch has been rumored to exist by basically every tech site in existence, and something is almost certainly coming, hopefully this year.  Apple has been on the TV for years, and the only real missing piece of the puzzle for them now is to get the App Store on their TV solution.

So, we know Google’s next moves, and we know Apple’s, but what are Microsoft’s?  Satya Nadella seems to be saying all the right things; mobile first, cloud first certainly the direction the world is moving in.  We’ve already seen moves of a more open Microsoft, as Office has finally made its way to iOS and Android, and though the seeds for that were almost certainly planted in Ballmer’s days, it’s possible Nadella was the one who finally decided to push it out the door.

The coming year or two will hopefully see the Xbox One running the same apps as their Windows tablets and PCs, and those same tablets and PCs running many of the same apps as Windows Phone.  Microsoft has demonstrated Windows in the car, but questions remain about when it will be available and who will support it when it is available.  It also relies, at least partially, on developers updating their apps for the car – and given how much trouble Microsoft has historically had getting developers to make apps for Windows Phone, I have to wonder how much support Windows in the car will get.  Finally, though there have been rumors of a multi-platform Microsoft smartwatch, but no further information has materialized.  Microsoft will certainly move into the wearable space, in some form, but no one really knows what form it will be in and how long it will take.

So what should Microsoft do next?  As I see it, they have several options, not all of which are mutually exclusive:

  • Stay the course.  Keep pushing Windows Phone, Windows RT, Windows 8, and Xbox One closer and closer together.  This may actually work, they just need to start pushing faster.  Microsoft can’t afford iterate as slowly from 2014 to 2016 as they did from 2012 to 2014.  Hopefully, with Nadella at the helm, the next two years will be very exciting.  The biggest problem with all of this may be customer’s perception of Windows 8, which seems to be mixed at best.
  • Continue to make their software more available.  Office is basically everywhere now – why not do the same for IE?  I use Chrome on my laptop because it syncs with my phone; if IE was on my phone, then I’d have one less reason to use Chrome.  Push for a world where using Microsoft doesn’t necessarily mean using Windows, just like using Google doesn’t necessarily mean using Android.  Google wants to put Android everywhere, but its open nature means Microsoft can put all of their software and services on Android and ride that same wave. If Google is the open cloud company, and Apple is the vertically-integrated hardware company, the place for Microsoft might be somewhere comfortably in the middle.
  • Drop Windows Phone and shift their phone strategy to Android.  Now that Microsoft has their own in-house phone team, they could develop first-party Android phones.  This is probably the least likely strategy in the short-term, but you never know what will happen in the next few years.  There was a time when the idea of Apple hardware running Windows was laughable, too.  This would allow them to leverage things like Android Wear and Android in the car without having to invest in those strategies internally. Still, this is my least-preferred option; as much as I’d love to see Nokia’s old hardware design team make a fantastic Android device, I’d rather see a more competitive mobile landscape with at least three major players.
  • Stay the course with Windows Phone and develop a first-party Android phone.  Continue developing Windows Phone and great Windows Phone hardware, but spin-off a piece of Nokia’s old design team to push out an Android-running, Microsoft-developed smartphone – like the Nokia X line, but without the customized build of Android.  This may come across as unfocused, but if anyone has the resources to hedge their bets like this, its a company the size of Microsoft.  If they start this project now – even if they don’t release it – they’d be ready for a worst-case scenario where Windows Phone, Windows in the car, and their wearables don’t get the kind of traction they want.
  • Figure out what the next big tech shift is, and beat everyone there.  Apple beat everyone else to the first modern smartphone, and now it looks like Google will beat everyone else when it comes to a single experience on all platforms.  Rather than chasing Apple and Google, ideally Microsoft will forge their own path to…whatever it is we haven’t thought of yet.  This may lead back to the idea of yielding the mobile space to Android and developing their own Android hardware, so that they can at least have a strong mobile presence while they work on whatever is coming next.

Regardless of what Microsoft does going forward, I desperately want them to succeed.  A mobile world dominated primarily by Android and, to a lesser extent, Apple, might be good in the short-term for consumers, but in the long-run, innovation will stagnate without enough competition.  Google was forced to sprint with Android for so long because Apple had such a big head-start; for them, it was iterate-quickly-or-die.  I don’t know what Microsoft will do next, but I hope for their sake and ours that they do it much, much faster than they have been.  The time for caution is over.

Nest is Opening Up (Finally)

Nest co-founder Matt Rogers:

“The home shouldn’t be a platform war.  We’re going to be neutral. Switzerland.”

From Arstechnica.

Being a Nest owner from the pre-Google days, I’ve been waiting for Nest to open their API, and I’m glad to see it’s finally happening – and I’m even more thrilled to see that it’s so open.  As Rogers said, home automation should be platform-agnostic – no one wants a Google Home or an Apple iHome; we just want our Android devices and iProducts to work seamlessly with whatever devices we’ve chosen from whatever companies have the best stuff.

The devil’s in the details

I recently replied to this post on The Verge, and I think my response is worth sharing as it sums up my current view on status of mobile tech, at least as it pertains to Android and iOS.

For the past couple years I’ve owned the 3 last Nexus devices: the Galaxy, the 4 and the 5. Each one got better than the last. Before that, I had a various smattering of iPhones, Blackberries, Sony Ericsson devices, Nokias. But, being the finicky bugger that I am, the other day I randomly decided to buy an iPhone 5S.

In any instance there’s a tiny bit of give and take on both ends and overall they probably just average out to being “Holy shit, both of these phones are pretty damn good and basically do everything I need them to do within reason.”

TL;DR: The platform war is over. Everything is beige.

I couldn’t agree more, especially with iOS8 bringing a lot of the features I’ve enjoyed on Android to the iPhone. It’s becoming less and less about what’s better, but about the small details and which of those details matters most to the individual user. For me, it’s come down to a few key things:

  1. I actually really love wireless charging, though I understand why others don’t care about it. Now that I’ve had it, though, the sheer convenience factor is something that’s hard to overlook.
  2. I prefer a larger device – 4.5-5 inches – to a smaller device.
  3. I want full control of my phone, at least where carrier crap is concerned. Don’t give me your shitty software, or your ridiculous restrictions on how I can use the data that I am paying you for. The Nexus 5 is the purest form of that, but the iPhone is the next best thing. I find it incredibly unlikely my next phone will be something besides a Nexus or an iPhone.

The thing is, none of these are deal breakers – they’re small details, but they’ve become important to me in a world where everything else is basically equal.


Copyright © 2022 writing about tech

Theme by Anders NorenUp ↑