Cover photo

Reinventing the Home Row

post image

I have been intrigued recently by apps that give a new spin on what have previously been stock features of the phone.  Apps that a) improve upon in minor ways or b) really try and re-invent some of the basic things we do every day. Above is a snapshot of my new "home row".  Sort of -- I say sort of because this isn't actually working for me, yet, and I'll explain why in a sec. Brewster is an app that I think of as a "launcher for people" -- their goal is to be the fastest, most intuitive, way to initiate contact with anyone, regardless of mode.  It takes your contacts, twitter followers, facebook friends, etc, and makes it easy to find who you want to find and then contact them how you want to contact them (via SMS, phone, twitter, etc).  I really like the idea of flipping the paradigm to "people first, mode second", vs how it is now: mode first (twitter, sms, etc), then person. I love the potential of Brewster, but it hasn't made it into my routine yet, for a few reasons: 1) speed.  It simply takes too long to fire up -- the whole appeal of this app, to me, is that it's the fastest, easiest way to find someone.  For that to work, it actually needs to be the fastest and easiest.  I would love it if they optimized the app startup process so that I see faces (ideally the best faces) super quickly.  2) intelligence.  Part of the promise of Brewster is to cut through the hundreds of people I'm connected to and surface the ones I'm most likely to want to contact.  Since I've authed them into my gmail, twitter and facebook, and they can see what's in my phone, I would expect them to do a better job of this, but it's not quite there yet.  3) A few bits of clunky UI -- the Brewster UI is all hand-rolled, so it doesn't feel native to iOS, and there have been a few times where that's lead me to make some mistakes (for instance, canceling edits on a contact when I thought I was saving them). I assume this is to make cross-platform development easier, and I expect it to improve over time.  But as it is now, it's not quite as easy to use as I would like or expect. Sparrow is a really nice email client for mac and iOS.  The've made a lot of subtle improvements over iOS Mail, which I won't go into detail on since it's been widely blogged about.  The feature that made me switch was search -- Sparrow's search is so much better than iOS Mail search, and searching email is something I do a lot.  Sparrow has been my daily mail client for a while now.  They were just acquired by Google, so there's some concern in the user community about what will happen to the app. For my part I'm not worried; it's great how it is now. Cue is the one I'm most excited about.  It's the next generation of what was Greplin, a search appliance across all of your web accounts.  They've pivoted and the idea now is to "cue up your day" with a super-charged daily agenda that draws from your calendar(s), mail, twitter, facebook, etc.  This is a radical, socially-powered, reinvention of the calendar, and I really really like the idea.  And the job they've done executing so far is really nice.  There is so much potential here, really (think: surfacing important to-dos, linking to bios of people I am meeting with today, giving me travel information a la TripIt, etc.). However, there is one simple problem which is stopping me from using the app completely: by default (and this is unchangeable), it draws appointments from every google calendar that has been shared with you.  For me, that's about 50 calendars.  So my cue is full of seemingly random events from calendars that aren't part of my real day.  I tweeted this feedback their way and got a response that they're working on this, and I hope they prioritize it, because it's a make or break feature for me (and I must assume it's the same for many others). Last, but not least is Chrome for iOS.  I'm a big fan of Chrome for mac, and my Chrome is totally tricked out with extensions and customizations that make it really work for me.   In starting to use Chrome for iOS, the one feature that's come in most handy is google login and shared history -- makes it really easy for me to access sites from my computer's browsing history when I'm on my phone.  This is a super nice feature, especially on mobile where typing is annoying.  Of course, the big problem here is that  you can't make Chrome your default iOS browser, so whenever you launch a link from another app, or from a home screen shortcut (I use several), you end up back in Safari.  Boo, Apple, for not making this configurable.  The solution here is to jailbreak my phone, which I just haven't gotten around to doing yet. So, that's about it -- lots of potential here, but some hurdles as well.  The screenshot above is what I want my home screen to look like.  Here's what it actually looks like now:

post image

I hope that will change soon.

Smoke Detectors, or, it's not the Backup; it's the Restore

