Crowd Funding Update

Back in August of last year I wrote an update on the status of the projects I have backed on Kickstarter and IndieGoGo. Eight months on, only one of the projects still ongoing has delivered: Parashoot. Lima and Lono are still promising to ship soon.

I also have a couple of projects not on either of the two platforms: Coin (which finally delivered this week, very late), and Nymi, a biometric authentication project (still to deliver, but different in that they won’t take the money until they ship, so really this is pre-ordering more than crowd funding).

In the meantime I have backed a few more projects:

The Egg

A personal web server gadget. This one was a little personal since I know one of the founders, but I’ve seen one of their early units and the project has some appealing features too, not least of which is the ability to share photos with friends & family without having to upload them to a public web service.

Expected delivery: September 2015

Pebble Time

This will be my third Pebble, and I upgraded the pledge to switch to the steel variant once they announced it. Not much more to say about this one.

Expected delivery: July 2015

Titanium Pens

A set of three (because I couldn’t decide on the finish I preferred & the set was a bargain compared to one or two pens). And, yes, these pens are going to ship without a refill. But they look gorgeous, and the guy behind the project already sells lots of titanium products directly from his site and clearly has a passion for this pen project. It has been incredibly over subscribed though – about 3600% more than the goal.

Expected delivery: July 2015

The Leaders Guide by Eric Ries

A new book project from Eric Ries (of lean startup fame) with lots of unlocked extras. 

Expected delivery: October 2015

Coin: The Card To Replace Them All

What seems like a very long time ago now, I signed up for a crowdfunded project called Coin. The literally credit sized (in all dimensions) sliver of electronics claimed to be able to pretend to be all of my credit cards, selecting the one I wanted being as simple as pressing a “button” on the card.

Well, this week my card finally arrived, much later than they had originally estimated, and after a much longer beta testing period (which I had signed up to be a part of, but was not selected for).

Setting up the card was mostly straightforward (I already had the app on my iPhone and the account set up since they sent instructions for doing that part a long time ago so we could track our order too).

Loading Cards

I had a small hiccup getting the cards sync’d onto the Coin, but once I worked out that the trick was to wait for the phone app to tell me to activate the card and get it into sync mode, it all went smoothly. At least for the two credit cards.

The Starbucks card I tried to load was another problem altogether. The Coin ships with a small card reader that plugs into the headphone/mic jack on the iPhone (similar to the original Square card readers). That is able to read credit cards easily, but when it came to reading my Starbucks card it took a few swipes to get it to read, and even then the number it read from the mag stripe didn’t match the number printed on the card. I have a support request open with Coin to see whether that is expected.

Continue reading

Smartwatch Thoughts

Black Pebble Time SteelWith what seems like my entire Twitter timeline getting excited about their new Apple Watches (arriving, one after the other today it seems), I thought it would be a good time to review some of my thoughts on smartwatches, and in particular why I have not pre-ordered an Apple Watch. In fact, not only have I not pre-ordered an Apple Watch, but I have “pre-ordered” (through their Kickstarter campaign) a new Pebble Time Steel watch.

What are the pros and cons of each in my opinion (and remember, that’s all this is – my opinion; you are welcome to disagree with me and choose whichever smartwatch works best for you, or even not get one at all).

Battery Life

This is the big one for me. I already charge way too many things every day (I carry multiple phones for work, typically an iPad and a laptop, and I also have a Nexus 7 and Kindle Fire and a pair of bluetooth headphones that I have to remember to keep charged). My Pebble and my Fitbit One are my best friends w.r.t. charging since they’re roughly once a week! Getting a 20% battery life warning on my current Pebble Steel doesn’t bother me – that’s still at least a day of normal use.

Less than 24 hours seems like a big miss to me. That means one more thing I need to find an overnight charging spot for. The new Pebble Time Steel claims up to 10 days with a colour screen. I just think that Apple could have pushed the technology here.

Overall Design

I think this one is actually a tie for the new Pebble Time Steel vs the Apple Watch (in fact, I’ve seen some photos that suggest they look pretty similar). Neither wows me as much as the Moto 360, but there are plenty of reasons why I am not interested in that family of smartwatches. I do have to concede that the circular design looks stunning though. I would have loved to see a rectangular and a circular design from Apple rather than just two rectangles in (barely – just 4mm) different sizes.

That said, my two existing Pebbles look fine to me, and more importantly don’t scream smartwatch to everybody. I wear my black Pebble steel every day and get very few comments about it. I ordered the new one in black too.

Continue reading

Ongoing Pebble Issues


Update: Check out my more recent update on my Pebble experiences too.

