(this is page 19 of 121)





Latest

My iPad ship notification came early this morning, and I along with about a quarter million other overgrown little boys and girls started anticipating the early (late?) Christmas Day coming this Saturday.

I'm excited, but not because I have a portable TV to look forward to. I'm also not excited for the price inflation that app vendors (who have barely scraped by at $0.99 and $1.99) are going to try to foist upon us with the new form factor. In fact, I'm not excited to buy any apps at all.

What I'm most excited about is seeing how well an A4 optimized Mobile Safari can behave as a full featured application host— for the only type of apps that will actually matter long-term on the iPad outside of the mail client: fully native cloud apps.

Unlike the iPhone, we don't have to worry about the poor DOM support for things like the camera and the accelerometer, or the coarse and kludgey location support that the browser provides. Those things make a ton of sense for a device which is always with you and frequently needs to be used from hostile environments (at weird angles when you are not sure where you are). In the iPad's case what will matter is the ability to get near native speed and stability from the browser for the following things:

1. Multitouch. Mobile Safari for the iPhone has supported multitouch for a long time, albeit a bit too slowly especially when compared to the speed of the native app gestures. I sincerely hope that the A4 chip and the larger screen area (thus larger digitizer) closes this gap.

2. CSS3 transforms. Productivity style work doesn't need to be cinematic, but there is a certain amount of eye candy that can make a big difference. Dynamic highlights, accordion effects, etc.

3. Clientside storage. This is good enough on the iPhone. All they need to do is not break it (and maybe move the default upper limit on SQLite above 5MB)

4. Offline support. App-cache works on the iPhone, but it is a little squirrely sometimes. In order for the iPad to replace a laptop it needs to be rock solid on planes, trains, and automobiles (in tunnels) which means this needs to work more reliably.

5. Websockets for true bidirectional communication with a server for all of those emerging realtime apps. Ok, this one is a total pipedream and the truth is long polling works pretty well on the iPhone, but one can hope.

There are rumors floating around the Internet that Apple is looking to break all of this stuff in Mobile Safari (in order to encourage developers through their tollgate), but I doubt it. More likely the worst case scenario is that like any big company, Apple is a multi-headed beast— albeit one that is often tamed by Jobs— and as such, there will be a pocket of cluefulls that will do the right open web thing and let Safari make the iPad the first truly novel cloud access device.

We can hope.

In the meanwhile, if you're going to hold an iPad hack party in the coming days, consider targeting the partial HTML5 implementation on its Mobile Safari instead of falling victim to the sirensong of Interface Builder and its jazzy drag-and-drop goodness. You'll be doing yourself a huge favor when the other large OEMs start pouring tens of millions of cheaper Linux and Windows-based tablets into the market over the coming years.

And Merry Christmas.

Comments Permalink

In the last 2.5 years of heavy iPhone use, I've had a few cases where I've wanted to sit down to build an app that would make my life easier only to discover some iPhone SDK limitation that would make it impossible. The lack of background processing has been a chief culprit in a some of these cases, but in just about as many, the lack of true inter-app communication or even a decent plug-in system for the four most common apps (browser, messaging clients, camera, and maps application) has made writing multimodal glue impossible.

Multimodal glue? Let's take that mouthful in pieces.

Multimodal refers to the fact that the interface for computing should be able to move seamlessly throughout my day from my laptop at home to my mobile phone to my 24 inch desktop display at work, and even eventually, to my tablet of choice. This is one of two reasons for our collective move to clunkier web-based experiences instead of desktop apps (the other reason being the collaboration vector that is opened when the data is held on the server).

Some use cases have longstanding protocols that make this easy within the single application silo: IMAP for email being the best example. But others do not; for a great example of one app that is unnecessarily still stuck to the device, look no further than the SMS application on most phones (it's why I'll take the kludgey Google Voice solution to SMS (on any non Android device) any day over tapping out messages on a tiny screen while sitting at a huge monitor).

And glue refers to the interesting combinations that come out of being able to wire these applications together in new and unexpected ways. The web-as-platform is king here; a few years ago we called this class of interop "mashups" (thank God that term devolved into "smashups" before falling into cultural oblivion), but now we take it as given that you can plug your Twitter stream into your Facebook status, as a simple example, with a just a few clicks.

