writing about tech

Tag: apple pay

Apple Watch Review

Smartwatches are incredibly hard to review. I’ve reviewed two others now, and I’m still not really sure how to approach it.

As a reviewer, you typically write with the assumption that the reader has, at the very least, accepted the value of the product category, and is simply deciding which product in that category they want. If you’re reviewing a smartphone, it’s a fair assumption that the person reading is already sold on the very concept of smartphones. Smartwatches are different. Many people – even people in the tech world – don’t see the value.

While I have wavered from time to time on the value of smartwatches, I generally err on the side of finding them useful. It’s difficult to explain why, however, because it’s all about the little differences they make in your day – each of which, taken individually, don’t sound terribly compelling. Today, my Pebble-owning co-worker excitedly explained how great it was to get his two-factor authentication codes directly on his wrist, without having to dig out his phone to read them. It’s one of those paradoxes that simultaneously thrill smartwatch owners while confusing cynics. “That’s it?”, they ask. Obviously, that’s not it, but it’s a fair question. If smartwatches are so great, why are they so difficult to sell people on? For me, it’s all about form factor.

My life is full of screens. My laptop screen, my tablet screen, my smartphone screen, and my smartwatch screen. All of them serve fundamentally different purposes, and are ideal for different types of activities. My laptop is better than my tablet for writing or coding or browsing, but not for traveling, or using in bed, or gaming, or using on a stationary bike or treadmill. My tablet is better than my smartphone at most things, other than photography, but isn’t something I want to haul with me from place to place.  My smartphone is better than my smartwatch for most activities that take longer than a few seconds – writing a longer e-mail or text, or browsing Facebook or Twitter.

So why a smartwatch? Well, stop and think for a moment: how many times do you dig out your phone for an activity that only actually requires a few seconds of passive interaction? Checking the time. Checking the weather. Checking your calendar. Checking your notifications. Starting a timer. Checking an item off a to do list. Creating a reminder. Reading a text. Reading an e-mail. Arming an alarm system. Starting to track a bike ride. Checking the stats during that bike ride. Playing or pausing audio. Double-checking directions to wherever you’re going. Paying for something. Identifying a song that’s playing. These are all things I do multiple times a day, and, honestly, a smartphone isn’t the ideal form factor for those. They sound trivial, because they are mostly passive, quick interactions, but they’re also the things I probably do most with my phone, and as average phone size continues to get bigger, taking out an oversized device for a trivial task feels increasingly ridiculous. As with many things in life – the little things make all the difference. Little conveniences, all day, every day, add up to something I like having in my life.

That’s almost 500 words, and I haven’t even really talked about the Apple Watch. There’s a reason for that: it’s because the Apple Watch is a smartwatch. It’s a damned good smartwatch, probably the best I’ve ever used, but it doesn’t sell the form factor in a revolutionary new way.

I don’t think it has to, though.  Apple won’t change the wearable world because they reinvented the product category, but rather, because they will introduce the product category to millions of people who may never have tried a smartwatch otherwise – and I think many of those people will be pleasantly surprised by how much they like wearing one.

The hurdle for many, and rightfully so, is the price. After the $149 Pebble, I balked at spending $249 on a Moto 360 last year, so I certainly understand the hesitation at the Apple Watch’s $349/$399 asking price. The good thing is that it feels like a device worth what you’re paying for it, but still, that’s a lot to ask for a device in a still-largely-unexplored category.

I was initially skeptical of the design, but it grew on me after seeing it in person, and the positive impressions have continued. Unlike some Android Wear watches, which impressively imitate  “regular” watches, the Apple Watch makes no attempt at doing so – for better or worse, it  undeniably looks like an Apple product. This is almost certainly intentional; Apple doesn’t want their watch to be mistaken for a regular watch.  They want people to immediately recognize it’s an Apple Watch. While understandable from a branding perspective, it also highlights one of Android Wear’s chief advantages: choice. Given another a year or two, I imagine almost anyone will be able to find an Android Wear device that matches their taste. If you want an Apple Watch, you better like the Apple Watch.