Anybody following along here will know that I have been having intermittent connection issues, as well as bluetooth audio interference issues, with my Pebble smartwatch. But more than that, I have been having issues with their customer support. Not to mention having their Chief Evangelist accuse me of whining, and then block me on Twitter. Great way to treat your customers. Guess she doesn’t want to actually hear from real users. 

On October 17, I was given this answer by one of their support folks:

We well received your logs, and will review them thoroughly and have a reply by Tuesday. Thanks for your patience.

That was a Friday. By the next Friday, October 24, I had still heard nothing other than another canned response on a different case number because I submitted more logs through their app and it generates a new case each time suggesting I upgrade to iOS 8.1 (which I had already done, and which has made no difference).

Continue reading

Apple Pay Experiences

image

Monday of this week saw iOS 8.1 land on Apple devices, and perhaps the most expected feature in the update was Apple Pay; the new NFC based, Touch ID approved payment service that was going to revolutionize how we pay for things. Or not, because of course NFC based payments have existed in Android phones for a while now, and even in plastic credit cards (mostly outside the US, but my Wells Fargo Visa card has both a chip and touch pay capabilities).

Continue reading

Pebble Issues

Pebble SteelAs one of the people who backed Pebble in their Kickstarter campaign, and somebody who subsequently upgraded to the Steel Pebble when it was launched, it saddens me to write this, but at this point I feel Pebble is going to find it hard to survive, and for two simple reasons: they don’t seem to care about software quality, nor their customers.

At a time when Google, Samsung and Apple are creating much more sophisticated smart watches, it would seem like a good idea for Pebble to keep its existing customers happy, and to take seriously any reports of problems. Instead, every problem I have reported has gone unaddressed (aside from some brush off suggestions that I un-pair/re-pair or restart the watch, reboot the phone etc). I would actually consider the hardware part to be fine, and despite not having all the bells & whistles of the others, it wins hands down on battery life (most of the time), and provides the essentials needed in a smart watch. But, the software is buggy, and the support experience is terrible, and without those aspects working well too, I don’t believe they will be able to compete.

Continue reading

Square, Coin and Smart Bank Cards

I read a blog post today from the folks at Square talking about how the more secure smart card enabled bank cards are coming to the US soon. That reminded me of my initial reaction to Square when it was first being hyped: “oh great, another magnetic stripe reader; can’t the US please move to something better.”

I first encountered embedded chips in my bank cards back in the early 1990s, in France – that is over 20 years ago. While my UK cards today still have the magnetic stripe (so they work in the US!), they also have chips and contactless touch pay capabilities.

When companies like Square, and more recently Coin, create technologies that are dependent on magnetic stripe technology I am amazed. It sounds like Square will be in a position to get new readers to their existing business customers. I don’t see how Coin will even survive if the US really can make significant progress in switching to chip & PIN technology next year (although I do have two cards now from US banks with the technology in them).

Continue reading

Preventing “Forgotten Baby” Deaths

Maybe being a father of a couple of young kids, one of whom is still riding in the rear facing infant car seat makes the recent stories of babies dying when they were accidentally left in the car all day when their parent (apparently most often their father) forgets to drop them at the day care in the morning worse, but it strikes me there ought to be something that technology can do to make this less likely. 

Low Tech Ideas

I read about the shoe trick the other day, and while it is clever, I don’t see it being foolproof. The one day you are rushing you will forget to place the shoe in the back too, and those are the most likely days you will forget the baby. Not to mention that it relies on you driving an automatic car. Those with a clutch pedal, will probably want to keep their left shoe on as well while driving.

Similar ideas exist using bags, or other items you are likely to remember, but realistically I think they all suffer from the same flaw, that they will be forgetten on the days when they are most needed.

I am also mystified why day care places don’t call to find out where their charges are when they don’t arrive on time and they haven’t been told not to expect them that day (I should actually check what my toddler’s preschool would do if he didn’t turn up and we hadn’t called to let them know).

Finally, for the low tech options, I read another suggestion that doesn’t rely on the day care place calling, but instead just has the parent who drops the kid off call (or I guess text if you prefer) their spouse to confirm the drop off. If the spouse doesn’t get the message at the expected time they can call to find out why.

A High Tech Idea

I have this little red low energy Bluetooth (BLE) device at home that is a demo/developer device for the Texas Instruments BLE chipset contained within it. This little gadget comes with a number of features that would be useful for building a baby seat alarm.

The basic idea is simple:

The device beacons continually indicating whether or not it detects a baby in the car seat. Any nearby BLE device can hear those beacons and will be able to react to them.

The parent either has an app on their BLE enabled smartphone (all recent iPhones and most, if not all, recent Android phones have support for this) that can listen for these beacons, or they have a complementary BLE gadget on their car keys that is paired with the baby sensor.