The glue apps are especially interesting in the context of a mobile device thanks to location information and the existence of a number of really interesting personal databases (call logs, addressbook, media library), and the fact that most platforms don't allow it (the iPhone is not alone here— RIM, Palm, and the forthcoming Windows 7 Mobile seem to be cargo culting their way to copying the wrong thing) is going be very good news for Android, and to a lesser extent Symbian Series 60.

But other than the platforms getting with the Android way of doing things, there is hope. Just as John Gilmore claimed that the Internet "interprets censorship as damage and routes around it," it would seem that web-savvy developers are seeing SDK limitations in multimodal glue as damage to be routed around. Reading apps that can post to Twitter is a good first example, though in this case, the app developer is forced to write an entire Twitter client within his app. A more interesting example are websites that rely on cloud services to deposit data into other apps. For instance, I read HackerNews on Mobile Safari and can mark an article for download into my Instapaper app through a link that is served to me. It's kludgey that the data is sitting in my browser and has to roundtrip itself through the Instapaper servers to get to my application, but it is nice a pattern that other developers can use to inject a little cluefullness into broken platforms.

A good thing to consider as we sit here right before the release of the completely gorgeous but totally locked down Apple iPad.

Comments Permalink

I thought long and hard about this next step, and in the end chose to do it over what I've known to be a very fulfilling and exciting career as an entrepreneur for two reasons.

First, throughout my entire entrepreneurial career, things have been much more concrete: I saw things that I wanted to work on and just dove right in, come hell or high water. These last few months though, I've been primarily thinking about the entire Internet venture ecosystem, and specifically, what seems to be a worrisome trend here in Boston (thanks Bill Warner) , with fewer and fewer startups turning into big companies that can bolster tech entrepreneurship in the region. I want to see this ecosystem thrive for very selfish reasons: it makes living here, a much more interesting experience.

So I had two choices: take another swing at making another big company, or try my best to find as many possible nascent ones as possible and help them as much as I can through investment, strategy, recruiting, and general ecosystem reinforcement. I've chosen the latter for a variety of reasons, but the most important one is that I am ready to make a sector bet on this next phase of the Internet's evolution in a way that I never would have before.

What?

I am fairly confident about the following statement: the Internet will continue its rapacious pace of absorbing just about every facet of business, and more significantly, regular life. Advertising, media, entertainment, commerce, communications— even staid industries like manufacturing are all being transformed by open protocols, ubiquitous connectivity, and more efficient information exchange— in short, all that has made the Internet the best platform ever.

At the same time, everything else is up for grabs: UIs for access (Android, iPhone, iPad, TV?), models for computation (the client, the cloud, a hybrid?), business models, and even basic patterns for work and play. More than any other time in my career, has the map been so confusing towards such a clear long view.

And rather than be tied to one 7-10 year bet on how to make a big contribution to our ecosystem, I've decided to zoom out and bet more widely on the entire space. I am sure that we'll get some monster hits out of this primordial soup— and I hope I get a chance to help with a few of them.

The second reason why it was a hard decision to make was because I hate being a freshman, plain and simple. And when it comes to investing in tech companies, I've clearly got a lot to learn.

One of the possibilities that I considered was in the emergent models for seed/A funds built by former operating entrepreneurs. There are a few of these funds run by folks I've gotten to know and respect, and there might be just be an opportunity for them to carve out a permanent niche in the supporting environment that sustains startups.