There is one area of personalization where Apple does win, though, and that’s with watch bands. While some Android Wear devices might let you swap in standard watch bands – again playing in their attempts to mimic a regular watch – Apple has found an incredibly slick, user-friendly way to easily swap bands within seconds. Whatever you think of the Apple Watch, don’t doubt this: Apple (and their third-party partners) are going to make an obscene amount of money selling bands to people. I’m already planning on buying at least one additional band – Milanese Loop – and swapping it out with the Sport band after my workouts. That’s absolutely insane, because I’m not a fashionable person, and this isn’t something I’d even consider doing with a regular watch. But Apple makes swapping the bands so easy, and the Milanese is ridiculously nice.

Fortunately, if you’re more sane than me, the band that the Sport model comes with is surprisingly good. Apple calls it “fluoroelastomer”, but I just call it “incredibly comfortable”. It’s the first watch band I’ve worn in a long time that I can actually forget I’m wearing, and that includes the pretty-great leather band that came with the 360. The only frustrating thing is that I’d prefer the black color, but for some inane reason, Apple refused to sell the silver aluminum Sport with the black band. So white will do, for now.

As I mentioned above, my life is full of screens, and the Apple Watch’s is one of the nicest among them. It’s the first smartwatch I haven’t been able to see pixels on, and AMOLED – with its ability to only light up the pixels in use while keeping the rest of the screen black – continues to be the ideal screen technology for a smartwatch from both an aesthetic perspective and a functional perspective.

One more thing about the hardware: I laughed at the digital crown when it was announced, but now I find myself using it constantly. It’s not a “revolutionary” control mechanism by any stretch of the imagination, but as a button that doubles as a way to quickly scroll content, it’s certainly a nice-to-have.  In the last day or so, though, I feel like it’s gotten slightly less responsive on initial use – like it “sticks” for a moment. It’s certainly tolerable, but hopefully it won’t get much worse.

As many doubt as I had about the hardware, they paled in comparison to my doubts about the software. I questioned Apple’s apparently app-centric approach, while praising Android Wear for its comparative simplicity. Once again, actual usage has mitigated those doubts – mostly.

While much has been made about apps on the Watch, they’re actually not as front-and-center as I feared. You could legitimately live in the watch face and get most of the functionality you’d want, as the watch face hides the two most important features – missed notifications, which are available with a swipe down, and Glances, which are available with a swipe up.

Glances are one of my favorite parts about Watch OS. They give me the information I care about most, while also acting as a shortcut to launch the app if need a bit more or want to interact with the information. Dark Sky tells me the current temperature and the weather for the next hour. Wunderlist shows me my next task. Activity shows me my progress towards my fitness goals. For this reason, I’m also incredibly picky about what gets to go in my Glances area – if I have to go through too many other Glances to get to the one I care about, then much of the point is lost.

Notifications, on the other hand, are about the same as you’ll find on Android Wear, right down to the fact that they inherit the notification actions you’d get on your phone. With Inbox, I can mark an e-mail as “Done” right from the notification on my phone – same with the Watch, and exactly the same as Android Wear. The only exception is with some of Apple’s first-party apps, which generally allow you a bit more interaction than third-parties do. For example, if you’re talking to someone over iMessage, you actually see the same “typing” indication on the watch that you’d see on your phone. It’s a small touch, but it’s the sort of attention to detail that is prevalent throughout the hardware and software.

Otherwise, I’d say Watch OS is actually a bit behind Android Wear in the area of notifications – as-of right now, you can only dictate replies to messages that come in through the default Messages app, so no responding to Hangouts messages or Facebook Messengers messages from your wrist. This is an obnoxious limitation that I hope is dealt with sooner rather than later.

There are some aspects of the Watch I prefer to other smartwatches, though. The “taptic” engine, despite the ridiculous name, really is a step above the vibration engine found in other devices. The same way the Force Touch trackpad actually feels like clicking, the “taptic” engine genuinely feels like something is tapping your wrist to get your attention. The look on people’s faces when I put my watch on their wrist and send myself a message is pretty delightful. The other nice thing: when you get a notification, your wrist doesn’t light up. You just get the tap, and you can either raise your wrist to immediately view what came in, or just check on it later. This has made the smartwatch experience far less distracting to me and those around me, and as an added bonus, people can no longer awkwardly read incoming messages off of my wrist.

