Olio – Did the Cat Finally Build a Smarter Mouse Trap?

Contestant number five has entered the ring…

olio

One of the bigger things to hit the market this year is wearables. Things like Microsoft Band (part two of the review can be seen here), the Fitbit Surge, the Apple Watch (review pending arrival of the hardware), Pebble Time and Time Steel are all wearables – specifically smartwatches – that will have been released or will be released later this year. As of the first of this month (yes, April 1st; but no, this isn’t a joke), a new player has thrown their hat into the ring – meet the Olio Model One.

The device…? Oh my stars and garters, yes! Have you seen this thing?!

The Model One is beautiful. It’s made of stainless steel and basically comes in two flavors – (brushed?) Stainless Steel and Black. And while it is DEFINITELY drool-worthy, it’s got a few hurdles to get past.

The device itself runs on a proprietary OS

According to Olio, people spend WAY too much time in their computers, in their smartphones and tablets and shortly, in their smartwatches… that are tethered and tied to their smartphones. Olio wants their users to think of the Model One as an extension of themselves and not something that drives them or makes them live in it. As such, there’s no app store to bury you in apps. You get what you’re given (at least initially).

While the device obtains connectivity via both Android and iOS wireless devices, there aren’t any apps for you to run on the watch other than the ones that come with the device. While it does have an “assistant” of sorts, called Olio Assist, providing time saving suggestions, the limited – but value-added – functionality of (just) what comes out of the box, is where Olio sees the Model One hitting the sweet spot. You don’t get lost or waste hours of time playing Flappy Bird (or one of its many device based, or online clones). Instead, you focus on the information you need and only the information you need, so you spend time instead to your family, friends and loved ones.

However, most of the world wants apps. Its why we buy smart devices, and without an app store or a market (more on that, below), you have to wonder what the draw will be? Yeah it looks GREAT; and people at Tech Crunch, The Verge, and Gizmodo, all think saving you from “notification hell” is the bomb; and maybe it is.

Maybe it is….

I know that it drove me a bit nuts with the Microsoft Band, and it didn’t work right on the Surge; but when things are configurable, as they are on Band (and are supposed to be on the Surge), then you have to think a bit more about the purchase. For example, there aren’t any apps or even an app store for Band, either… (and its $400 cheaper).

And by the way, there’s no fitness band functionality here that I can see. This is a smartwatch and not a smartwatch that also measures physical activity. It doesn’t have any activity sensors, a GPS, a accelerometer, or a gyroscope. The functionality appears limited at this time.

It’s Expensive
Yeah… let’s talk about that for a sec.

While Microsoft Band is clearly affordable at $199.99, the Olio Model One is $345 – $395 for the Steel flavor and $495 – $545 for the Black flavor as of this writing with the $250 “friends and family” discount that’s being extended to the public. Normally, we’re talking $595 – $645 for Steel and $745 – $795 for Black (which puts their metal link bracelets at around $50 bucks over their leather bands).

The Olio Model One runs in the same neighborhood as the Apple Watch and Apple Watch Sport. The pricing models may be very different, but their close enough to be similar. You can clearly get a decent and high end analog watch for about as much AND get the band you want, too.

The device has a stainless steel case and an ion exchange glass touch screen that is supposed to survive impacts and resist scratches. It has wireless charging with a battery that can last a full two days with full functionality and then an additional two days, if you turn off connectivity to its Bluetooth-LE radio. The Model One can communicate with both Siri and Google Now via Olio Assist; and can control third party smart devices like thermostats and lights. It’s also water resistant so you don’t have to worry about ruining it when you take a swim.

The Model One is clearly a premium product; and maybe all of this is worth the premium price to you. I’m skeptical at best, at least until I have it in my hands.

It’s got an Initial Production Run of Just 1000
The Model One is a limited edition device.

Other companies release things in “limited edition,” and then they really aren’t limited at all. Olio’s first run of the Model One is limited to 1000 units – Five hundred of each the Steel and Black flavors. According to Olio,

“We decided to do a very limited production for its first release because the company is committed to the quality and craftsmanship and wanted to make sure that every piece holds up the high standards of the company. Olio compares themselves to a craft brewery, and aren’t trying to be everything to everyone.”

Olio likens itself to a craft beer brewery. Brian Ruben from ReadWrite.com said it best, I think. “if I buy a six-pack of a craft brew and I don’t like what I drink, I’m not out $600. Plus, I don’t have to call tech support.”