In my case though, I wanted a chance to learn the business from folks who have been at it for a few decades and who have shown repeated success across industry changes in helping entrepreneurs get big. And there is little doubt that Matrix is the place to do that (as the freshman in the class, it's a little daunting).

For sure there is an element to be learned around identifying the right bets to make but I was more concerned with understanding how the best investors seem to be able to provide help all along the way, nurturing and guiding entrepreneurs until their small companies grow to fit their big visions.

I presume this stuff is not going to be easy but I'm looking forward to the challenge.

Comments Permalink

Why I bought an iPad

Apple is doing douchey things with its app store policy and newly discovered offensive position on patents. For sure. And yet, I joined the masses of folks on Friday that made the company close to $100M of presales on a product none of us have seen. It hurts me to fork over money to such a closed ecosystem, but I did it anyway.

Not because I am a fanboy. Not because I want to watch video in bed. And certainly not because I want to replace my laptop with a new class of device.

But because I've got a really compelling usecase and am currently using a poor substitute.

My Aye PadThe picture to the right is my ailing original iPhone running an app called Instapaper— a fantastic slim little app that lets you select content from any webpage for reading later. I have bookmarklets installed in all of my browsers and the app running on this crap old iPhone. I collect content throughout the day and (sometimes) read it at night while in bed. The iPhone lives by the bed (along with a charger) and occasionally doubles as a web access device for sending a reply to an email that I've forgotten or looking something up.

However, it is crappy and suboptimal because of how little the screen is. So much so, that I used to print out my Instapaper archive and take that to bed. Which would be okay were it not for the one-way trip to dead that content takes when it gets on paper— no sharing, no commenting, and no peripheral exploration of references within the content.

This convenience is worth the cost of entry for me. It may not sustain a runner product like the iPhone, but in aggregate, I think that looking for a way to place and device shift longer form reading is a killer app for the tablet form factor. The Kindle, while great for novels, is too close to paper to fulfill this role.

Apple ought to pay attention to apps like Instapaper in the event that it discovers that not all of us want to continue feeding on TV content after we've gone to bed.

Comments Permalink

It is a mystery to me how the hobbyist hacker community can make Android so much better than the stock images that Google ships, but if you've got a Nexus one, Cyanogen has just made things much much better. As an iPhone owner from day 1, I can tell you that the simple fact of moving from the stock 2.1 image that comes with your Nexus to the latest Cyanogen creates about the same feeling of improvement that moving from an iPhone 3G to a 3GS provided— except that in this case, you aren't changing your hardware. It is software's true magic!

If you've got a Nexus One, and are interested, read on.

Unfortunately, the process is far from simple and the Android mod community has a lot of new jargon that you have to get used to. If you've ever jailbroken an iPhone or iPod Touch, I'd say this is about 30-50% more involved, so get ready to rumble.

Fortunately, I had the benefit of Eddie's amazingly good notes to guide me through it all. I am reproducing them below, along with a mini glossary at the front, and some comments in places that I found tricky. Your mileage may vary on these, and be aware that you could in theory brick (or destroy) your phone, though practically speaking, I've found this to be almost impossible to do with how well the boot loading sequence has been thought out on Android.

--

Some basic terms:

In Android land, the equivalent of jailbreaking is "rooting" which refers to getting access to the root directory of the phone's ROM (which is not really Read Only since both Google/HTC and you overwrite this with every update). In the steps below, you will be using a command line program called "fastboot" to do the unlocking on that root directory and install custom software. Fastboot is also the name of a mode in the Nexus when you first boot up (it is actually available to all Android phones) that gives you a sort of minimalist OS/boot loader thing to take actions that affect the OS in the phone. It's not quite like a PC BIOS menu, but it can be helpful to think of it that way. Below you'll see the key combination required to get the phone to that which can vary a little by model.

Also, there are three basic software bundles you will be applying after the phone is "rooted:" the recovery image which basically provides a more powerful fastboot environment (to do things like unlocking and backing up), the baseband update (which is just like the iPhone one is that it updates the separate system that runs the radio), and the Cyanogen custom ROM which is the magic that will make your Nexus instantly better.

There is an additional step required which has to do with the crappy licensing around the proprietary Google apps (that you will definitely want on: Market, Gmail, Maps, etc.). Because Google asked the Cyanogen guy to stop including those with his mods, you'll have to apply them as a sort of patch when you are done. This is ok and is actually the easiest part of the update.

We did all of this on a Mac and the instructions below are for that platform— however, I am sure the Android SDK is good enough that it will be a relatively simple exercise to transpose the instructions for Linux and Windows. We did assume however that you are comfortable with the command line.

Finally one important note: in doing this, you will lose all of the data on the phone. Because of Google's phenomenal sync, this won't affect email, contacts, or calendars, and because the media (pictures) are stored on the SD card, you will be fine there, but depending on which apps you've installed, you may lose some local data. You will also have to reinstall all of your apps. You have been warned.

Let's get started:

1. Take a deep breath. It is just software and you are going to master it!

2. Download and install the Mac OSX Android SDK. I am going to assume for the purposes of this list that you have put it in /Applications/android-sdk-mac_86/tools/ but it doesn't matter.

3. Get fastboot-mac from here. Rename it 'fastboot' and put it in /Applications/android-sdk-mac_86/tools/.

4. Get Radio_20100203_2_Signed_PASSION.img,
update-cm-5.0.4.1-N1-signed.zip AND gapps-passion-ERE36B-2-signed.zip
from here and put them in /Applications/android-sdk-mac_86/tools/.

5. Get recovery-RA-nexus-v1.6.2.img from here and put it in /Applications/android-sdk-mac_86/tools/

6. Put Get Radio_20100203_2_Signed_PASSION.img,
update-cm-5.0.4.1-N1-signed.zip and gapps-passion-ERE36B-2-signed.zip
on the root of the SD card. You can do this by mounting the phone via a USB cable (this works just like any USB stick except you have to click a button on the phone's UI).

7. In your phone settings > applications > development, set usb
debugging to enabled.

8. Turn off your phone and put the SD card with the 3 files on it
into your phone.

9. Hook up the USB connection to your phone and your mac.

10. Reboot phone into fastboot: Hold down trackball, push the power
button and hold both until you see the fastboot screen. (The fastboot
screen is the one with the Androids on skateboards)

11. In Terminal on your mac, cd to /Applications/android-sdk_mac_86/tools

12. Type ‘./fastboot devices‘ to make sure your phone is recognized
(it should list a device number rather than simply returning to
command prompt with no feedback).

13. Type ‘./fastboot oem unlock‘ to unlock the bootloader (wohoo, your phone is now rooted!)

14. Use volume keys on the phone to navigate to yes and press the
power button to confirm.

15. When the phone finishes booting, in your phone settings >
applications > development, set usb debugging to enabled, then power
it down.

16. Reboot phone into fastboot: Hold down trackball, push the power
button and hold both until you see the fastboot screen. (The fastboot
screen is the one with the Androids on skateboards)

17. (you're still in terminal in /Applications/android-sdk_mac_86/tools)
Type ‘./fastboot flash recovery ./recovery-RA-nexus-v1.6.2.img‘. (Note
filename will change as recovery image is updated)

18. Type './fastboot flash radio ./Radio_20100203_2_Signed_PASSION.img'
to also update your radio at this point

19. Once the Recovery flash is complete (should be almost instant),
press the Power Button. The highlighted blue text should now say
HBOOT. Use the volume down button to highlight "Recovery" and hit the
power button to reboot into recovery.

20. if this step fails, power down the phone, and try this: hold down
the VOLUME DOWN button and then hold the POWER button until you get to
the skateboard screen; use volume down to highlight RECOVERY and hit
the POWER button

21. You should now be in the Recovery screen after a reboot -- this
screen has 9 green text options at the top and an android x in the
center of the screen

22. Once in Recovery Mode, use the trackball to scroll down to
"Backup/Restore" and press the trackball three times, and wait until
the backup is complete.

23. Once backup is complete, wipe, since you're coming from stock
(even fastboot oem unlock may not fully wipe, do it just in case) many
users report the phone not booting properly without a wipe at this
point.

24. Scroll down to "Flash zip from sdcard", and press the trackball.

25. Select the CyanogenMod update (update-cm-5.0.4.1-N1-signed.zip),
and press the trackball again to confirm. Wait until the flash is
complete. (Note: this will take a little while).

26. Once again, Scroll down to "Flash zip from sdcard", and press the trackball.

27. This time, select the Google Apps File
(gapps-passion-ERE36B-2-signed.zip), and press the trackball again to
confirm. Wait until the flash is complete.

28. Once you are back in the main menu, press the trackball select the
first option (Reboot system now) and reboot the phone.

29. If everything was done correctly, the phone should boot into CyanogenMod!

Eddie's extra bonus section— only for the adventurous (I have not tried this!)

Follow the instructions here to download your kernel and associated .ko module, your overclocking tool, and go
to town with undervolted and overclocked goodness!

Good luck. If it works correctly, it should take about 35-45 minutes to do it. And at the end of it, you will not only have one of the coolest hacker phones, but you will have done it! And trust me, it is worth it!

[A big thanks to Eddie, who both plied me with drinks last week to convince me that I should take this on, and then produced the first draft of this document so that I could not end up bricking my own iPhone]

REFERENCE

http://forum.xda-developers.com/showthread.php?t=611829
http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
http://forum.xda-developers.com/forumdisplay.php?f=559
http://wiki.cyanogenmod.com/index.php/ADB
http://developer.android.com/guide/developing/tools/adb.html
http://forum.xda-developers.com/showthread.php?t=459830
http://andblogs.net/fastboot/
http://developer.htc.com/adp.html
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Nexus_One_Firmware_to_CyanogenMod
http://www.mahalo.com/how-to-hack-a-nexus-one#cite_note-4
http://www.cyanogenmod.com/home/cyanogenmod-5-0-nexus-one
http://forum.xda-developers.com/showthread.php?t=633238&page=66

Comments Permalink