Speaking of the screen-on-on-wrist-raise feature, it works…mostly. It might be a little more consistent than the Moto 360 was, but there are certainly times where I go to check something and it misbehaves.  It does seem to false trigger less often, though – for example, it doesn’t randomly turn on and off when I’m driving around.

So, notifications above the watch face, Glances below it – what about the watch faces themselves? Well, some are great, and some are pretty-but-useless, and some are just useless. Fortunately, I (eventually) figured out how to delete the ones I didn’t care about, so now I’m down to Utility (somewhat pretty, mostly useful), Modular (not really pretty, but has the most information), and four others that are very pretty but almost entirely useless.

What makes a watch face useful? What is quite possibly my favorite feature of the Watch – the complications. While Apple currently doesn’t support third-party watch faces, and some suspect they never will, the existence of complications helps soften the blow. On my Modular watch face, I currently have: time (obviously),  date, my next calendar appointment,  current temperature, battery level, and, perhaps my personal favorite, my activity level for the day so far. The activity level information is something I desperately wanted in Android Wear, so I’m pleased it’s a default option on the Watch.

Perhaps the best thing about complications, though, is that they act as shortcuts to full apps. The current temperature is sometimes what I want, but sometimes I want the forecast for the rest of the day – tap on the temperature and I’m in the Weather app. Next calendar entry is great, but what’s my agenda for the rest of the day? Tap on the calendar entry and I’m there. It’s hard to believe that the Apple Watch is, far as I know, the first to do something that seems so obvious.

As for those full-apps? Well, it’s a mixed bag. Like watch faces, some are great, and some are useless? Calendar? Great! Here’s my schedule. Remote? Great! Controlling my TV from my wrist never gets old. Photos? …thanks but no thanks. Twitter? Why, why would I want Twitter on my wrist? Instagram? God no.  Wunderlist? Great! I can jump in and mark something as completed – something I wanted to do on my Moto 360, but a proper Wunderlist app wasn’t available during my months spent with it. Never doubt Apple’s ability to bring third-party apps to the table in a way competing platforms just can’t seem to do, for whatever reason.

Performance of those apps is occasionally slow, as they aren’t running natively on the watch, but rather are just fancy extensions of something running on your phone. However, I’ve found performance generally acceptable, and far better than the initial reviews led me to believe. I’m not sure if Apple made some optimizations prior to the retail release, or if tech journalists are just less patient than me.

We’re now over 2000 words in, and I still feel like there’s a lot more to cover. I could probably go on for another 2000, but instead, I’ll shotgun out some random thoughts I’ve had over the last few days.

  • Force Touch? It…usually works, but it’s frustrating when it fails to. Also not sure if I like the general interface paradigm of hiding actions behind a Force Touch, as it basically requires the user Force Touch every screen to see what they can do. A subtle visual indicator would be nice.
  • Digital Touch? I haven’t drawn anything, or sent my heartbeat to anyone, so I can’t really say. I’ve sent a couple of animated emoji, and they send as animated images to non-Apple Watch owners. Cute, but basically useless.
  • Siri? Mostly great, surprisingly. Way better than on the phone. Dictation still seems a bit slower than Google’s dictation on Android and Android Wear, but it’s acceptable.  “Hey Siri” detection is significantly less reliable than “OK Google” detection, for whatever reason – however, it’s available from everywhere on the watch, not just the watch face, so that helps make up for it. Perhaps more annoying is that Watch OS lacks Android Wear’s “automatically time out and complete the activity” option, so if I create a reminder or dictate a message, I still have to tap “Okay” to finish creating it. Clunky and annoying – it’s obvious Android Wear was built more around voice as a primary input mechanism than the Apple Watch was. Watch OS seems to know that voice input is important, but at times still treats it as a second-class citizen.
  • Taking a phone call on your wrist? Feels kind-of cool the first time you do it, but not something I’d envision doing on a regular basis.
  • The screen is surprisingly easy to see in the sun. Early reviews said otherwise, though that could be because the Apple Watch Sport’s screen apparently performs better in sunlight than the Apple Watch’s.
  • Battery life is more or less the same as it was on my Moto 360. It certainly lasts longer while exercising, and I no longer feel obligated to charge it after a workout to get a full day out of it. Ittill goes on my charger when I get in the shower, because the charger’s already on my nightstand, and where else would it go? Speaking of the charger – I like that it’s magnetic and wireless, but still miss the elegance of the 360’s Qi charging dock, not to mention its use of a wireless charging standard.
  • I like that the watch automatically locks itself when removed from your wrist. Given that anyone with my watch could easily trigger an Apple Pay transaction, this seems like a particularly elegant solution to a necessary feature.
  • Speaking of which: Apple Pay was born to live on the Apple Watch. Apple Pay (and NFC payments in general) are already pretty cool, and while paying with your phone is generally faster than paying with a credit card, paying with something that’s already on your wrist is noticeably faster than both.
  • The watch can be set to unlock to the last used app, which is useful if you’re doing something like using the watch as a remote for an Apple TV, or monitoring an active workout. As a bonus, all apps have the time in the upper right corner, so it’s still useful as an actual watch when you aren’t on the watch face itself. In a way, it becomes a makeshift whatever-activity-you’re-doing-centric watch face.