This week we are out in Cape Cod with Frannie's family, hanging out at the beach in Truro (where, incidentally, there was a shark attack a few weeks ago).  This week, we're renting a different house than normal -- it's an old run-down house next door to the cottages where Fran's family has vacationed forever, that was fixed up into rentable shape over the winter. Last night, as everyone was sleeping, a loud alarm went off.  A few minutes later, it went off again. It woke us up and we started investigating.  It turns out it was the smoke / carbon monoxide detector. We were a bit freaked out, because of carbon monoxide's reputation as the "silent killer" -- we didn't smell any smoke and couldn't detect anything out of the ordinary, but we also couldn't explain why the alarm was going off. Most importantly and disturbingly, neither of us knew what to do when the carbon monoxide detector went off.  Do we call the fire department?  Press reset?  Call the person we're renting the house from (who is 200 miles away and sleeping?) How do we know this isn't just a bad battery?  Ultimately, I pressed the "test / reset" button (that's what you're supposed to do, right?) and the intermittent alarm stopped, but we weren't even sure how to tell what that meant. We didn't know any of the answers.  So, in the midst of a mild panic about the kids asphyxiating in their bedrooms, we turned to Google.  We searched to try and figure out what exactly you're supposed to do when that alarm actually does go off.  Turns out a lot of people have the same question.  I looked all over, and even ended up in a PDF of the product manual for a detector -- amazingly, the whole manual has only one short paragraph on what to do when the alarm goes off. Eventually, we came across some information (somewhere; I can't remember) saying that in cases of power surges or interruption, the alarms can go off -- and I remembered that the lights in the living room had been flickering the night before.  And to, in these cases, press reset to stop the beeping and wait to see if the alarm resumes.  If not, then don't worry.  Ultimately, this answer worked for us, and we were able to get over the scare and try and get back to sleep. But the whole experience was kind of dumbfounding.  The fact that we really had no idea what to do in case of alarm -- how to tell a real emergency from a false alarm (especially when I've changed the batteries in 5 smoke detectors in my in-laws' house in the past few months to stop the beeping).  How to interpret the beeps; who to call; what to do.  What good is an alarm if you're not sure what to do when it goes off?  It made me really appreciate all those fire drills we did as kids in school. All in all, it reminds me of the (old?) saying in computer land -- having backup procedures is good, but what you really need are restore procedures.  A backup is no good if you aren't sure you can use it or don't know how.

IP Enforcement Strategy

Today is the last day to submit comments to the White House on its plans for Intellectual Property enforcement for the coming year. This is yet another act in the fight for the future of everything, and it's a relatively obscure and quiet one (as we expect many more will be, in the wake of the SOPA/PIPA blow up). A number of folks from the internet community are submitting letters to this request today, urging the WH to take a modern view of dealing with the challenges and opportunities in digital content creation, distribution and monetization. This afternoon, I am drafting a short response, which I'll post here when it's done.  I'll be drawing a lot of inspiration from the terrific report by Professor Ian Hargreaves, which was commissioned by the UK last year: Digital Opportunity: A Review of Intellectual Property and Growth (PDF).  This report is one of the best I've seen at laying out, in balanced and measured terms, what I consider to be an intelligent and progressive approach to IP management. In the meantime, I urge you to take a few minutes and respond to the White House survey.  You don't need to write a long or detailed response, and it's important for the WH to hear from a large number of folks who understand the impact of IP enforcement on innovation and the web. Another point of reference is France's recent move to reduce its focus on strict enforcement as a way of dealing with piracy.  Their work over the last three years has basically shown that the "three strikes" approach to policing piracy is both expensive and ineffective.  This is an important precedent as the US considers how to allocate its efforts moving forward. Update:  Here's the letter, signed by me, Brad Burnham, John Buttrick, Beth Noveck, and David Weinberger: Update 2: Here are a bunch of other letters submitted by internet folk:

The Slow Hunch by Nick Grossman

Written by

Investing @ USV. Student of cities and the internet.

Subscribe