It’s a shame, really. You’ll just have to imagine all of the obscene, over-the-top alliteration I would’ve used.

Quick recap:

• The car2go 24 hour project was a ton of fun. Got to meet with their CTO and hear about what they have planned for the future. Since car2go.markphillip.com launched, Austin CarShare died. I’ll let you read between the lines. More importantly though, I now have a little blue car2go USB drive that I like to chew on. Win.
• My HVAC died back in June and I was AC-less for almost a month. Any discomfort for those few weeks is overshadowed by the awesomeness of the new cooling system. I’ve never been so thoroughly obsessed with a home appliance. Two-stage HVACs, ftw.
• Twitter is still dumb.
• Through some dumb luck and quickly-written emails, Are You Watching This?! was on ESPN.com and Deadspin. RUWT?! momentum is really good right now.
• I’ll be travelling a lot over the next six weeks. Get your airport abbreviation dictionaries out, kiddies.

Night, kids.

car2go.markphillip.com

Thought you’d like to know.

Build #2: car2go.markphillip.com

This build is start to look a whole lot more like a mobile app. One big question though: Who exactly are we building for?

iPhone/Android/Palm are of course at the top of the list, but what about Blackberry? Sure, it’s the odd-man out when it comes to a Webkit browser, but I rock a Blackberry. Am I really building something that I can’t use?

Yes and no.

I definitely won’t see the hawtness that the iPhone/Android/Palm triumvirate will enjoy, but with graceful degradation I’ll still accomplish the overarching goal: a super fast app that can get me to my car2go when I’m on the go. And the good news? With their next OS, Blackberry will finally join the cool kid Webkit club.

So all is peachy, right? Instead of building a native app on four different platforms with four different languages, I’ve built just one using the ubiquitous HTML. Not exactly.

While wrapping these pages into native apps and posting them to their respective stores is trivial at this point, I’ll never have access to core features like GPS detection. For this app, more than most, is an important feature. We worked around it by remembering recent location searches, and squeezing all the performance we could out of the app, but it will always be brought up up by the native app purists.

And that’s really, really too bad. Many in the tech community will rail against the evil that is the closed, proprietary Flash, yet will happily spend months learning Objective-C to build an app for the most closed-off platform we have.

Peter-Paul Koch had a great post last year (Apple is not evil. iPhone developers are stupid.), but sadly backed off it the very next day (Native iPhone apps vs. Web apps).

Truth is (and admittedly this is excessively blunt because I’m tired), native app developers on any single platform are stupid. And it’s not just the smartphone developers—I’m looking at you, Seesmic and Zynga.

Jeez, this post has taken me a long time. I’m gonna cop out, end it there, and get back to work. Trust me, it was gonna get even more boring.

car2go.markphillip.com

Not wanting to repeat the same mistake I called in my go-to designer (and fellow, car-less, scooter rider) Tara to make it worthy of car2go’s clean, modern design.

She’s already paying big dividends.

There are always bugs in software development. Nothing is scarier than doing a code read of a big mess of work, and not being able to find anything wrong with it. No typos, no comments to be updated, and nothing to optimize. There are always bugs. Always. And if you can’t find one, it just means you’re not looking hard enough.

Things are going so well that I’m due for a whopper.

Looks like the Google Geocoding API will have to make an appearance sooner than expected. Their daily limit is 2500 requests per IP. Normally that’d be a ton, but with almost 200 cars, I’d whip through 2500 requests pretty darn quick.

I had planned an in-memory address/latlon cache, but if I don’t persist the results in the database, my fatfingered coding stylings might put me in a world of hurt.

Already down to 14 hours and change, but thankfully I woke to a server at the ready with car2go.markphillip.com patiently waiting for it’s first task.

So what exactly are we doing today? First, some background.

car2go is a car-sharing program that descended on Austin earlier this year. Unlike any other program I’ve seen, it’s completely focused on one-way trips. Find a car, hop in, drive it, park it, walk away. There’s no returning it to where you first picked it up, or even searching for a sanctioned parking zone. You just park it at any legal street parking spot (meters are okay too), and shed your 90-hp speed demon like a NASCAR tearoff.

It’s pure genius.

There are 200 cars scattered about the Austin area, and with a quick swipe of your membership card you’re off an driving. For someone that lives Central and hasn’t owned a car since 2004, it’s pretty much the best thing ever. Except for one small thing…

Finding, and even reserving cars online is a breeze, but what about when you’re around town running errands? I’m not an iPhone-owner so I can’t use the official app, and the CSRs on the toll-free members help line, while quite polite don’t know the Austin area very well. They’re based somewhere in Europe so I can’t really blame them. If you called me up to ask for directions to Trafalgar Square, I’d struggle too.

car2go needs to have apps for all smartphones, and today the goal is to build it for them. We’ll be building a Webkit-focused mobile site that has as much functionality as we can squeeze in. If it all works, not only will there be a mobile-friendly URL that any phone can visit, but we’ll be just a hop, skip, and a jump from installable apps on iPhone, Android, and Palm.

Enough blabbing. Time to go slurp up some data.

Okay, I know I said I was headed to bed, but as I closed my browser I was greeted by an image too funny-looking not to share. Do I really look like that?

Okay.

Bed.