And then, of course, there’s the fitness stuff. I could write a whole post about that – in fact, I already have – but the long and short of it is that it’s exactly what I’ve wanted out of a fitness tracker for years. It passively tracks my movement throughout the day, while also actively and accurately tracking my heart rate during exercise. The only time I’ve seen it struggle to read my heart rate is while dancing, which Apple explains with: “Rhythmic movements, such as running or cycling, give better results compared to irregular movements, like tennis or boxing.” It’s not that it stops working entirely during those activities, just that it seems to take a reading less often. There are, of course, dedicated fitness trackers that will also read your heart rate – but as someone who has already decided they want to wear a smartwatch, I’m not really interested in wearing something on both wrists.

Most importantly to me, MyFitnessPal’s latest version will update my calorie allocation for the day based on the activity recorded by the watch, and the Fitbit app can be set to record my steps based on my iPhone rather than the Fitbit hardware.  All of this means I finally have what I wanted since the original Pebble – a smartwatch/smartphone combination that will allow me to retire my Fitbit One without sacrificing MyFitnessPal functionality or the social aspects of the Fitbit ecosystem.

So where does that leave us? The Apple Watch is, in my experience, a paradoxical device. Sometimes it feels like Apple’s most-polished first-gen product ever…until it doesn’t. 95% of the time, it’s a smooth, reliable experience…but then Siri will freak out. Or a poorly written Glance will cause my watch to reboot. Or I’ll show the watch to someone and it won’t let me enter my passcode to unlock it without restarting it.

Bottom line: the odd quirk aside, it’s the best smartwatch and the best fitness tracker I’ve ever used, but the price is pretty hard to swallow unless you want both types of devices. Most people probably shouldn’t buy it just as a smartwatch, or just as a fitness tracker – it doesn’t do enough beyond what other smartwatches do to revolutionize the category and push into “objectively useful for everyone”, and it’s too expensive to buy as solely a fitness tracker. 

For most people, it’s hard not to recommend waiting for the next generation – not because this one isn’t good, but because the next one will probably be better and cheaper. If nothing else, the next generation will drive down the cost of this generation. It’s not that it isn’t great or useful – it’s pretty great and pretty useful – but rather, that it’s not necessarily $349 worth of useful. At $299, it becomes more reasonable. At $249, it’d be much, much easier to recommend.

But, if you have an iPhone, and you love gadgets – it’s a pretty damn cool gadget, so that might well be enough. If you love gadgets and have an interest in fitness tracking, like me, then it basically sells itself.  So if the question is “Should I buy?”, the answer for most people is “probably not”. But if the question is “If I do buy it anyway, will I like it?”

Yeah, I think you probably will.

iPhone 6 Plus Conclusions: Battery, battery, battery. Also camera.

Two weeks ago, I purchased an iPhone 6 Plus, largely due to my issues with battery life on Android phones.  If you’ve been following my posts,  you’ve probably figured out that I’ve decided to keep the iPhone and stick with iOS for awhile. I wish I could say I had some grand, all-consuming revelation, but really, it comes down to the same reason I decided to try an iPhone again in the first place: battery life.

