« swipe left for tags/categories
swipe right to go back »
This morning, as I was waiting for my laptop to grind through its startup process I started wondering why I had a laptop. I travel a lot and had it with me in San Francisco and Los Angeles this week, but hardly used it. And, when I did, I was frustrated with how long I had to wait for it to “get started”.
Today, while I was waiting for my laptop to sync email (Outlook 2010) I grabbed my iPad, opened mail, and read/reply/deleted all of the email that came in over night. I was finished processing the email before my laptop was ready to be used.
I had this same experience yesterday morning in LA. Except then I processed all of my overnight email on my HTC EVO phone which was also acting as the hotspot for my laptop to connect. And, throughout the day, I just did email on my phone instead of firing up my laptop.
The only time I used my laptop last week was a three+ hour stretch in San Francisco when I was at First Round Capital’s office (thanks Josh for the use of your desk) in between meetings. I had turned on my laptop at 8:45am when I got to FRC’s office, did a board meeting from 9am to 12 (the laptop was in a different room), and then used my laptop from noon until I left around 3:30. By noon it had fully synched itself.
As I write this, I realize that Android and Apple both sync faster with my email on an Exchange data store than my Windows 7 laptop with Outlook. A lot faster. It doesn’t seem to matter whether I’m connecting over 3G or Wifi – my Android phone, iPad, and iPhone are ready to go right away whereas my laptop takes anywhere from 5 to 15 minutes to get into a fully usable state (where the disk doesn’t spin an slow things down, or Outlook is non-responsive, or something else funky is going on.) I’m on a Lenovo X300 with 4GB of RAM so it’s not the hardware.
I wrote this post on my iPad using the cute little iPad keyboard doc. It appears my laptop is once again useable, but it’s probably too late for me this morning. Time for a run.
Google gave all 5000 Google I/O attendees an HTC EVO (I guess it’s a Sprint EVO) running Android. For the past two years I’ve been using an iPhone and have become increasingly disgusted by AT&T’s service which is horrible (and deteriorating) in the cities I frequent – most notably Boulder, San Francisco, Los Angeles, Seattle, NY, and Boston. So – I decided to give the EVO+Android a real shot and use it for a week as my permanent phone.
When I wrote my post Open Android vs. Closed iPhone right after Google I/O a few folks took shots at me for pimping a free phone that I got at a conference. Given the amount of money I regularly shell out to screw around on hardware and software (I’m one of those guys who happily buys things just to try them out) I shrugged this off but figured it was worth pre-empting since I’m sure this nonsense will come around again. So – there’s the disclaimer – I got this phone for free (although I did sit on two panels and spent a day and a half talking to people at Google I/O.)
While there has been plenty of fan boy and anti-fan boy chatter about this phone, I can only find one thing to complain about – the battery life. It’s still running Android 2.1 so I expect there will be plenty of battery tune up in Android 2.2, but out of the box the battery only lasts about six hours. I’ve tuned my settings so I can get a full day out of it, but am still carrying my USB cord to grab some juice from time to time. There a few tricks (like charge it with it turned off) that help a lot, but it feels like the iPhone 3G did when it first came out where I was always paying attention to how much charge I had left. Fortunately this will get better with software (quickly) and – since the battery is removable, I can just carry a spare around.
Ok – that’s literally the only thing I don’t like. The screen is phenomenal. All of the apps I run on my iPhone are available on Android – I even found a few new ones. The camera is killer. The email client is much better than the iPhone. Search for anything is lightening fast. Voice recognition – er – recognizes my voice. I have a phone that tethers and – if I want – I have a hotspot (bye bye MiFi.) My applications remember their state and come up instantly because they are still running in the background. The browser is fast. Google Maps + Navigation is incredible, especially for someone who can’t read a map to save his life. I can dial a phone number, look up an address, and get directions from within the calendar. The weather app knows where I am. Google Voice works great and is tightly integrated.
And – for the payoff – I can make a fucking telephone call on this thing. I can’t remember the last time I looked back after a day and thought “wow – I didn’t drop a single call today.” Now the only dropped calls I’ve had are when I’m talking to someone on an iPhone and they drop.
I’m looking forward to iPhone 4.0 coming out so I can see how it compares. My guess is that I’ll get the Android 2.2 upgrade at about the same time so I’ll have both to play around with in June and July. The real result will be to see which phone I’m using when I get back from Alaska in August. In the mean time, the HTC EVO is a winner and – as a result – the smart phone thing is going to get interesting now that Apple has some real competition and can no longer just walk all over Microsoft and Palm.
Did I mention that I can’t wait to get my hands on an Android Tablet?
I’m at the Glue Conference all day. So far, it’s far exceeded my already high expectations. I’m now sitting in the API track and the first two presentations have been dynamite. Clay Loveless from Mashery just did a presentation titled “5 Things I Hate About Your API-TOS“. He nailed it. Here are his top five (most important last), along with some commentary from me.
For simplicity, I’ll call the company providing the API’s the “platform company” and the companies using the API as the “ecosystem partners.” Also – I’m not picking sides here as I’m an investor in both “platform companies” and “ecosystem partners”. Rather, I’m just trying to summarize Clay’s points, bring out a few ideas, and give you a sense of the kind of stuff we are talking about at Glue.
5. Do You Think My Code is Yours? While it may seem like a stretch that a platform company trying to create an ecosystem would try to assert this, the phrase “derivative rights” appears in a surprising number of platform company API’s. And I’ve run into people that actually believe they own the code (or rights to the code) developed by their ecosystem partners. The only thing I can say to this one is “be careful and don’t accept absurd assertions.”
4. It’s Just Tooooooo Loooooong. This one is related to the next one, but it’s what happens when the lawyers take over. See #3.
3. It’s Written in Legalese, But I Speak Geek. Thanks for the 14 page TOS – now what the fuck does it mean? Give me a one page summary in plain English and bullet points. Be “ecosystem friendly” – all the time. Don’t bury the lead on page 11. Just tell me the rules so I can play by them.
2. Commercial Use OK Or Not? I’m seeing this become increasingly contentious between some platform companies and their ecosystem partners. Until the platform company is successful, this is a mellow and happy situation. Once the platform company becomes successful, often in part to the adoption of their API by their ecosystem partners, the platform company starts trying to split out commercial and non-commercial use, at least in certain areas. If you are an ecosystem partner and you think this evolution should be against the rules, just check page 10 of the TOS (per point #4) where it says “Company reserves the right to change any aspect of the TOS at any time in the future.”
1. TOS != Product Roadmap Communication Platform. As an ecosystem partner, you should assume the platform company will change its roadmap over time to support its business goals. It can be painful when this happens in the context of a TOS change, although I think there are some cases where the platform company just has to say “ok – here’s how we are going to do things going forward – deal with it.” The solution to this one is clear and open bi-directional communication – as long as there is trust and no one is trying to hide the ball or do things that are clearly “over the line” in terms of the TOS, these situations are usually quickly resolvable with an appropriate commercial agreement.
Oh – and if you want to run Java on an Apple IIc, here’s how you do it.
I hate spam. Over the years I’ve been an investor in a number of companies that address the spam problem, including Postini and Return Path. I’ve also been involved in lots of other companies in the email ecosystem and spam has always been something I’ve paid close attention to.
I’ve thought hard about Blam (Blog Spam), Spim (IM Spam), Skam (Skype Spam), and SMam (SMS Spam). A few times in the past I’ve thought about Twam (Twitter Spam) but Twitter has done a good job so far of dealing with most of the nasty stuff, the most visible being the porn-follower twam that they somehow managed to beat back (or that I’ve successful ignored).
Today, I got caught in a twam trap. I got a note from someone to try out a service. It’s someone I’d heard from before so I went to the new site and played around with it. I wasn’t terribly impressed and didn’t really get it. A few minutes later I got a DM from a friend that said “@bfeld none of the links on that page are active, fyi. tried Chromium + Safari”
I didn’t know why my friend was tweeting me that, but then it occurred to me that playing around with the software must have sent out a tweet. I took a look and lo and behold it did. I didn’t want that, nor did I set it up. But it did. Yuck.
Automatic tweeting from within applications is becoming commonplace. This is good in many cases, but unless the sender authorizes the actual tweet, it’s twam. There’s no opt-in dynamic around twam, so before a service sends out a tweet for the first time, it seems like good form is to make sure the user wants to tweet. Most, but not all, do.
When you develop a twitter integration, think this through. Don’t be a twammer.
On March 8, 2010 Amazon fired me as an Amazon Affiliate because of Colorado HB 10-1193. I proceeded to have a dozen different conversations (email and live) with several of my state representatives, including one of the co-sponsors of the bill, and each conversation made me more incensed at the abject stupidity and lack of understanding of the dynamics surrounding the situation. Ultimately, the argument came down to one of protectionism – e.g. “we have to protect our local merchants so Amazon shouldn’t get an unfair advantage by not having to charge state tax.” I could rant about this for a while, but I’ve got better things to spend my time on at this point.
I’ve been an early Viglink user for a while. Niel Robertson, the CEO of Trada, introduced me to Viglink’s founder Oliver Roup and I agreed to be an alpha tester. While we aren’t an investor, I’m intrigued with what Viglink is doing and I’m already a big fan.
Last week I realized that all of my going forward Amazon links (and other links to merchants with an affiliate program) were getting rewritten by Viglink. As a result, on a going forward basis, I was getting Amazon affiliate revenue (via Viglink) for anyone that clicked through one of my links and bought something on Amazon.
That was cool, but I have a gillion of old links using my Amazon affiliate code that no longer works. I asked Oliver if he could rewrite all of the old links also. Here’s his response:
“We have coded this and deployed it. As a result, all your dead Amazon affiliate links will be overwritten with our affiliate code and the revenue will be credited to you. What’s more, we just created an affiliate program against ourselves – any links you have to us on your blog will automatically be affiliated and you will receive 10% of the revenue from any customers we get as a result of those links.”
Awesome! If you are a fired Amazon Affiliate in Colorado, take a look at Viglink.