Now the clever part. One feature of the BLE spec is the ability to determine the approximate distance between the two devices. If the parent unit (app or key fob), detects the distance between it and the beaconing car seat increasing while the seat is occupied it can sound the alarm. Immediately reminding the parent that the child is still in the car seat.

Sensing the Child

There are baby seat alarms already on the market, but a study by the National Highway Traffic Safety Administration in July 2012 found none were that reliable. The devices in the study that sensed the child were mostly based on either a pressure pad under the car seat cushion, or a replacement chest clip for the car seat’s restraint. One was using carbon dioxide sensors integrated into the car to sense a breathing baby (or animal) left in the vehicle.

The pressure pads all suffer from being able to move, or having the child move off of them by shifting in the seat. The clips seem like they should be better but in the NHTSA testing seemed to have problems staying synchronized with the parent module. Also, as the report indicates, not all the deaths are from children in car seats. Some are from children who climb into the car themselves to play and then get stuck inside.

The TI Sensortag contains an array of sensors, most of which are irrelevant for this application (barometer, gyroscope etc). But, there is an IR temperature sensor behind that opening in the front of the device which functions a bit like the IR motion sensors username alarm applications. If the sensor is positioned where it can “see” the child, the IR sensor should be usable to indicate the presence of the child in the seat. The parent app can then arm itself and alert when it moves too far from the seat sensor.

Just an idea, and clearly it needs a little more experimentation and even a prototype. And then I think it would make an awesome Kickstarter/IndieGoGo crowd funded project.

An Alternative

If the IR sensor proves to be too difficult to make reliable, there is perhaps a simpler option: a tag bracelet that the baby wears and another that stays in the car. When the phone sees both tags, it arms. When the baby is dropped off, there will be a period of time when it sees just the baby tag, and then just the car tag again. If it starts moving away from the car tag and the baby tag at the same time, it can sound the alarm.

To avoid forgetting the baby tag, the app can also alert the user when it sees the car tag and not the baby tag; forcing the parent to confirm that the baby is not in the car for this trip before they set off.

Pebble Update

A couple of updates on my communications with Pebble about the audio interference, especially the A2DP but also the handsfree interference (which makes handsfree calls in my car near impossible most of the time).

I also get a response to a tweet about Pebble not really being ready for mass consumer use:

@bluedonkey We're proud of our approach. Shooting to be the best wearable out there.

I am happy that they are shooting to be the best, but I still don’t think they are quite there yet (and to be honest the recent versions have been going backwards IMHO).

Battery Issue
The latest on the battery issues I am seeing with the latest firmware came in the form of this email from their support team:

The logs I referenced were from 1 charge cycle, which did not reveal the substantial drop in battery life that you experienced in the aforementioned charge cycles.

Since we’ve verified the issue, let’s get you Pebbled again as soon as possible!

To make sure I fill out your Replacement Authorization with the correct information, could you please confirm the following:

Please also include a picture of the back of your Pebble with the Serial Number clearly shown and “Case # 239312 ” written beneath it on a slip of paper.

Once you have confirmed the above, I will fill out your Replacement Authorization and get you set up with a new Pebble!

So, aside from the fact that seeing one charge cycle that looked OK was enough for them to dismiss the issue initially (even though the report clearly stated that the battery issue was somewhat random), now their answer is to swap the hardware without any explanation. Since the watch is clearly operating normally, and some of the time has a very acceptable 10% per day battery consumption rate, I don’t see this being hardware. Seems far more likely that the problem is a software issue with something getting stuck in a state where the radio is on more than it should be.

Audio Issues
On the audio issues, I am not getting far either. The best response I got was to the update I sent their support organization with two 30 second samples recorded from an external Bluetooth speaker with and without the Pebble connected to the phone too:

With Pebble Connected:

Without Pebble Connected:

The drop outs you hear in those happen on all the A2DP playback devices I have tried so far, and only with the latest firmware (previously music playback to Bluetooth devices was fine). That got this reply from support which I take as progress:

Thank you for your e-mail and demonstration. The engineers have been made aware of this issue and are working on a fix for future updates.

I should probably try to record some samples of a phone call too so that they can hear how bad that is (it is much worse than the A2DP).

Pebble Battery Life

Given how random my Pebble’s battery life can be these days,I thought I would extract the battery level information from the logs they keep (tip: if you want to see these, just start the process to generate a support request but when the email editor opens change the recipient to your own address before sending).

The graph is quite telling:

That is a little over 6 days worth of data and clearly shows periods where the consumption is far faster than it should be to allow for several days of battery life. The last two days, I have had to charge the watch every night or risk having it run out mid way through the day (and I don’t want to carry the charging cable with me everywhere I go).

The most recent firmware was meant to address the crazy power consumption issue, but it looks from this chart as though their fix doesn’t change anything.