My rule for the last two weeks was a simple one: if I was going to keep the iPhone, it had to last all day, every day, only being plugged in at night when I get to bed.  Day two (New Year’s Eve) was actually a close call – it came off the charger early for work, and was used heavily throughout the day to coordinate my NYE party, stream music, etc. It scraped by with 10% left when I finally went to bed at 2 AM.

Since that day, though, I’ve come nowhere close to hitting that 10% mark. Sitting at home right now, after work, 11 or so hours after my phone came off the charger, my phone is at about 70% percent. When I go to bed, I will likely have more than 50% remaining – probably closer to 60%, actually. That means I could have used my phone way, way, way more, and still had battery to spare.  One morning, I went running for two and a half hours, with RunKeeper tracking in the background the whole time, streaming podcasts to my Bluetooth headphones, and still had 88% battery left.

These numbers are about average from what I’ve seen in my two weeks of usage.  They are also quite possibly irrelevant to you, as we likely live in different places, work in different places, and use our phones very differently.  It’s an apples-to-oranges comparison to anything except my own previous experiences with phones – and in that regard, I can say it’s exceptional. I rarely play games or stream video, but I also don’t baby it – I simply use it when I need it. You know, like a tool should be used.

The key to this is standby time: when the phone’s screen is off, it is actually asleep, unless I’m intentionally doing something in the background, or it’s running one of the apps I’ve decided I want running in the background. It’s a bit of a revelation to use a phone whose battery life I don’t have to worry about, at all – in that regard, it’s more like having an iPad Nano than an iPhone. The iPad is a device I use every day without concern for the battery – and my phone now falls squarely in that same category. Until recently, I never would have thought that possible.

I’m not going to pretend there aren’t Android phones which, under the right conditions, would provide me the same results – I’m sure those Android phones exist. The problem is deeper than that: after owning three Android phones, and an Android tablet, I simply don’t trust Android to manage my phone’s battery life anymore.  Given how I use my devices, I fear that buying an Android phone with a bigger battery would just be a bandaid over the larger problem of Android’s battery management. As long as a background app or process has the ability to wake my device and keep it awake, I will always have reason to doubt my phone’s reliability – and at this point,  that’s an unacceptable scenario.  I don’t own technology to babysit it; I own technology to use it.

Reliability is really what the iPhone 6 Plus is all about. It’s a boring answer, but for many of us, it’s also the only answer that matters. Vlad Savov explained why the iPhone’s camera is still the camera to beat better than I ever could, but it boils down to this: I can take my phone out, snap a random photo, and, 99% of the time, get reliable, in-focus results.  I don’t even get that kind of reliability from my point-and-shoot, the fantastic Sony RX100M2.  Obviously the image quality and shooting capabilities of the Sony camera are still far superior, and the camera still comes along to more important events, but I no longer feel the need to dual-wield a phone and a point and shoot on a day-to-day basis.  On my Android phones, and to a lesser extent on my point-and-shoot, I rely on burst mode shots to make sure at least one will be in focus. I haven’t felt the need to do that with the iPhone; I only use burst mode for capturing motion or trying to get a very specific moment in time. I can hold the iPhone in one shaky hand, take a single photo, and, almost every time, it still comes through completely focused. I took a little video to demonstrate:

Photos from the sample video:

2015-01-13 20.35.22 2015-01-13 20.35.23 2015-01-13 20.35.24 2015-01-13 20.35.25 2015-01-13 20.35.27

It’s frustrating because no Android OEM has managed to replicate whatever software algorithms Apple has – there’s certainly nothing special about the hardware optics, so it has to be done in the software. I imagine it’s quickly taking a bunch of photos when you hit the shutter key and either using that data to piece together an in-focus shot, or choosing the most in-focus of the ones it took, or some combination of those techniques. I honestly thought the iPhone’s camera abilities were exaggerated until I started using one again – but now, I am a believer, and it will be hard to settle for anything less.

It feels like a shame to talk about the iPhone 6 Plus without at least mentioning TouchID. I’d had some experience with it on the iPad Air, so I mostly knew what to expect, and I can’t really add much to what others have said.  Personally, it’s hard to imagine going back to a phone that doesn’t allow me to secure my device in such a way – I put my thumb on the home button, push it down to wake up the device, and it unlocks almost instantly:

2015-01-13 21.17.04 (1)

Trusted Devices on Android is good, but TouchID is fantastic, especially now that third-party apps can leverage it. Paying for apps in the App Store, logging into the Amazon app, opening the Mint and Alarm.com app, paying for stuff at NFC terminals – all secured with TouchID.  Speaking of payment – Apple Pay is probably worth its own post at some point, but man, it is good. I used Google Wallet in the past, but Apple Pay definitely has the advantage when it comes to implementation. I simply point the top of my phone at an NFC terminal, an image of my credit card appears, I put my thumb on the TouchID sensor, and it’s done. This is the future, folks – and it’s kind-of neat.

So, does all of this mean I’m “switching” to iOS? Technically, yes, I guess, but I don’t really like the term “switching”, or the connotations that come with it. I’ve opted to use an iPhone as my daily driver for the foreseeable future simply because, at this moment in time, it’s the best device for my needs. A few years ago, Apple and I diverged – their phones weren’t big enough and the OS wasn’t flexible or interesting enough. Today, enough has changed that using an iPhone again just makes sense for me. I no longer feel like I’m making a major compromise when it comes to software or hardware, and the benefits – incredibly reliable all-day battery life and a best-in-class camera – are impossible to ignore.

I hope this isn’t a permanent change. I enjoy having a foot in the iOS world and the Android world, as I feel it forces me to broaden my perspective, both as a tech enthusiast, and with regards to the services I choose to use. Eventually, I hope to see an Android device released that, like the HTC One X before it, offers enough of an advantage over the iPhone that I can’t resist it.

Today, I am an iPhone user again. Tomorrow? I don’t know what I’ll be, but I can’t wait to find out – and that’s why I find the tech world such an exciting place.

Retailers are disabling Apple Pay and Google Wallet to push their own terrible payment system

The Verge writes:

…a significant number of merchants, including heavyweights like Walmart, Kmart, 7-Eleven, and Best Buy, are in outright competition with Apple Pay. The retailers, through a joint venture formed in 2012, are building their own mobile payment app, called CurrentC. It’s expected to launch next year. In the meantime, these retailers have no intention to support Apple Pay.

Hooray! A whole new set of mobile payment standards.  And you know what they say about standards.

Meanwhile, not a single bank backs CurrentC. That’s because the system is designed to cut out the middleman — and credit card processing fees. The app, when it launches next year, won’t replace your plastic credit card. Instead, it will withdraw directly from your checking account when you pay at the cash register with a QR code displayed on your Android or iOS device.

Okay, two things:

  1. Why the fuck would I want to give these retailers direct access to my checking account, especially after the number of stories about POS system hacking in the last year?
  2. QR codes?  Fucking QR codesAre you serious?  Was this system devised in 2006?  (answer: probably)

I don’t expect everyone to welcome Apple with open arms just because they finally jumped on the NFC mobile payments train, but can’t we at least all agree that having NFC readers that charge our credit cards is infinitely better than using QR codes to directly withdraw money from our checking accounts?  I want as many barriers between my money and these security-backwards retailers as possible; the last thing I want is the only barrier between them and my money to be a glorified bar code.