Back in ‘08 CapMetro started publishing all of their stop and schedule data using the Google Transit Feed Specification. To a public transit geek like me, that’s pretty awesome stuff. You can keep your Twitter API (shot at Twitter? check.), I’ll be over here hanging out with my real world people data.

I made googly eyes at the data for weeks, never able to rationalize playing around with it to see what I could build. I finally solved the painfully geeky internal struggle by giving myself 48 hours to play with the data. Once the time was up, I had a to let it go and get back to real work. And surprisingly, it turned out pretty awesome. CapMetro’s CIO noticed, and I got to visit them and talk some GIS shop.

So why has the time-based title made a comeback? Because I’ve become obsessed with car2go. We’re talking serious fanboi here, people. I haven’t gotten middle-aged-woman-watching-twilight bad, yet here I am on a Saturday night talking to you.

I just spun up a new server, and all of my domain ducks should be in a row come morning. I’m only giving myself 24 hours this time–hopefully it’ll be enough to knock it all out.

Night, kids.

Here’s 12 minutes of me talking about sports and race, along with a veiled shot at Twitter tossed in just for fun.

The crazy rotation that’s a part of any contractor’s life continues, but most of my gig time since HomeAway has been spent doing work for Ace Hardware. A handful of Facebook apps and a microsite made up the hit list.

I’ll actually be at work during the Super Bowl, sweating through one of the most nerve wracking launches I’ve ever been a part of. My contract gig at HomeAway is wrapping up, and after two months of ActionScript-slinging and Airport-sprinting, we get to share it with the world.

Third Quarter. Griswolds. Stay tuned.

Admittedly, it’s hard for me to hate Walmart more than I already do—the real travesty is that this puts Halloween officially in our rear-view mirror, and I must bid adieu to The Mash. It’s easily in the Top 5 of cool projects I’ve had the luck to contribute to, the best use of Facebook Connect I’ve ever implemented, and the team was an absolute blast to be a part of.

Check it out quick before it’s retired and we’re left with another season of going to Jared.

You should come check out my talk on building add-ons for Firefox and Fennec at this month’s Refresh Austin meeting.

Tonight. Buffalo Billiards. 7pm.

There’s food. There’s beer. There’s ample time to heckle me.

Be there.

http://www.facebook.com/event.php?eid=170821558189

But as far as intimidating intros go, where does it rank? I ask you, America: Ivan Drago in Rocky 4 or Jay-Z from Game 2?

I remember standing stationary in the busy hallways at SXSW/i ‘06, mesmerized by the Twitter chatter plastered on Plasmas all over the Convention Center.  The overwhelming buzz and seemingly overnight new media darling status has quickly changed that mystical chatter into annoying noise.  What kind of noise?  Well, as I write this, the top trending item on Twitter is “RIP Kanye West“.  Now I’m sure it’s very possible that The Louis Vuitton Don has passed, but Jeff Goldblum and I are skeptical.

What does this “noise” have to with Facebook?   Nothing.  Other than its raging case of Twitter-envy.

The original Facebook News Feed worked as a curator.  It knew that you didn’t want to search through each and every one of your friends’ profiles to figure out the big news of the day.  Just like working through my email inbox, I could read through all of the Facebook-supplied, juicy tidbits until I got to one I had already read, and then cross “checking Facebook” off my mental to-do list.  “I’m done,” I would think.  “I’m caught up. I’m in the know.”

But like the Facebook fiend that I am, it wouldn’t take long for fear to creep in.  “Hm…it’s been a little while since I’ve been on Facebook,” would lead to, “I wonder if there’s anything new going on,”  which would ultimately turn into a panicked, “Crap, I hope I’m not missing anything!”, and right back to facebook.com I would go.

But as Facebook started to feel the unwarranted heat from Twitter, the News Feed suddenly changed from a curated summary into a real-time, unfiltered activity stream.  Going even more Single White Female, Facebook organized a username land-grab, and even implemented their own version of @ replies.

Now this isn’t a problem when you’re just starting out on Facebook, but as the average social graph size continues to grow, it becomes impossible to read through absolutely everything.  Shouldn’t a friend getting engaged be given more prominence than Liz sending Eric a horse topiary?  With zero possibility of processing every bit of the unfiltered minutiae of my friends’ activities, there’s no fear of missing something, because you’re always missing something. Without that fear, checking Facebook slips a notch from being a must-do, to being a fun-to-do.

And that’s what the new Facebook homepage design hopes to fix.  Leaked earlier this week by a brand advertiser being pitched to by Facebook, it seems that they’re bringing story curation back to the forefront.

“Facebook is simplifying the user experience on the home page by introducing Top News and Recent Activity streams. Now, when users log on to Facebook for the first time in a while, they will see the most important stories that they missed while they were away. From there, users can navigate to the real-time stream and toggle between both views throughout their sessions. In addition to making it easier for users to view content that is most relevant to them, this change also speeds up the time it takes for the home page to load and makes birthday reminders more prominent.

Ultimately, Facebook believes these changes will increase engagement on the home page by surfacing more relevant stories to users.”

The emphasis added was mine, and it can’t be stressed enough.  Facebook is turning off the firehose stream of data, and returning to the role of uber-connected friend that knows all the best and most juicy gossip. If you don’t stay in touch, you’re going to miss something.

Facebook is bringing the “fear” back. And that should scare all of its competitors.