Skip to main content

Samsung Gear Fit vs Apple Watch 2 - a review and comparison

Recently I was given an Apple Watch 2 - it's very nice and I've replaced my Samsung Gear Fit with it. After wearing the Watch for a week, there have been a few tangible differences between the two I thought it might be worth noting. If you're unfamiliar with the devices they look like this:


These images are the same as the devices that I have. The physical differences are obvious - the Apple Watch is significantly bigger, with the more square face. Both have OLED displays which make for bright, colourful GUIs. Both are touch screen and both share a variety of internal sensors like heart rate and accelerometer. The Gear Fit is lighter, narrower and for what I've used it for - holds a longer charge than the Apple Watch. The Apple Watch has many more sensors - including GPS/GLONASS and WiFi, checks your heart rate with great frequency daily and keeps telling me to "Breathe"! (this gets a bit annoying after a while)

Here are a few of the summary differences I've found in the last week (and please bear in mind I wore the Gear Fit for 2 years before replacing it).

  • The sleep function on the Gear Fit is much better than the Apple Watch - you have to get a 3rd party app for the Watch which I found annoying. It's built into the Gear Fit, mutes and blocks the device and gives you some nice reporting via the Samsung Health app. Also, access to the sleep function I found is better - put the Fit into sleep mode and it's ready to track your sleep, then give you a report in the morning when you turn it off. The Apple Watch - using the AutoSleep app, alleges that it can work out when you go to sleep and then when you get up via some sort of magic I assume. I'm still trying to figure out the meaning of the sleep reporting (which is irritating in and of itself).
  • The Watch hasn't locked up yet but the Gear Fit has twice in the last week. This is a full reboot, and lose all of your sleep data - something that happens with semi frequency on the Fit and is quite annoying.
  • Notifications are roughly the same through both - configurable and fairly useful. The ability to send detailed replies with the "Scribe" function (you use your finger to write each letter) on the Apple Watch is pretty neat - I've used that several times.
  • Both watches can answer the phone, or more likely - divert to message or voicemail. The Apple Watch you can actually talk into the watch and I've been on the receiving end of that a couple of times. It wasn't bad really, but I think you'd feel like a dill talking into your watch like Get Smart rather than use the phone.
  • the summary from the Samsung Fitness software is much better than what Apple Health provides (at least for me). I find the sleep data and the way its presented to be significantly better than the Apple information. The Samsung software tells you how often you got to bed on time, and how often you got up on time. I like that. It provides a small sense of accomplishment just for getting my lazy backside out of bed in time.
As a bit of an update to this review - it's been an extra week of using the Apple Watch and I'm still unimpressed by the sleep thing. I have set aside some time to look into this in greater depth because I feel it's so lacking. Keep an eye here for some more info. The alarm feature on the Apple Watch has been pretty good. The vibration on the wrist isn't startling to wake up to, and it doesn't disturb my wife (which she is happy about). 

In summary both of them are really quite good devices. They lock you into their respective ecosystems (Samsung vs Apple) and this is to be expected, potentially not loved though. For purpose, I think the Gear Fit was better for tracking sleep, better battery life and a robust device. The Apple Watch's aesthetics are lovely, it has a tonne of functionality and I've barely scratched the surface of it. I'll go into it more as I play with this thing a bit. It's easy to see where the extra value in the Apple Watch is.

Comments

Popular posts from this blog

Plone - the open source Content Management System - a review

One of my clients, a non-profit, has a lot of files on it's clients. They need a way to digitally store these files, securely and with availability for certain people. They also need these files to expire and be deleted after a given length of time - usually about 7 years. These were the parameters I was given to search for a Document Management System (DMS) or more commonly a Content Management System (CMS). There are quite a lot of them, but most are designed for front facing information delivery - that is, to write something, put it up for review, have it reviewed and then published. We do not want this data published ever - and some CMS's make that a bit tricky to manage. So at the end of the day, I looked into several CMS systems that looked like they could be useful. The first one to be reviewed was OpenKM ( www.openkm.com ). It looked OK, was open source which is preferable and seemed to have solid security and publishing options. Backing up the database and upgradin

Musings on System Administration

I was reading an article discussing forensic preparation for computer systems. Some of the stuff in there I knew the general theory of, but not the specifics of how to perform. As I thought about it, it occurred to me that Systems Administration is such a vast field. There is no way I can know all of this stuff. I made a list of the software and operating systems I currently manage. They include: - Windows Server 2003, Standard and Enterprise - Exchange 2003 - Windows XP - Windows Vista - Windows 2000 - Ubuntu Linux - OpenSuSE Linux - Mac OSX (10.3 and 10.4) - Solaris 8 - SQL 2005 - Various specialised software for the transport industry I have specific knowledge on some of this, broad knowledge on all of it, and always think "There's so much I *don't* know". It gets a bit down heartening sometimes. For one thing - I have no clue about SQL 2005 and I need to make it work with another bit of software. All complicated and nothing straightforward. Irritating doesn&

Traffic Monitoring using Ubuntu Linux, ntop, iftop and bridging

This is an update of an older post, as the utilities change, so has this concept of a cheap network spike - I use it to troubleshoot network issues, usually between a router and the network to understand what traffic is going where. The concept involves a transparent bridge between two network interface cards, and then looking at that traffic with a variety of tools to determine network traffic specifics. Most recently I used one to determine if a 4MB SDSL connection was saturated or not. It turned out the router was incorrectly configured and the connection had a maximum usage under 100Kb/s (!) At $1600 / month it's probably important to get this right - especially when the client was considering upgrading to a faster (and more expensive) link based on their DSL provider's advice. Hardware requirements: I'm using an old Dell Vostro desktop PC with a dual gigabit NIC in it - low profile and fits into the box nicely. Added a bit of extra RAM and a decent disk and that&