Apple Watch, Apple Pay, iPhone 6 Announcement Thoughtstream

  • Cool work with that livestream, Apple.  Love the way it keeps cutting off.  Hope you aren’t going to brag too much about your cloud services today…
  • Whelp, guess I’m reading live blogs instead. Way less exciting this way. Way to ruin the mood out of the gate, Apple.
  • Holy shit this is the fastest event ever. They must have a lot to talk about.  I bet this would be way more exciting with a functional live stream.
  • iPhone 6 and iPhone 6 Plus.  Look just like the leaks.  I would’ve gone with iPhone 6 Pro, but eh.
  • “Retina HD” is one way to name something, I guess.
  • 1080p resolution for the 5 inch – interesting.  That’s lower than the guesses made by Gruber.
  • The live stream is working!  And now there’s a Chinese translation over it, because reasons.
  • Okay, that “Reachability” feature looks like something out of Samsung’s playbook.  Or even something Samsung would’ve rejected.  Gross.
  • I’m actually pretty excited by the motion co-processor stuff, especially if it really can differentiate between running and biking. No exercise tracker has nailed that yet.
  • Still 8MP, but I’d argue that’s all you need for a good camera phone.
  • With that camera bump, I really expected OIS.
  • Ah, there it is…but only on the Plus. Shame.
  • Burst Selfies. Yup, that’s what the world needed.
  • iOS8 is still pretty great…and that’s about as much time as Apple spent on it, too
  • Apple finally bumped up the storage in their models, though of course they couldn’t bother to put 32 GB in the $199 model. Because margins.
  • 40 minutes for the new iPhones. That’s a lot of time for whatever is left.
  • I wonder if Apple will talk about wireless payments without even mentioning NFC.
  • If Apple fails at mobile payments, I feel like it’s probably dead for a long time. Hope they get this right.
  • Oh, I was wrong. They actually mentioned NFC.
  • If nothing else, maybe this will get NFC-based mobile payments into more places, regardless of payment platform.
  • Oh wow, an actual “One More Thing…”  Here we go.
  • Apple’s making a watch?! No way!  Said no one, ever.
  • Wow, is it really just a square smartwatch?  Hope there’s more to it, because right now this looks like an Android Wear watch for iPhones.
  • Lots of customization though, so that’s neat.
  • I love how this is getting a standing ovation before we even know what it does.
  • I really don’t see how this is any more acceptable to wear in public than existing smartwatches.
  • So…what’s the battery life?
  • Not always on. Responds to wrist-raise.  Strange that it turns “on” to the home screen and not the watch face, though.
  • I…don’t know about this.  This looks like an iPhone on your wrist, rather than a companion to said phone.
  • I’m starting to think this thing doesn’t have a touchscreen.
  • Ah, there it is.
  • Looks like the exercise tracking stuff isn’t really much more advanced than something like the Moto 360.  That’s a shame.
  • Wireless charging on an Apple device. That’s always good.  Wonder if it’s Qi, or something proprietary.
  • Multiple sizes is good. More companies need to get on that.
  • So much for the claims that Apple would unveil something that changes the entire way people think about wrist wearables.  It’s very pretty, but it’s not a game-changer – it just means the game is truly afoot in the wearable race.
  • This looks way more like a Galaxy Gear than I’d be comfortable with, if I was Apple.
  • These apps are cool, but it’s like it does too much – I don’t wear a smartwatch to use tiny apps.
  • Did people seriously just applaud canned responses to text messages? At least it does have a voice dictation option.
  • Siri on the watch.  Table stakes for the watch game at this point, but still good to see.
  • “Being active is one of the best things you can do to improve your health”…gee, you think?
  • To be fair, this is exactly what I want out of a wearable – smartwatch + exercise tracker + microphone – but it requires an iPhone, which makes it an iffy proposition.  I’m excited to use a Moto 360 to see how decent its heart rate tracking and step tracking are.
  • I mean, it’s basically the iPod Nano on your wrist that so many people wanted.  I’m sure it’ll sell amazingly.  I just don’t know if it’s for me.
  • A basic amount of backwards compatibility down through the iPhone 5 gets applause.  I guess I expected that at bare minimum.
  • Really? “Inductive wireless charging is something only Apple can do”?  *looks over at his wireless charging Nexus 5*.  Fuck off.
  • Using the ease of charging as a way to redirect from likely issues with battery life.  A day at most seems likely.  Probably a bit better than the Moto 360, but behind other Android Wear watches.
  • I love how Apple’s making it look like their charging solution is amazing and innovative, despite the 360’s being better.
  • Early next year – saw that coming.  Not in time for Christmas, so that’s a big miss.
  • Apple Pay works with Apple Watch.  Obviously, but still good.
  • $350.  Not bad. Less than expected, but more than Android Wear competitors.

Overall…I think I’m sticking with Android, for now.  I was relying on the Apple Watch to push me over the edge back into Apple ecosystem, but it’s just not quite enough at this point. Also, seriously, fuck that “Reachability” mode.  What is Apple thinking?

Copyright © 2024 writing about tech

Theme by Anders NorenUp ↑