While the limited run and the high price are, I think, partial marketing tools to help create hype (as well as tech coverage by a number of different outlets, including yours truly and Soft32, at the end of the day you have to wonder how viable a company with such a limited production run with such a high end product will be. Olio appears to be artificially creating a limited supply in order to make the device’s value appear higher. Things that are rare ARE considered more valuable.

Diamonds, like the Hope Diamond, with such a highly desired cut, level of clarity and precision cut ARE rare and ARE very valuable. Olio hopes that watch aficionados see the Model One in the same light and don’t ding it for its digital guts as they do with nearly every other smartwatch; and with nothing really to compare it to (the Apple Watch isn’t even available for pre-order as of this writing, and hasn’t hit the market with either a splash or a thud…), it’s hard to see how well or how poorly the Olio Model One will do.

Have you seen the Olio Model One? Does it interest you? Will you buy one? Stay tuned to Soft32 as 2015 truly does appear to be the Year of Wearables. I’ll have more coverage on devices as they are released or as they make news.

In the meantime, if you have any questions, please let me know in the comments and discussion area, below.

Related Posts:

FEATURE REVIEW – Fitbit Surge

The next item up for review in our smartwatch round-up is the Fitbit Surge. Let’s take a look…

Untitled

Introduction

My quest to stop being a fat slob continues.

What to do, how much of it to do and what else I need to do to keep myself healthy is a never ending battle… and its not easy. There are way too many different daily challenges that present themselves.  Am I moving enough?  Am I eating right?  Am I sleeping right? These questions are difficult to answer as it is, and Fitbit has been trying to help people answer it for more than a few years now.

Their latest foray into fitness band/ smartwatch arena is the Fitbit Surge. It has a few nice things to offer not only the fitness conscious, but the smartwatch curious as well; and in this article, we’ll be taking a look at its suitability in both arenas.

This is the second review in a series – or round up – of smartwatch reviews that I’m doing.  The first on the Microsoft Band was large and in depth enough for me to break it up into two parts. You can see them here and here.  Its good and certainly worthy of more than a casual look.

My review of the Fitbit Surge is likely going to be just as lengthy and just as in depth. I’m going to pick apart the hardware. I’m going to pick apart the software. Smartwatches aren’t cheap. The Microsoft Band is $199… IF you can find one to buy.  I’ll cover the cost of the Fitbit a bit later, but I will say that it isn’t cheap, either.

Is the Fitbit Surge the right smartwatch and fitness band for you? Let’s stop dawdling and get down to it!

Hardware

Like the Microsoft Band, the Fitbit Surge is a single piece of hardware.  It has a wide, silicone/ rubber band with a traditional, aluminum alloy buckle.  Its much easier to wear than the Microsoft Band, as there’s a great deal of give and flexibility in the Fitbit’s rubber band.  Aside from the same kind of issues that you might find in wearing any other sports watch, band or bracelet made of silicone or rubber – where you sweat a great deal and your skin may become irritated due to a lack of exposure to air – the Fitbit wears the way you would expect a sports watch to wear.  Honestly, I was very pleased with the way it felt while it was on. The only comfort issues I had were related to breathabiltity.

Wearability and Usability

I’ve been wearing the Fitbit Surge for quite some time now – well over six weeks.  The device is easy to wear and its very comfortable.  However, there are a few things about it that I am not too crazy about.  Part of that is esthetics, part of that is design and while the device is comfortable to wear, it does have Wearability issues.

 The first thing that I noticed about it is that its BIG, even the small sized Surge is big.  The device comes in 3 sizes, small, large and extra-large.  However, size doesn’t relate to device size, it relates to band length and the size wrists it fits. The device itself is 1.34″ wide (34mm) and the screen is 0.82″ x 0.96″ (21mm x 24mm).

 Here are the sizing requirements, direct from Fitbit:

    • Small fits wrists that are 5.5″ x 6.3″ (13.94cm x 16.00cm) in diameter.
    • Large fits wrists that are 6.3″ x 7.8″ (16.00cm x 19.81cm) in diameter.
  • X-Large fits wrists that are 7.8″ x 8.9″ (19.81cm x 220.61cm) in diameter.X-Large is available as an online only purchase.

There are a couple of gotchas here that you need to be aware of.  While they aren’t mission critical, they are important to be aware of so that you can deal with the issues they present.

  1. The wrist band is made of silicone or rubber
    Wearing a silicone band in and of itself isn’t bad, unless you’re allergic to the rubber.  Even if you aren’t allergic to it, you need to make certain you spend some time with the band off.  Silicone can often cause rashes and other skin irritation, and its important that you spend at least some inactive time during the day with the band off, especially if you start to notice any dry, red or flakey skin, or if you start to have some other sort of skin reaction to prolonged wear of the device.
  2. The device, though flexible is bulky
    While the band in and of itself is flexible, the actual Surge itself, is stiff and bulky. The Surge is much more comfortable to wear than the Microsoft Band but the actual electronics of the device go out a bit farther than you might think.  Its clear that Fitbit have created a device that’s very compact, but if you look at it from the side and feel around the ends of band near the actual device FOR the device, you’ll see that its actually a lot bigger than just the screen.

The device itself is, well… ugly.

I hate to say it, but it is.  It’s a lot bulkier than it first appears or seems and its one piece construction means that you don’t have any kind of style choices with it.  Other Fitbit devices like the Apple Watch and even the Fitbit Flex have interchangeable bands. The Surge is a single piece unit, and… right now… you can have ANY color you want… as long as its black.  It’s the only color currently available.  The Surge is supposed to be available in blue and tangerine, but as of this writing, both are currently – still – unavailable. I’ve had my Surge for about two months or so. It was announced at CES and black was the only color available then.  You would think by now – or at least, I did – that the other two colors – which, quite honestly, aren’t all that attractive either – would be available by now.

However, don’t expect to be able to change bands. Unlike the Apple Watch or even the Fitbit Flex, this is an all in one unit, and you’d better be happy with the color choice(s) you make. Once you buy the device, its yours to keep; and there’s no way to change colors or change bands. What you buy is all that you get.

Notifications

If the Microsoft Band got notifications right, the Fitbit Surge doesn’t even come close.  On the Band, it was very easy to overdo notifications, as you could choose to have ALL of your notifications from your phone come over to Band, or you could choose specific ones that it does and keep the vibrations down to a dull roar.

With the Fitbit Surge, its exactly the opposite. You have just a single on-off setting for notifications on the device and then you get only notification of incoming text messages or incoming phone calls.

That’s it.

That can be good or bad, depending on what you’re looking for Surge to do.  If all you’re looking for is basic notifications from incoming messaging, you may be in luck.  As I said, the only notifications that the Fitbit Surge picks up are text messages and incoming phone calls.  If you’re looking to get notifications from upcoming appointments, Facebook Messenger or some other app on your phone, you’re out of luck.

The other big problem I have with notifications on the Fitbit Surge, is that the device doesn’t seem to understand or know when I don’t want them, or want them to stop.  I had notifications turned on for a while on the Fitbit, but have recently turned them off, as I didn’t need BOTH it AND the Microsoft Band buzzing my wrists every time my iPhone received a message, a phone call, or some other event occurred.

So, as I said, I turned notifications off on both bands.  Interestingly enough, Notifications on the Surge are still occasionally received, even though they are clearly turned off on the watch. I have no idea why. This is clearly a huge bug, as there shouldn’t be any notifications coming over at all.

However it clearly shows that the device’s software is capturing the notification and broadcasting the data. It clearly shows that the watch is receiving it through the Bluetooth partnership created on the device, even though its not supposed to be collecting ANY data at all. I’m seeing issues on both ends of the pairing; and its problematic at best. The fix for this – and it definitely needs to be addressed – will likely involve both a software update on your smartphone as well as a firmware update to the device.

UPDATE – The more that I wear the Fitbit Surge, the more I continue to have issues and problems with Notifications coming to it when they are clearly turned off on the device.  While the device does not alert that any text messages have come it, they are clearly coming across and they should not.

Period.

This is an issue that needs to be resolved immediately.

Battery Life

Battery life on the Fitbit Surge is actually pretty good. Compared to the Micrsoft Band, though, nearly ANYTHING would have better battery life… Well, not everything… the Apple Watch won’t last longer than 18 hours. The Micrsoft Band lasts 36 to 48 hours (even if you have Bluetooth turned off and sync via the USB cable).

The Fitbit Surge on the other hand, will last the better part of a week, even with all of the stuff that it does and all of the activities it tracks. Since the Surge tracks nearly everything you do, including sleep, the best thing to do when you do have to charge it is to charge it when you know you’re going to be inactive, or when you can’t wear it.  Swimming and showering come to mind as good candidate times when you might want to charge your Surge.  While the device is DEFINITELY water resistant, I wouldn’t hold it under water for long periods of time. Its not a perfect world, and my luck would have it getting water damage.

The biggest problem that I’ve found with the Surge is that it doesn’t give you a lot of warning when the battery is low, and you might find yourself out and about when you DO get a low battery warning. I’ve actually had mine die on me a time or two because I didn’t get an early enough warning that the battery was level was low.

Connectivity

The Fitbit Surge uses Bluetooth 4.0 to connect to your smartphone. I’ve found that while there are there are issues with this on other devices, the Surge specifically doesn’t use Bluetooth LE. I’m not certain if that’s why there are less connectivity issues with it as opposed to the Pebble Steel and Microsoft Band that I currently own.  Perhaps it is, and points to some larger issues with BT-LE devices.

What I can say about the Fitbit Surge is that while its connection to my iPhone 6 is much more stable, it isn’t as reactive or responsive as other devices are.  When implemented correctly, BT-LE devices tend to see their paired counterparts better and will actively connect when in range (though there’s even issues with this, as you can see in my article), as opposed to devices that do not pair with a BT-LE profile.

While I have less connectivity issues with my Surge, and while the battery life is decent even with its Bluetooth radio on all the time, I have found that data doesn’t come across the pairing unless the application is open and active. This means that I need to be actively using the app for the sync to work and pull data over.  Leaving it run in the background doesn’t do much… at least not consistently. I see this more as a Bluetooth issue rather than an issue with the Surge.

When you pair your Fitbit Surge with your smartphone, you’re going to see two connection partnerships – one for the Surge and one for Surge (Classic). The connection for the Surge is the one that you’d expect to see, and the one that is responsible for all of the connectivity and communication between the device and your smartphone.  If you want to use your Surge to control music playback, you need to enable Bluetooth Classic in the Settings app on the watch. After your Surge and your smartphone are paired, you can use it to control music playback.

To do so, open up a music app on your smartphone.  Then, double tap the home (left side) button on the Surge.  This will bring up the music control app on its display.  You will see your Surge attempting to connect via the (Classic) pairing, and then the current song’s meta data should appear on the watch face’s display.  You can pause the current song’s playback or skip to the next track. Unfortunately, not all music apps broadcast track information, which means that when using apps that don’t do that, the song title won’t appear on your Surge. However, you can still pause or skip to the next track.

I can see where this might be a great tool for someone who is exercising to NOT have to pull out their phone to control their playlist. Depending on where you have your phone stashed (not everyone fancies or trusts an armband case…), you may have to break your stride or stop exercising all together to retrieve and return your phone to its original place of storage.

However, I’ve tried this, and while its easier than pulling a phone from a shirt or pants pocket while running or walking, it isn’t totally a walk in the park, either. You’re going to need to get used to the interface and controls. You can pause, play, and skip songs. You’re going to have to pull your phone out if you’ want to repeat or replay any tracks or if you want to change playlists, midflight.

If you wear glasses for reading, you may have issues reading the audio file’s metadata, provided that your music app of choice transmits that information, on the Surge’s screen. While this isn’t a deal breaker, you do need to be aware of its limitations. Its hard to handle all of the varied functionality with only three buttons; AND to do it while you’re moving, too.

UPDATE – While writing this review of the Fitbit Surge, I’ve had it synching to my iPhone. Over the past few weeks, I’ve started to notice a few issues with Bluetooth connectivity between them both. They always seemed to work and play well together.

Right now, they are not; and NOTHING has changed on either end to warrant the issue in their pairing.  They just seem to not be looking at each other right now unless I absolutely tell them to get together. This is problematic at best, as when I started my Fitbit Surge journey, getting these two together was the easiest paring I’ve ever seen.  It just worked… straight out of the box.  Now, its like they love each other, but their not “in” love.

 Really..?

This is yet another reason why I think that while Bluetooth offers a LOT of potential, it has REAL issues as a data communications and transmission technology and conduit.

Software and Interfaces

I’ll get into Fitbit’s smartphone software in a minute, but I have to say something here, that’s bothered me since I started wearing the Surge – The information that it tracks and collects isn’t stored in Apple Health. Its stored in Fitbit’s proprietary program.  The app doesn’t share or swap data with Apple Health, and it really seems like it should. Some of what it does can’t be done in Apple Health, and that’s fine, but there really should be a way to have data from your iPhone and the data from you’re the Surge work and play well together, especially where Fitbit falls short.

Next Page

Related Posts:

My Bluetooth has Cavities

Sometimes, I really wonder why I use so many Bluetooth devices…

bluetoothApple has just released iOS 8.3 Beta 1 to its developer partners. The big push behind iOS 8.3? – Wireless CarPlay connectivity. This is a change to CarPlay, which previously required a cabled, lightning connection to a head unit to function.

CarPlay and iOS 8.3 are obviously going to rely more heavily on Bluetooth Low Energy connections going forward. For me – and I think, a number of actual and potential CarPlay users – this is likely going to prove to be a huge headache.

I’ve got a Pebble Steel, Microsoft Band and a Fitbit Surge. These three smartwatches and activity bands all use BT-LE to communicate with my smartphone – currently an iPhone 6 running iOS 8.1.3. I’ve been experiencing some very serious challenges with Bluetooth connectivity over the last number of years and I’ve come to a very clear and solid conclusion:

Bluetooth just plain sucks.

I’ve had more dropped connections, failed connections, and difficulty pairing devices than I think ANYONE should have to put up with. The technology is supposed to be active seeking, meaning than its supposed to actively find paired devices and when it does find them, activate secured communications between devices that are paired and hold and maintain that connection as long as the two devices are in range.

The problem that I run into, with my:

  • iPhone 6
  • Pebble Steel
  • Microsoft Band
  • Fitbit Surge
  • Kenwood BT952HD Car Stereo
  • Beats Wireless Headset
  • MacBook Pro
  • Apple Magic Mouse
  • iPad 1

and any other wireless device that I’m forgetting to list is that none of them…

NONE

OF

THEM

can maintain any kind of consistent level of Bluetooth connectivity between any of the devices that they’re paired to on a consistent basis. Devices always fail to sync at some point. Active connections are dropped (like, I’m on a phone call in the car and the call I’m actively on drops off the car stereo, but the call itself is still connected to my iPhone; and this happens WHILE I’m driving) without any kind of warning or indication of communications problem.

Paired devices often refuse to connect, requiring Bluetooth radios in either one, the other, or both devices to be turned off for 15-30 seconds and then cycled back on before formerly paired devices may connect. In some severe cases, partnerships have had to be deleted and devices repaired, because no amount of trying, begging, pleading, bargaining or cajoling has gotten them to connect (and then even repairing the devices can be difficult…)

Mercedes-Benz at the Geneva International Auto Show 2014

This is why I was so very interested in CarPlay in my vehicle. It REQUIRED a cabled connection, meaning that I wouldn’t have to argue with the head unit and my iPhone and their potentially fickle relationship any more. The devices would connect when the phone was plugged into the cable, and that would be the end of that. As long as CarPlay continues to support hard wired connections, then I think it will be a good solution for hands free operation in a vehicle. The moment that it moves to wireless communications only, is the day that I think the standard will begin to have some serious problems.

What’s even more infuriating is that they stop and start working seemingly at random and completely on their own. I have no idea at times whether or not the devices I assume are connected are in fact… CONNECTED.

But can someone please help me understand what I’m supposed to do here??

Can someone point me to some sort of “wireless crazy glue” that will insure that Bluetooth connections work as their intended all the time? I know I can’t be the only person having this kind of problem. I’ve learned over time that I can’t just assume that paired devices will connect when they’re supposed to and/ or will stay connected as they’re supposed to when the devices come in range. At best, this is a hit and miss sorta deal, and honestly, Bluetooth needs to be better than this.

When I rely on Bluetooth connections to connected and stay connected after pairing (as long as the devices are in range), this sort of hit and miss crap just can’t be tolerated. I can’t get any of the Continuity features between my Macs and my iPhone to work consistently. I can’t get any of my smartwatches or activity/ fitness bands to consistently sync with my smartphone. I can’t get my smartphone and my car radio to connect and work the way it’s supposed to.

How the heck am I supposed to rely on any of this stuff to work and “improve” my life if the connectivity technology – Bluetooth is full of “cavities?”

I have NO idea what to do…

Are you having issues with Bluetooth or Bluetooth LE? Do your devices drop connections like paparazzi drop names (and flash bulbs)? Do your mission critical Bluetooth applications – your car radio, your fitness band or smartwatch, your wireless headset, etc. – crap out on you when you need them most? Am I missing something that I should be doing, but for some reason am not? What words of wisdom can YOU offer ME? I’d love to hear your thoughts on the whole issue. Why don’t you meet me in the discussion area below and give me your thoughts on the whole ordeal? Lord knows… I could use the help!

Related Posts:

Convert videos for your Mac or favorite iDevice with MacX Video Converter Pro

Convert videos for your Mac or favorite iDevice with MacX Video Converter Pro

MVCP-01

One of the greatest things about modern computing is that the tools to create, transport and convert video – the kind that are of the quality that used to be available only to professionals – are now available to just about everyone. This is largely due to the fact that most of the hardware that common computer users now have access to, is professional grade. With that being the case, tools like MacX Video Converter Pro are a huge asset, as it provides professional processing with consumer level ease of use.

MacX Video Converter Pro is a general purpose Mac video converter that can convert video to any format. It supports MP4, H.264, MPEG, AVI, FLV, MOV, WMV, MP3, AAC, among others. It can also transfer supported HD video formats (AVCHD, M2TS, MKV) with flawless video quality. The app will also download YouTube videos. It will also record your screen, edit videos and allow you to make photo slideshows

The app supports a wide variety of formats and devices. You can convert video to and from iPhone 6/6 Plus, iPad Air 2/Air, iPad Mini 3/Mini with Retina, and Apple TV 3. The app supports files from iTunes and iMovie; and it will also support conversions to and from the HTC Desire 816, Galaxy S5 mini/S5, Galaxy Note 4/Edge, Galaxy Tab S, Amazon Kindle Fire HDX8.9, Google new Nexus 7, Surface Pro 3 as well as the Xperia Z1/ Z2/ Z3, and PS4.

MacX video Converter Pro is a decent desktop converter. Its interface is a bit disappointing to be honest, but its more than made of by the file formats and the the mobile devices it supports. The app works well with consumer based hardware, but is even better with high end hardware. The price is a bit on the high side for today’s desktop app market, but its performance is top notch. If you’re looking for a decent app that will not only download and convert YouTube video, but will also convert video to and from most of the popular mobile devices and video formats, you really will have a hard time finding a better app.

 

Download

 

Related Posts:

A Month or More with the iPhone 6

I’ve had the iPhone 6 since its original ship date back in September 2014. Let’s take a look at how things have gone so far…

Introduction

The release of the iPhone 6 is probably the biggest iDevice release in Apple’s history aside from the releases of both the original iPhone in 2007 and the original iPad in 2010. The iPhone 6 and its bigger cousin the iPhone 6 Plus are both evolutionary and revolutionary in the smartphone and phablet categories as they have brought both their 4.7″ and 5.5″ form factor sizes into the main stream, in my opinion. Before the iPhone 6 and iPhone 6 Plus, smartphones around 5″ or larger were exclusively an Android thing… and something that Apple enthusiasts could only dream about.

No… I’m not saying that Apple defined, redefined or was the first one to the market with these larger phablet sized devices. That honor is definitely in the Android side of the world; and I think HTC or Samsung was the first to this party back in like 2008 or so. There was an Android device on the Sprint network (I forget the device name); but at the time, everyone thought it was WAY too big.

Now with the iPhone in the larger screen category, everyone is interested in how the phone looks, works and functions with a larger display, as well as with some of its newer functionality and hardware. I’ve had an iPhone 6 since the day it was originally released to the public in late September of 2014. I did an unboxing the day it arrived, and you can watch it on my site, iTechGear at your convenience. However, let’s take a look at the iPhone 6 as it compares to the iPhone 5/5s and a couple of other phones in my current device stable and see how it stacks up again not only the competition, but past iterations of itself.

Form Factor & Display

Next to the conclusion in this article, I’ve chosen to write this section last. I’m telling you this because, well… you’d think that with the size of the device and its display being one of the bigger differentiators with the iPhone 6 and iPhone 6+ that I’d be rushing to talk about the device’s form factor and display.

No… not really; and there are a few, specific reasons as to why…

Device Size

First and foremost, I didn’t want the entire world to think that I’m too much of a fanboi. Yes… I *AM* a full Windows to Mac convert at home. I really DO prefer OS X to Windows for what I do at home, for me… which amounts to mostly multimedia consumption (audio and video) via iTunes as well as digital photography (at least, once you get past all of the writing and such…)

Secondly, the change in device size is perhaps the most noticeable thing about the device. Once people see that you’re running iOS on your smartphone, AND they see the size of the device, they almost always ask you

  1. If you’re using the iPhone 6 or 6+ (without the context of the OTHER device, most people are surprised at how big either device really is. It’s not until you have both new iDevices side by side that you realize just how big they are.)
  2. If they can compare the size of my device to the size of theirs

In the case of the iPhone 4/4s or iPhone 5/5s, both the iPhone 6 and 6+ are dramatically and noticeably bigger. The iPhone 6 makes the iPhone 4/4s look like a growth stunted, pigmy of a device. It’s clearly much larger, and as such, the device loses its classic and Apple-touted one handed usability, that is, unless you’re someone with hands like LeBron James. I don’t think he – or people of similar size and stature – would have trouble stretching their hands to any corner of the device. However, in most cases, having a 4.7″ or 5.5″ diagonal screen means that you’re going to need both hands to operate it in most settings and occasions. However, Apple has tried to compensate for that somewhat, and has included a double-tap action for the Touch-ID sensor that will bring the top of the screen down to the middle of the display, making it easier to get to items at the top.

I will say that I love the new size of the screen. It’s much nicer to have a larger screen, though I wouldn’t like to go (much) bigger than the 4.7″ of the iPhone 6. I have also got an HTC One (M8), and that has a 5.0″ display. You can see the difference in the extra 0.3″; but I don’t want to get any bigger than that.

The iPhone 6+, for example, is just too big for me. The extra 0.8″ larger display than the iPhone 6 and half inch (0.5″) larger display than the HTC One (M8) is just TOO big for me. I honestly wanted the iPhone 6+ after seeing the announcing keynote during WWDC; but after I put my hands on it in an AT&T Store…

Yeah, no. It’s just too big for me. It’s like holding a mini iPad Mini up to your head, and I don’t know that I’d be able to do that without a tin foil hat or something… (too much radiation from too large of a device).

So for me, the size is just right.

Device Profile

Oh my goodness the device is THIN!

In fact, it’s almost too thin. The iPhone 6 is 6.9mm thick. The iPhone 6+ is 7.1mm thick. Compared to the iPhone 5/5s at 7.6mm, you can really see and feel that the iPhone has “lost weight” and has a much thinner profile than before.

The biggest problem I have is not necessarily “bend gate.” I know that the device isn’t going to bend in my pocket. It’s just that I’m afraid that it will. I know… it’s completely irrational once you get beyond the conspiracy theory. So, I’ve got my iPhone 6 is a huge, ugly Otterbox Defender Series case. It’s nice, but it really more than doubles the thickness of the device. I like this case. It does a good job of protecting the device; but its ugly as sin, and really makes the device almost too big in and of itself. I’m looking for a thinner profile case that offers some decent protection, but I haven’t found one that doesn’t cost more than the $50 USD that I paid for the Otterbox Defender I got on iPhone 6 Day.

I love the profile of the iPhone 6. I truly do, but I’m afraid that I’m going to drop it; and that if I do, that I will break or fracture the screen without the right case around it.

Yes… it may be irrational, but have you seen photos of the device or have seen one up close? It’s totally beautiful. Speaking of pictures, I have the full 360, below.

Device Photos – The Full 360˚

Here, you’re going to see my iPhone 6 beside an iPhone 5, the HTC One (M8) (an Android 4.4.x device) and the iPhone 5.

DSC_1864

DSC_1866

DSC_1877

DSC_1869

DSC_1875

DSC_1870

next page

Related Posts:

iOS 8.0.2 Released to Resolve Cellular Issues

The QA Manager at Apple is having a really bad week…

I know I’ve said this before, but I’ve got 25 years in QA management. I know that Apple hires only the cream of the crop; but you have to wonder if after not one but two huge software bug blunders in the last two years if the guy running the QA ship at Apple is the right guy. It’s a reasonable question. And I’m certain that its something that is likely crossing the mind of EVERY member of Apple’s senior leadership team’s minds.

Earlier today (as of this writing), Apple released iOS 8.0.2 to resolve the issues with cellular connectivity and TouchID functionality. Specifically, the release provides the following improvements and bug fixes:

ios801

Unfortunately, the big issues around cellular connectivity and TouchID were tested by the same QA organization responsible for the same testing type of misstep that occurred with Apple Maps. That particular issue was enough to get Scott Forestall fired. However, it didn’t go much lower than that.

Now, a couple releases later, there’s another huge testing bungle hot on the heels of the iPhone 6 release and iOS 8. Funny how the same QA manager that blew Apple Maps also blew the testing on this particular release.

This was a big one; and from what I’ve read on Bloomberg, this guy has had a really crappy week.

iOS 8.0.1 was aimed at fixing issues from the iOS 8 GM release, and also introduced Apple’s health and fitness-tracking application HealthKit. Unfortunately, the update also disabled some people’s – and the estimates around “some” is around 40,000 – access to their cellular network so they couldn’t make or receive phone calls.

While some may try to make the story about the QA guy and the fact that he blew the testing on three huge bugs (Maps, TouchID and cellular connectivity), the issue shouldn’t necessarily be about what was missed, but how it was missed.

Apple does most of the right things the right way. Its clear from their sales, stock prices and consumer loyalty. I’m not entirely certain what went south with iOS 8.0.1, but I have a few ideas; and I’m going to offer them briefly with the hope that they will be taken constructively and not as deconstructive criticism.

While Apple ranks their bugs with an industry standard process, its said that their bug review meetings can get ugly. Engineers often argue for more time to fix a problem while product managers push to move the release forward. In the case of Apple Maps and iOS 8.0.1, too much risk was assumed by the product manager(s) in question. Its obvious that more time should have been given to issues in iOS 8.0.1 or the issues weren’t discovered until after the software was released.

The biggest issue that I’ve seen – IF it in fact proves to be accurate – is that software testers and engineers don’t get their hands on the latest iPhones until the actual release date. This is the biggest reason why there is normally a software update to iOS a week or two after the release of the device. Testing and Development get the latest hardware, install the OS, and then start poking around. Prior to that, QA and Dev team members either use existing hardware to test the new mobile OS, or run the new software in an emulator.

While this seems like a no brainer to resolve, the problem exists because of one word, really – Gizmodo. The leaked iPhone 4 hardware that got passed around is still giving Apple heartburn, nearly 5 years later, and as such, Tim Cook has limited use of unreleased hardware to only senior managers, unless special permission is granted. This makes testing difficult.

Internal turf wars also create issues as teams responsible for testing cellular and Wi-Fi connectivity will sometimes sign-off on a release too early, and then – as in the case of iOS 8.0.1 – connectivity or other compatibility issues are discovered. There tends to be a lot of finger pointing when things like this happen, and that’s never productive.

No matter how you slice it, there’s something very wrong with the way Apple’s SDLC (software development life cycle) is working. The in-fighting going on between development, testing and product management is leaking out of Apple’s nigh impenetrable walled garden and into the streets. It happened with Maps a couple years ago, and its happened again with iOS 8.0.1. While the fallout from the latest SNAFU won’t be nearly as big as it was with Maps, its toxic none the less, and needs to either be buried, or stop completely (the preferable outcome).

I’ve been in situations like this. Its hugely problematic, and hugely indicative of individuals that put themselves before the company…. and it never ends well, especially for individuals that are involved. The activity breaks down relationships, productivity and creates problems that kill opportunities to get future work done. It also breads additional problems, so the issues are circular.

This may go underground again; but then again, it may not. No matter how things are looked at, however, Apple has to make it stop.

Related Posts:

iPhone 6 First Impressions

I’ve had the iPhone 6 for a few days and here are my initial thoughts on the device

iphone-6

It happens every year since 2007. The world goes bat-stuff crazy when Apple announces and then releases a new iPhone or iDevice. Everyone that has the old one WANTS to get the new one. Not everyone that wants one can either afford to buy one or those that are, are lucky enough to get one on the actual launch day. This year, I was blessed enough to be both.

I’ve been playing with a space gray, iPhone 6 since the evening of 2014-09-19. I completed an unboxing for Soft32 that you can see on my site, iTechGear.org.

After working with the device for about five or so days, I have the following to share about the device.

Size and Form Factor

The iPhone 6 and 6 Plus is perhaps one of the thinnest smartphones I have ever put my hands on. While the 4.7″ screen size is perhaps the biggest – and most noticeable – of Apple’s new smartphone’s features, the device’s waist size is relevant news, especially after report after report of the device bending.

With the new design, the iPhone has departed from its four version, design stagnation (iPhone 4, iPhone 4s, iPhone 5, iPhone 5s). The iPhone 6/6 Plus is new. Its sexy. Its bigger, and its thinner. It provides the user with a whole new smartphone experience; or at least that is what Apple would have you believe; and its probably true.

In hand, either device is huge. While the 6 Plus is like holding an iPad mini to your head, the iPhone 6, while only slightly smaller, is still vastly larger than its predecessors. Over the past few days, I’ve found that holding the device is noticeable, especially after using the iPhone 5 over the past two years. However, its noticeably larger, and you know that you know that you’re using a much larger device.

The device is super sexy; but I wouldn’t use it without a case. I made this decision BEFORE hearing about all of the device bending stories and before seeing all of the pictures. As such, the day that I got my iPhone 6, I went to AT&T and bought an OtterBox Defender Series Case for my iPhone 6. I love the profile of the iPhone 6, but if smartphones get any thinner, they will definitely need to be able to bend or fold on purpose in order to prevent the device from being damaged.

You won’t want it to be in a case, but you’re GOING to need something to help protect the device. Its really a GREAT looking device; but while Apple has done a really great job of designing a technologically advanced, consumer friendly device, it may have gone too far in thinning it out.

The screen seems great, and iOS 8 provides a way to change the display resolution on the device to provide those with failing eyesight – like me – a way of changing the zoom level so that its easier to read. The setting is available on both the iPhone 6 and iPhone 6 Plus.

So far, I like the size change. The older form factor seems tiny by comparison. Thankfully, the larger device still fits in my Arkon Car Mount, allowing me to use the device with my hands free kit in my car.

I’ll have more on the device size and my use of it in my full review of the iPhone 6.

Battery

Over the past few days, there have been a number of reports on issues with battery life. I have on occasion experienced some of this. While the battery in the iPhone 6 is definitely bigger – you can tell its got a longer battery life – its clear that in some instances, it should last longer than it does.

Like many others, I connect my iPhone to my Pebble Steel, my car radio, my Nike Fuel Band, my Bluetooth headset, and of course, my MacBook Pro, among other devices. While many of these may be BT-LE compatible, and therefore don’t suck too much power, some of them aren’t. Interestingly enough, I don’t see Bluetooth being among the guilty parties in some of the power drains I’ve seen.

As with the iPhone 5 and earlier, most of the drain I’m seeing is coming from screen and processor/co-processor use. Yes. You can read that as gaming. Its also one of the biggest reasons why I really don’t do a lot of gaming on my iPhones. At the end of the day – literally…the end of the day – it doesn’t pay off.

On my iPhone 5, I could start the day with a full charge and after one session of Angry Birds Friends, where I went through all 6 levels for the week – perhaps, 30 minutes of play – my battery life would be down below 70%. I’m seeing similar performance with my iPhone 6.

Some games just suck battery life. You’re going to need to govern your game play and figure out which games are the biggest culprits. I’ll have more on battery life with my review.

iOS 8

I’ve written a lot on iOS 8 over the past few months. You can see my coverage on Soft32 over the past few months, here, here, here and here. The beta period wasn’t pretty. While the OS itself is showing some stability, the release of iOS 8.0.1, has been just as big a train wreck as the other pre-releases of the new mobile OS. Apple, like so many others, is cutting corners on quality; and when you have something like this, being this big, and this visible, you simply just can’t.

Releases of any mobile operating system need to be clean and as issue free as possible. As a software quality professional with over 25 years in quality, I can tell you that there will always be bugs. Always. You’re not going to get away from them. However, you need to make sure that the bugs that you are releasing with are known, of lower priority and severity, and that fixes are planned and coming. Releasing an update to your mobile operating system that disables all mobile, cellular communications and kills the device’s biometric security measures is certain evidence that your QA director isn’t watching where the ship is going. Defects of that severity and priority were easy to spot and should have prevented the release of the update.

I’ll have more on the device, including comparative photos of the iPhone 6 up against the iPhone 5, the HTC One (M8) and Lumia 520 that I have. If you have any specific questions on the device or on iOS 8, I’d be happy to address them in my review. Please feel free to leave your questions in the comments section, below.

Related Posts:

Apple Updates: Yosemite Developer Preview 8/ Public Beta 3

os-x-yosemiteI’m not going to go into too much detail here. I’ve covered this quite a bit so far. Suffice it to say, that while the OS in and of itself seems much more stable than it has in the past, I’m having issues again with Bluetooth and my new, iPhone 6, as I mentioned earlier.

Continuity is still cool, and most of it works well. However, it needs some work. This is something that really needs to get addressed and addressed well before the release of OS X 10.10 Yosemite. The whole thing with the integration between the desktop and the mobile only works if the connection between the two platforms is solid. Right now, its not. Apple still has work to do.

Conclusion
I’m going to make this short too. Everything that Apple has shown us in the past few days should be considered a work in progress. While the hardware for iPhone 6/6+ is finalized, things like Apple Pay have not been implemented yet and won’t be for a month or more as of this writing. There will likely be some software revisions that need to take place in order to enable all of the hardware functionality that is currently dormant and not used. Which brings us to iOS 8…

iOS 8, though also released, is definitely a work in progress. With everything that I have seen of it so far, it definitely feels as though the finishing touches on it were rushed. As apparently, was its latest update.

While finishing the conclusion section of this article, iOS 8.0.1 was released to help introduce support for HealthKit apps, provide Photo Library fixes, as well as fixes for third party keyboards, Reachability, etc. However it has some SERIOUS issues.

First and foremost among those include breaking cellular connectivity (your iDevice can’t connect to a cellular network, which makes your iPhone effectively…a door stop), and the inability for TouchID sensors in the 5s, 6 and 6 Plus to recognize or setup any new finger prints.

USERS ARE ADVISED TO NOT INSTALL iOS 8.0.1 until these issues can be addressed.

If you’re using OS X Yosemite, the OS is very usable. Its stable enough for daily use at this point, but if you’re looking for the finer points such as Continuity and Handoff to work as designed, you should understand that these also need work.

I’m in the process of working on my iPhone 6 review and I will have a first impressions document published in the coming days. Please stay tuned to Soft32 for all the updates!

go to Apple Updates : IOS 8 GM

Related Posts:

Stay in touch with Soft32

Soft32.com is a software free download website that provides:

121.218 programs and games that were downloaded 237.780.356 times by 402.775 members in our Soft32.com Community!

Get the latest software updates directly to your inbox

Find us on Facebook