Showing posts with label mobile phones. Show all posts
Showing posts with label mobile phones. Show all posts

Saturday, February 05, 2011

Victory!

I thought that this would happen long before now, but I'm finally rid of AT&T!

I've been out of contract with them for nearly two years, and could have switched long before, but the forces of inertia and indecision kept me from doing so. This is largely an occupational hazard. Much of my job these days involves writing pre-loaded apps for mobile phones. That means we get to see and play with phones long before they go on sale to the general public; we often first get it six months before it ships, and several months before it's even announced. Particularly buggy phones can last even longer and may not ship at all, but that isn't the problem; no matter how cool any phone on the market is, odds are that I've worked on a cooler phone that I can't buy yet. Once that phone does come out, I've received the next generation, and can't bear to part with hard-earned money to get something that I know will soon be surpassed.

The end result: I'm probably the last person in San Francisco who's still rocking the original iPhone. (8GB, baby! Top of the line!)

Still, I've gotten increasingly fed up with AT&T, to the point where I was ready to pull the trigger even without having identified a suitable replacement phone. The service was OK back when I lived and worked in the South Bay, but now that I spend much of my time in the City, I just can't deal with it.

For a long time I'd been planning to switch to T-Mobile. In my humble personal and professional opinion, they're the overall best choice amount mobile carriers. Here's how it generally breaks down.
AT&T: Best devices. (This was even more true when they were the exclusive iPhone provider; even now, though, they tend to get first crack at the coolest new devices.)
Verizon: Best network and call quality.
T-Mobile: Best calling plans and most customer-friendly policies.

T-Mobile is the perennial underdog, and so they have to try harder, which they do. There's a bunch of stuff about them that appeals to me.
  • They're a GSM provider, which, among other things, means that it's trivial to switch phones. Now, granted, I haven't switched my phone in four years... but I like the idea of being able to do so whenever I want. 
  • Alone among major US carriers, they offer an unsubsidized phone rate that's cheaper than the normal rate. In other words, if you skip the free or discounted phone, you can pay less each month for service.
  • Along with the above point, they also make it easy to avoid getting a 2-year contract. As long as you provide your own phone, you can continue month-to-month. (You can do this on most carriers with a pre-paid plan, but that generally doesn't work well for heavy data-users like me.)
  • They have an unlimited data plan, which includes a 4G network that's available here in San Francisco.
So, late last year, I was all ready to switch to T-Mobile; I'd just grab an old phone for now, and then take the first dual-core Android phone that came out. But then, they pulled the rug out from under me. Their "Even More Plus" plan, which would let me bring my own phone and get a cheaper plan with no contract, was rescinded from their web site. Apparently, it's still available, but you need to go into a T-Mobile store to sign up for it. I know, I know, it shouldn't be that hard, but it was just enough of a hassle that I put off doing it for several months.

In the end, I landed with someone else: a small carrier called Simple Mobile. Simple Mobile is an MVNO, which means that they're run as an independent mobile company but use another company's wireless infrastructure. The most famous MVNO in America is probably Virgin Mobile, a prepaid carrier that runs on Sprint's network. Sprint phones and Virgin Mobile phones will get the same service whenever you make a call, but use different billing models.

Some Wikipedia research and a few Google searches revealed that Simple Mobile was:
  1. A GSM carrier
  2. An MVNO that uses T-Mobile's network
  3. A 4G carrier (again, using T-Mobile's HSPA+ network)
  4. Surprisingly cheap
All Simple Mobile's plans feature unlimited minutes, which seemed absurdly unnecessary to me. I'm currently on a 450-minute AT&T plan, and in any given month, I'll use about 40-50 "anytime" minutes, with another hour or two of nights and weekends. And yet, even with the unlimited minutes, the Simple Mobile plan cost just as much as the 500-minute T-Mobile plan that I'd been looking at. I'd bring my own phone, and pay $60 a month in return for infinite minutes, messages, and data. In contrast, today I pay $60 a month for AT&T-quality voice service with 200 messages (more than enough) and data that's technically unlimited but only on craptastic 2G EDGE.

I hate to waste food, and I hate to feel like I'm wasting minutes, but still, the math totally penciled out for me. And, again, Simple Mobile doesn't require a long-term contract, so if I found a better deal elsewhere, I could always switch again. So, away I went!

If you're getting a new number, you can do everything you want online. Fill in your details and they'll send you a SIM card in the mail. Once it arrives, punch some numbers into a web page, and you'll be set. Since I was porting my old number, I had to contact customer service. The wait was relatively long (maybe about 10-15 minutes when I called in the middle of a weekday), but once I got through, the process was painless: just provided my old AT&T account information, my new SIM number information, and I was all set. My service was available on my new phone after just a few minutes; incoming calls continued to be directed to my old iPhone for a while longer.

My next step is getting rid of this old phone. There's a website called NextWorth.com that looks pretty promising: you select an item to sell, answer some questions about its quality, and get a quote for its value. Ship it off and they send you money. I'm pleasantly surprised to see that there's still some demand out there for first-generation iPhones, so I'll be happy to make the sale.

It is pretty funny to reflect back on how T-Mobile messed this situation up... they were super-close to gaining me as a devoted customer, and would have collected a lot of money over the years from a customer who kept their voice lines almost totally free. Instead, by making it hard for me to buy a product that they sell, they drove me to a pseudo-competitor. Granted, I'm sure there's some kickback to T-Mobile since I'm using their network, but they're only making a fraction of the profit that they would if they still made it easy to buy Even More Plus plans.

As a final bonus: at long last, I can finally actually write apps for my phone. It's pretty absurd that for years I've been able to write apps for just about every mobile platform out there except the iPhone - I can write Java ME, BREW, Android, Windows Mobile... I can even do Symbian if you hold a gun to my head. Android is my favorite platform, and finally I can make stuff that I'll actually be able to use in my daily life.

Friday, July 28, 2006

Act Locally

I'm never on top of the latest breaking news, but at least a few of you also didn't know about this yet, so I figured I'd pass it on.

Google has released an updated version of its Google Maps application for mobile phones. If you haven't seen the previous version, you're in for a treat. Google has done a phenomenal job of converting its excellent mapping software to the mobile phone. They got everything right: it's feature-rich with items taken from the web version (including searching, getting driving directions, zooms, satellite imagery), and is well adapted to the constraints of a mobile device (easy and clear step-by-step driving directions, jumping between search results on the small screen). The number of cool use cases is pretty impressive. I open the phone, and it remembers where I was using it last, bringing up the Los Gatos area map. I type in "burger" to search and get back a bunch of results. I find Main Street Burger, and then press the "Call" button and instantly initiate a phone call to them.

I've been geeking out on this application for a while now; the new version adds even more to amaze. The single coolest addition is real-time traffic information. Just press # on your keypad, and your local highways receive another overlay: green for running on time, yellow for running slow, and red for backed up. Even more amazing, this is integrated into the routing algorithm: your driving directions now include up-to-the-minute traffic estimates.

So that's incredibly cool, although it isn't something I'll use that often (seeing as how I rarely drive to work and, when I do, it's almost always a smooth commute). Traffic info has a high wow factor, but I'll get the most mileage out of an improved favorites feature: the previous version had the standard "recent searches", which was nice, but this one lets you bookmark and name common addresses. Then, it's just 1 touch to center on that bookmark. It's not just locations, though: you can also bookmark routes! I could see myself, for example, bookmarking the route from home to SFO, then checking it to see whether I'm better off going up on 280 or 101 on a given day.

Anyhoo, cool stuff. It's available on Sprint and Cingular; if you have a data plan, it's totally free to download and use.

Some inside-the-beltway-commentary: obviously I'm a BREW guy, do or die, but I'll really miss things like this when I switch over to Verizon. The carriers who don't offer this generally have one of two reasons: either their technology doesn't support it (that is, they use BREW phones instead of J2ME), or their network doesn't support it (that is, T-Mobile has awful awful data channels).

The argument about technology not supporting it is a bit facetious, though. Yes, Verizon sells BREW phones, but the reason why is because they want to have total control over the programs run on their phones. This all goes down to the bottom line: Verizon would rather sell 1000 copies of Verizon Navigator for a monthly fee than have 1000000 copies of Google Maps running for free. I shouldn't complain, since that business model supports my salary, but it can feel frustrating to operate in a nickel and dime economy. Sprint takes the broader view, hoping that people will like the free stuff so much that they'll shell out $15 a month for the data plans. (And some people will pay even more for the premium games and applications.) Time will tell which strategy ultimately wins out. Personally, I'd be delighted to see a future world where free J2ME programs run on the BREW platform. The technology is already there to do it; it's a question of courage on Verizon's part, and I think it would be a shrewd move as well. Few people who haven't previously experienced mobile applications will shell out money for them; free high-quality applications like Google Maps are a great way to get people used to using their phones like computers, and once they make that transition, far more of them will convert to data users who want Verizon's BREW content.

And what does Google get out of all this? First off, remember that Google has never been reluctant to offer free services while experimenting with new products and technology. In the long run, it will probably support this through advertising. It'll be interesting to see how that happens - obviously, you won't have as much screen space to support ads as you do in a web browser, but then again this could be a place where Google's text-only ads really shine. I can imagine me typing in "burger", and along with my results having a tiny crawl at the bottom calling out a local burger restaurant I haven't been to yet. It's a brave new world out there.

Download the application by opening your phone's web browser and going to http://google.com/gmm. If you'd like, you can take a tour of the application online - keep in mind, the interface is much nicer in the palm of your hand than the end of a mouse.

Monday, June 12, 2006

MoMoMo

As I think I've mentioned before, I occasionally attend Mobile Monday, which is a monthly gathering of Bay Area mobile developers. I decide on a case by case basis whether to attend, depending on the location and the topic. (Mobile Search at Google? I am SO there! Funding a Start-Up in Berkeley? Eh... pass.) This week the topic was the current handset market, with hard data from researchers about what phone models were out there, what their capabilities were, how different carriers and manufacturers compared, etc. It's a topic that (a) is somewhat relavant to my current work, and (b) I don't know a whole lot about. So, after riding back home (oh yeah, I'm riding to work again), I showered, hopped in my car, and drove up to the Motorola plant in Sunnyvale, who was hosting the meeting.

A little background - the same two people have been organizing most meetings, which are very ad-hoc. They depend on donations of space and supplies for the meetings. Sometimes, as with Google, it's really classy - they gave us a nice big conference room and their cafe catered in some nice appetizers and fancy desserts. Others are more ordinary - I went to a meeting at AOL held in a regular conference room, where a local headhunting firm had ordered lots of pizza for everyone.

In lieu of my normal post, I would like to transcribe verbatim from my notebook the comments I wrote to myself while sitting on a chair in Motorola's cafeteria, waiting for the meeting to begin.

Mo Mo Mo - Mobile Monday Motorola
Topic: Phone hardware market and more
Almost nobody's here! It was hard to find, though
It doesn't help that we're in a cafe, with food tantalizingly out of reach behind glass cases, along with signs that say "HUNGRY? We can help!" The joke being that, while perhaps they could help, they choose not to.
Man.... I will be very tempted to leave if they start this without any food. I do not need this. I rode 15 miles today.
It's also cute how the email made a point of saying that we needed to get here at 7 sharp. It's well past that, with no word on when we're starting.
If I'd stayed home, I'd be eating my last Lou Malnati's now.
As it is, I could run my errands and still get back in time to eat enchiladas before 8. No "professional development" is worth this.
Food food food foof [sic] food food.
If I'd started lunch at noon as planned, instead of 11:58, I'd be 2 minutes less hungry than I am now.
OK... plenty of people now. Maybe even too many for the chairs laid out. Nobody else seems as furious as me, though. No, they're happily standing, chatting, mingling, networking, while I'm over here, slumped over in my chair, trying to distract myself from hunger pains by writing about how hungry I am. This isn't the smartest thing I've done.
Seriously, though: what's the deal? I've had this fantasy that someone ran out for pizza. Maybe they haven't started yet because they're waiting for it to get here. Yeah, right!
Oh, sure... they're waiting until NOW to set up the projector? Geniuses!
I propose an armed insurrection.
There are more women here than I expected. Still just around 10-15%, but still. I wonder if more women attend certain topics?
My rage fills me. My hunger consumes me. Which will fall first, my mind or my body? That will be tonight's entertainment.
They just gave the 5-minute warning. "Yay." No food, I guess.... what a shame. I will destroy everyone.
Now the question: do I leave now? Seems like a waste. They haven't said for sure that we aren't having food, I guess.
Finally starting.
Next month may be messaging!

[End of pre-meeting notes. I won't bother transcribing my notes from the actual meeting.]

(There wasn't any food. I ended up eating an enchilada much later than I would have preferred. The meeting itself was quite useful and informative.)

(I promise this will be my last food-oriented post for a while.)

Wednesday, June 07, 2006

I Love the Girls and the Money and the Shame Of Life

I've been looking forward to the DevCon for a while. Last year, while I was still with Nexgenesis, I attended the Sprint Application Developers Conference, which focused on developing J2ME applications for Sprint users. It was pretty interesting, even though most of it did not really apply to me since most of my development was in BREW. Still, it's always good to expand your horizons, and conferences are great for getting a taste of what the Next Big Thing is going to be.

From talking with folks at Rocket Mobile about it, it sounded like the BREW DevCon had more of a party atmosphere. The people who had gone before had some entertaining stories about the fun stuff that had happened in previous years.

Last year, due to a major crunch at work, nobody was able to attend. This year, Wayne wanted to make it up to everyone by sending the whole company. Unfortunately, a few projects were under a lot of pressure, and so a lot of people were not able to go. Those of us who were still fine headed out on Wednesday morning. I did my standard VTA to the airport thing. Most people were leaving on the same flight, so we hung out in the gate area together, and took over several rows when we boarded.

Flying in to San Diego was really nice. As I said before, this was my first visit there ever, and from the air it looked as beautiful as I expected, with the striking blue expanse of the Pacific Ocean leading up to clean beaches and the gleaming towers of downtown. The airport itself wasn't quite as good - it's nice and modern, but the layout is a little awkward, we had to walk quite a ways to get to the taxi area and then needed to wait too long to be serviced. Neither the Hyatt nor the conference were running shuttles, which really bemuses me, since everyone waiting for a taxi (and there were more than a few of us) were obviously there for the con.

The conference officially runs for Thursday and Friday, but there were "pre-Conference" sessions on Wednesday. We speculated whether we'd actually make it there in time for the first one, which started at 1PM. A fleet of taxis eventually arrived, though, and we did the five-minute ride to the Hyatt. This was a very nice, huge hotel, and had been overrun with nerds. I was rooming with Josh, who does QA for my team and is the youngest RM employee. We checked in, deposited stuff in our room (a corner!), then headed to the conference area to get checked in. We got some nice swag including a T-shirt and a backpack, along with the customary notebook and designer pen.

It's kind of amazing just how much time I would spend thinking about food: when we were eating, what we would be eating, how much I should eat, how it tasted, whether there would be dessert, where dessert would be, and so on. I think this was mainly due to my unpleasant realization on that very first day that I would not be eating any lunch. The rest of the meals would be provided through the con, but since it hadn't technically started yet, I was on my own. I realized this too late to acquire any food, so I stood around complaining with Greg and Josh for a while until my conference started. I attended the BREW uiOne introductory sessions; I'd poked around uiOne a little before, and others in our company have done quite a lot with it (including the initial work for Samsung's Sprint handset that was featured during this conference), but hadn't done any actual coding. It was a pretty interesting session and well-structured, starting with an abstract overview in the first session down to plenty of real code examples in the second one.

I was pretty hungry by the time it was all over, so I made a beeline for the Partner Pavilion. This was a huge ballroom that had been converted into a showroom, filled with booths from software developers, OEMs, outsourcers, Qualcomm teams, and more, all boasting their wares. More importantly, from 5-7 it would be the location for Happy Hour. I grabbed some Dos Equis (hey, if I'm that close to Mexico, do I really have much of a choice?) and loaded up a plate with plenty of crackers and cheese and fruit before hanging out with Chris and Shane. I was a little surprised to be carded for the beer, but it wouldn't be the last time; over the course of the conference I was carded more times than I have been in the previous year. Which seems odd; I had a badge, and one would think that someone old enough to work as a developer would probably be over 21, right? Well, someday I'll probably look back on this and take it as a compliment.

I wandered around the showroom for a while, checking out the various offerings. As with most of the conference it was very fluid: I would meet up with various groups of RM people, walk with them a while, then we'd split up and go separately or meet with other RM folks. One of my favorite things was getting to talk with people who I've seen around the office but haven't interacted with much before; I had a nice long chat with Richard, who is a new developer on the Published Apps side.

Running out of steam, I went back to my room and flipped through my schedule, planning my course for the next two days. Jim had mentioned before that he wanted us to split up to cover more ground, but I hadn't heard any specific schedules set, so for each slot I picked the one I wanted to attend, with a few alternates just in case it was full or we already had too many people there. Josh came back and we headed out to the Welcome Reception, held in the Embarcadero waterfront park.

This was a really excellent setup, with a variety of food stations scattered throughout, plenty of large tables, and stretches of entertainment. There was a variety of Mexican food, Italian food, roast beef, and maybe more that I missed, along with an excellent dessert selection. Charles and Ray had already arrived, and together we staked out a table. We took turns filling and refilling our plates as people came and went... again, fluidity was the watchword of the conference. At one point we were joined by John Sullivan, Wayne and Sheila, but by the time I thought to take a picture John had already left and the three of them weren't ever together again. I did get some other good shots here, though. I had some more Dos Equis and got carded again.

After it got dark, Chris, James, Josh and myself decided to wander and see if we could find the "rides" Sheila had talked about. She was either drunk or had gone to another place, we couldn't find any rides at all. What we did find, though, was still pretty cool: cariciturists, a beatboxer, some cool green-screen music-video things, more bars, and a big old inflatable balloon thing. We posed for a hilarious picture (few things are more entertaining that computer science professionals attempting to look cool) and the evening generally degenerated.

Rajiv and Graham had stayed behind to take care of some last-minute business, but arrived just as we were heading out. Some of the guys were going out again for more drinking, but Josh and I were operating on too little sleep so we went back and crashed. I was briefly awoken by what sounded like a freight train derailing, then again by my alarm. Barely conscious, I stumbled into the bathroom and got ready for the day.

Why was I up so early? Primarily because, as previously noted, I was obsessed with food. Thursday started with "Developer Breakfast Roundtables," where people sit at tables and discuss stuff while eating. It ran from 7-9 with the warning that "Seats fill up quickly, so come early!" Horrified at the thought of needing to wait until noon for my next meal, I was willing to get up early (though, granted, with about 8 hours of sleep due to my early bedtime) to ensure a seat at the table.

It turns out that I didn't need to worry. Breakfast was not exclusive to the Developer Breakfast Roundtables. I grabbed a plate, plundered the continental spread with a croissant, fruit and danish, then joined Shane (and later Eric and Ray) for the meal.

The conference officially started at 9 with a welcome from Peggy Johnson, the President of Qualcomm Internet Services. She was wearing capris, and actually looked pretty good in them, thus destroying my theory that no real person ever looks good in capris. Oh, but wait: before she took the stage, we were treated to an extremely high-energy hip-hop song called "BREW Your Way." It was pretty special. Lots of breakdancers, rapping, drumming, crazy video images, duelling singers... it was simultaneously awful and exciting. Peggy took the stage after they left, and ensured everyone would be uncomfortable by attempting to explain to us the "lingo" used in the song. "When they say 'My BREW is Tight,'" she helpfully explained, "That means, 'My BREW is really good.'"

The welcome and keynote were held in the Elizabeth Ballroom, a simply massive space. I sat up front along with Ray and the other old-timers, but those further back were treated with rows and rows of enormous video projectors that ensured everyone could see everything. Even people who had been to the conference before were impressed by how big it all was, and I heard a lot of reminiscing about the old conference before it moved to the Hyatt.

Peggy introduced Dr. Paul Jacobs, the CEO of Qualcomm, who delivered the keynote. It was... a really odd experience. He's a very fine speaker, and showed off a lot of impressive statistics (BREW developers made over $750 million in 2005!), but the highpoint of his speech was showing off something called "Creatures." The idea was sort of cool, basically they're network-aware social-networking applications that live on the phone and are geared around commerce. He gave an example of Creatures being used to remind you of a friend's birthday and suggesting what to buy him, or letting you know what music your friends like so you can be a great DJ at a housewarming party. It's the sort of thing that's guaranteed to generate a press release, but for the developers out there, it was really dumb... it was clearly just a series of screenshots, there was no actual application there, nothing real to show off. It might prove to be something other than vaporware, but it felt curiously insubstantial to make the show's centerpiece.

It was only the centerpiece for a few minutes, though... after the keynote, we never heard about Creatures again. Good riddance to bad rubbish. Dr. Jacobs was followed by this long-haired executive from Sony BMG, which was a pretty interesting talk, in no small part because of Rocket Mobile's association with Sony. He talked about how digital music sales are rapidly catching up to physical sales in the US, and have already blown past them in much of Asia. Digital music includes iTunes and stuff in addition to ringtones on mobiles, but it's still impressive. It's a section of the industry that I'm not too plugged in to so it was nice to get some more information about it.

Staying for BMG meant I had missed out on the first half of the day's first technical session. I had planned to attend the Developer Awards Ceremony - RM wasn't up for anything this year, but it sounded interesting and there were some cool apps on deck. I ran into Jim in the interim, and he suggested I attend the Advanced TrigML session, so I did. The room was totally packed; I had to stand out in the hallway for the first bit, finally making my way in when others left (presumably to attend the awards ceremony). Having done one UIOne course for the day (or at least part of it), it made sense to follow it up with another, so I finished up the morning with uiOne Actor Development. Unlike Cathy, who attended both sessions, I thought the Actor session was more interesting. Then again, I tend to think that low-level C code is intrinsically more interesting than UI, so I may not be the best judge. In either case, by the end of these sessions I felt like I had a really good grasp of uiOne, and feel fairly confident that I'll be able to use it if the situation demands.

Up next: Lunch! Lunches were pretty good both days, your standard sandwich-plus-potato-salad-plus-fruit-plus-chips affair. I'd lost track of people after the Actors session so I wandered around a while, hoping to find some people on the lawn, but failing. I eventually located a table that held Cathy, Sasha, Erik, and Peter, who was a friend of Eric's when they were at CMU together and who has worked at Qualcomm for over a decade. We had a nice long conversation, I learned a lot about San Diego from Peter and shared my enthusiasm at moving to the west coast.

We split up and I wandered some more. My wanderings took me back to the Partner Pavillion, where dessert was served. And what good dessert it was! A wide variety of tasty cakes tempted. Food quality waxed and waned throughout the conference, but the desserts were dependably delicious.

That afternoon I had lined up my "fun" sessions for the week. The first was "Dirge of Cerberus Lost Episode - Final Fantasy VII." I was pleased to find Shane attending as well, which helped me feel like what I was doing wasn't totally marginal. And it really wasn't. This was a case study on translating the FF universe into the mobile space; the two panelists were Kosei Ito, a producer from Square Enix, and Alex Caccia, the COO of Ideaworks 3D, who were SE's partners. All the content was really interesting. For those of you who don't know, Asia in general and Japan and South Korea in particular have far more advanced mobile phones than we do here, and they are generally a generation or two ahead of us. Japan actually had a Final Fantasy cell game (Before Crisis, also FFVII-related) back when most people here thought "Breakout" on a cell was pretty cool. There was a lot of conversation about the different expectations of user groups, and also about how SE was able to preserve the hallmarks of the FF series, including impressive cutscenes.

Oh, I should probably mention here that Ito-san (or is it Kosei-san? I can never remember) spoke entirely in Japanese; there was a translator who handled the English part. That was really cool. I couldn't understand anything he was saying but it sounded great.

Back to the content: the technical things they talked about were really interesting, at least to me. Rather than download the entire game at one, subscribers were basically downloading an engine, and the content was streamed onto the handset as needed. This keeps space available on the mobile, and with Japan's advanced 3G network, this didn't really require any latency. Similarly, they tried to be smart about the graphics: they carefully chose palettes for objects at different resolutions so, for example, an enemy may have 8-bit color when on the horizon but a full 24-bit color when standing right in front of you. They could swap these models in and out to achieve the optimum balance between speed and detail. There were other technical solutions they covered, but those were the highlights for me.

Their information on the business front was also impressive. On the very first day Beyond Crisis launched, 1.6 MILLION people downloaded it. This is a staggering number for a cell-phone game even in Japan, and unheard of in the US. Most of what they showed us this day was from Dirge of Cerberus, a more recent game that is planned to actually get a release in the US at some point. Unlike BC, which really stands alone, DoC is being released in tandem with a PS2 game, with both featuring Vincent from FFVII. Both games are action shooters, but the restraints on a mobile phone (small screen, poor controls) required them to radically rethink the mechanics of the game. In the end, the mobile version of DoC is designed to reward the player for planning and decision-making, as opposed to twitch reflexes. The videos they showed were simply amazing, playing out in real-time with impressive gun battles, but you could see what they were talking about: the playing field was primarily a plane, and movement generally followed a grid, so while it looked very smooth, aiming automatically followed from movement.

Tangent time: If you have a cell and enjoy gaming, you might want to check out "Doom RPG". This is a mobile game written by John Carmack of iD, and is essentially a turn-based FPS. It's very well-done and a lot of fun. I bring it up here because Carmack took a similar challenge (how to bring a shooter IP to the mobile) and came up with a completely different solution (change the play genre while keeping the setting, plot and themes). Carmack's approach may be more interesting, and is virtually a necessity in the current US market where only a fraction of phones are remotely capable of supporting a real-time action game; Square Enix's approach is more technically daring, difficult, and probably represents the future.

Back to the session (didn't I already say that?): The Ideaworks guy talked a fair amount about his company's proprietary technology - not saying how it was implemented, of course, but walking down a list of what it accomplished. It included extreme compression rates, the cool resolution-swapping trick, some special audio things and advanced caching algorithms (so you don't need to stream additional content when staying in the same area).

Q&A was good, although I get the impression a few things got lost in translation. Someone asked about what happens if the user loses a connection while streaming data, and Kosei's answer was basically "Streaming lets us keep the amount of data on the handset to a minimum."

All this was very interesting, but arguably the highlight of the panel were the demo videos and trailers they showed throughout. I'm a bit of a Final Fantasy nerd (though not to quite as great an extent as, say, Ultima or Baldur's Gate), and it was really exciting to see all my old friends from FFVII in action again.

I had a good long chat with Shane afterwards. I hadn't realized he was a gamer, and we reminisced a bit about our favorite games of the past. We both are into RPGs, and he's currently slowly working his way through Oblivion. He mentioned that there actually used to be a Neverwinter Nights game for mobile phones that he thought was pretty good; it may have been on the T720, and also used the same streaming strategy that Dirge of Cerberus uses. He also talked up GameFly and how much sense it makes compared to buying a game.

The second afternoon session was also planned as a fun one, though of a slightly different sort. The title was "LBS Architecture for Security and Privacy." This is another area that RM really isn't involved in, but the short description made it sound like it would tap into a lot of the digital liberties issues that I'm most passionate about. I was not disappointed.

The main speakers included John DeAquiar from Autodesk, who represented the carriers' interests, and Rob Whitman, the CEO of RiffWare, who represented developers. To provide some background to my readers: LBS stands for Location Based Services, and for many years now has been the Next Big Thing in mobile development. Think of it as a GPS in your cell phone, though it's possible to have LBS without a GPS. With a bit of thought you can come up with the benefits this might offer: Google Maps with your current location displayed, a geocaching program, a friend finder, and all sorts of other stuff. With a bit more thought you can begin to imagine some potential problems and why some people might be reluctant to use it: what if other people can also find you? What if some of your friends don't want to be found?

John briefly introduced the topic and defined his terms: "security" means ensuring that only authorized people can access data, and "privacy" means users can control who gets to see the data. He pointed out that security is a pre-requisite for privacy: it doesn't matter how good a company's privacy policy is if people can steal their data. Then he talked about the three security architectures from the perspective of the network: "Trusted," "Mostly trusted," and "Untrusted." You can imagine these as points along a continuum, with very easy but insecure at the top and very hard but secure at the bottom. In the trusted case, any program can do anything. In the mostly trusted case, the program needs to authenticate itself with the network (as with a login and password), but once it passes that it can do anything. In the untrusted case, every request a program ever sends the network is considered suspicious, and the network relies on its internal policies to determine whether to authorize that request or not; it also performs additional challenges to ensure that it is dealing with the actual client and not a "man in the middle" attack.

After covering all this, John concluded that everyone should run untrusted networks. It's a pain for both carriers and developers, but is the only way to ensure security, and the carriers are so exposed to financial liability in the event of breaches that they can't afford to do anything else.

Rob made it clear off the bat that he wanted to be controversial and provoke discussion. His big thesis was: carriers are already capable of tracking you everywhere. The government can get that information any time you want. By carrying a cell phone, you are already giving up your privacy. That said, do programs' privacy or lack thereof really matter? In other words, should a developer need to jump through hoops to ensure nobody can find you, when an entity is already tracking you?

He also briefly covered some possible ways to enhance privacy. For example, in a mapping program, instead of sending a request for a map in San Jose, the program might simultaneously request San Jose, Chicago, and Boston; that way, someone monitoring your IP traffic wouldn't know what city you were in. Similarly, a phone might pull down a bunch of data in advance, then operate statically on that data instead of transmitting its location and requesting specific data. The main goal here is to eliminate broadcasts of potentially private data.

The Q&A was relaxed and wide-ranging. There was a fair amount of discussion over EULAs, which nobody reads anyways and which are impenetrable on a mobile screen. Can we really rely on EULAs to disclose what aspects of privacy we may be giving up? Several people thought it would be better to build it into the program itself, for example by asking the user every time you would broadcast their location.

My last session of the day was far more practical, and it covered the BREW Dispatcher. BREW is a single-threaded, event-driven programming environment, and as such its architecture is quite a bit different from Java or even most desktop C++ applications. I've gotten a good handle on it, but this is one of those areas where I felt I could stand to learn more, so I headed over to the session. At least, I tried to. It was held in the Randle conference rooms on the fourth floor, and I proved to be uniquely unqualified to find them. I finally tracked it down and walked in just as it was starting, fortunately grabbing a chair next to Rajiv, my previous officemate.

Most of the session covered the use of IThread, a 3.0 API that adds virtual threading support to BREW's architecture. The presenter (a Qualcomm director) talked about how it was implemented and what it could or could not do. (Bottom line: it's best used when porting existing code that takes "blocking" actions on resources such as network sockets; it can also be useful for heavily stack-based ports because an IThread's stack is actually on the heap. [Yeah, I know.] Since threads aren't pre-emptive, you need to be very cautious about starvation and other issues.) He also dug a bit more into the implementation of BREW's event system, which is more of what I was interested in, and contrasted use of ISHELL_Resume with AEECallbacks. He really likes callbacks, and think that people should generally use them.

There were a ton of questions and some of them were pretty heated. Someone asked about when pre-emptive threads would come; the word was "it's in the planning stage." Rajiv essentially accused them of draining battery life by implementing a polling loop for their events; he dodged the question and talked about the advantages of the event-driven model. Others chimed in with their concerns about performance. I really wanted to ask how timers fit into the event model, but since nobody else was mentioning them I figured it was probably a stupid question.

After the session closed, Rajiv, Charles and I spent a good ten minutes or so talking about Rajiv's question. Charles pointed out that, while the pseudocode the presenter had shown displayed the event reactor as a while loop, in reality it exists outside BREW in the OEM layer, and may even reside in hardware. That's where the question comes in, because if it's hardware-driven, it isn't polling, and won't have nearly as many no-ops that drain battery life; if it's in software, it'll cause all sorts of headaches. Rajiv thinks that the VZW Razr may implement it in software because the battery life is poor, but the bottom line is none of us know for sure, and there really isn't anything we (or even Qualcomm) can do about it. (My thought is that, since Qualcomm makes the CDMA chips, they'd be foolish not to offer the hardware capabilities to the OEMs, and the OEMs would be foolish not to use it.)

It was now around 5:30, about 90 minutes before the start of BREWFest. I was sorely tempted to walk over to the Hall of Champions in Balboa Park where it was being held: it was a gorgeous day outside, I hadn't really been anywhere in San Diego besides the airport and hotel, and I was starting to feel the pain of too little exercise. Judging from my map it was just over two miles, a very reasonable distance for a walker like me.

I swung by my room first, though, and ended up hanging out with Josh. Josh is an avid cyclist of the downhill-racing and stunt variety; he broke his... foot, I think, last year when he failed to clear a ravine. Anyways, he had downloaded a video that showed incredibly talented trick cyclists doing all sorts of crazy stunts, from extreme downhill racing to city tricks (hopping from bench to bench, riding on railroad tracks, jumping from one side of a bridge to the other, and so on). That took us up until 6:15, when buses were supposed to start leaving for Balboa, so I decided to skip the walk and just ride.

Turns out that was a smart move. Unbeknownst to me, only people boarding the buses would be issued the bracelets and drink tickets necessary for the evening's entertainment. If I'd walked there I may well have been turned away at the door, which would have been awful.

A Rocket Mobile crew seized the front quarter of a charter bus and excitedly made our way down to the Hall of Champions. The event had been built up as the social highlight of the conference, its promise of food, drinking and music gripping all of us. The location proved to be pretty cool. The HoC is a sports museum, apparently the largest of its kind not devoted to one particular sport; the walls were covered with various balls, bats, signed photos and other memmorabilia, while display cases lined the floor. There were no single large gathering spaces, but instead a variety of tables and stations spread throughout three floors.

The food was... meh. After the previous night I'd held high hopes, but this was merely mediocre: bowls of jambalaya, some sad slices of chicken, and not a lot else. I quickly lost sight of everyone, then touched base with Arvi, Raffi, Richard and Rajiv; we grabbed two tables and pulled them together in anticipation of a large RM crowd settling, but after several minutes it became clear we were on our own. This was doubly unfortunate because it invited visitors, including one strange guy who introduced himself and sat down. I forget his name and the company he worked for, but he was one of those people who are really friendly while rubbing you the exact wrong way. He noticed we worked for Rocket Mobile (which led to a funny moment where it became obvious that Richard hadn't met Rajiv before - understandably, since they're on opposite sides of the building and Richard's new, but still pretty funny) and mentioned he'd attended Ray's session earlier. "It was pretty good," he said, "Except that I totally disagree when he says that BREW is easier to port to than Java." This was something so completely unlike what Ray would say that I didn't know how to respond - I wanted to say "You must have misheard him" or "He did qualify that statement, correct?", but at the moment I was trying to avoid conversation. After I'd cleaned my plate Rajiv asked, "Hey, Chris, do you want to go get dessert?" I said "Sure" and we left. Rajiv leaned in conspiratorially and said, "And not come back." We laughed and moved on to greener pastures.

The beer was freely available but mixed drinks cost one ticket each. We had each been issued three tickets and a black market quickly sprang into action, with teetotallers selling their tickets for favors. We also found that occasionally a bartender would forget to claim a ticket. All that to say, there was a decent amount of alcohol in play. I started the night with Heineken, then moved on to my cocktail workhorse of rum and coke. (I know that "Beer then liquor will make you sicker, liquor then beer you're in the clear," but I've never been able to do this. I'm always thirsty when I start drinking so I want beer; if I do work in liquor, it always comes at the end after I've got food in my stomach.) We found a dessert table, which was excellent as always: soft chocolate chip cookies, a nice chocolate cake covered with warm strawberries, and a sort of apple pie ice cream cone. I sampled each multiple times over the course of the evening.

Rajiv and I located another table where Greg, Eric, Cathy and Sasha had set up. The fluidity continued as the night went on, and I got to spend time with each of my co-workers over a variety of locales: the tables, the Sprint "Oxygen Bar", the chillout room, and the funky karaoke room. I didn't mingle much outside my company, and I'm not entirely sure why. Probably partly because I'm not super-sociable to begin with, particularly around strangers; partly because I had been scared off by my earlier meeting with a non-Rocket-mobiler.

Many levels of inebriation were on display; nobody from our company totally lost it, but certain people were much more enthusiastic about, say, karaoke than others were. Jim proposed that everyone on his team sing karaoke, in ascending order of age. (Coincidentally, this would have put him last in line.) Josh, our baby, announced that his voice was high enough for him to sing The Darkness' "I Believe in a Thing Called Love." With very little argument he persuaded Graham, who is also very young, to accompany him. We were hanging out in the karaoke room for them to start when the DJ announced that Earth Wind & Fire were getting ready to take the stage. We all headed outside for the concert.

Every year, BREWFest includes a once-big band for a concert. Previous years have featured Huey Lewis & The News, The B-52s, and Kool & The Gang (who I actually would have enjoyed seeing). Apparently, ampersands are a big factor in determining which band gets to play. I couldn't name a single song EW&F had done, but, hey, a concert's a concert, and I'm all about going with the flow. We gathered together in a big.... hm, it was probably a parking lot by day? I don't remember the surface too clearly, but it was probably paved. Anyways, we gradually reconstituted until we had close to a dozen RM people together. A few people (Cathy and Eric) seemed excited for the show, the rest of us were hanging out and cracking wise.

One nice thing about a concert like this: there's no opening act, no MC, no self-promotion. The concert was meant to occupy a block of time in the evening's entertainment, not be an end unto itself. They took the stage astonishingly close to the advertised time and launched into a high-energy rendition of a song I would probably know if I were 20 years older. I still enjoyed it - the band wasn't phoning it in at all, and did all their choreography and performance with full passion. By far the highlight was their bass player, who is probably an original member. He was wearing a see-through shirt over a wifebeater along with tight leather pants with fringes on them. He strutted all over the stage, emoting more than anyone else I have seen recently, and was absolutely mesmerizing.

After a while the RM crowd started to get into it a little. Cathy worked her way to the front of the stage, Eric moved in a bit closer, and Graham said, "At first I was hating on these guys, but this actually sounds pretty good." During one slow song I pulled out these funky things we were given in our drinks - they look like ice cubes, and change colors when placed in liquid or held in your hand - and shook them over my head in rhythm with the song. The rest of the RM crew, who had been collecting them throughout the night, joined in as well. I felt an odd sensation of accomplishment.

During a slow song we worked our way out of the crowd towards the back, where a few tables and chairs were scattered. Jim had successfully smuggled in a bottle of liquor and we did shots around a table - he'd grab a cup, pour it discretely under the table from under his jacket, then set it on the table and do another. I only did one but it packed a decent punch. If possible, the mood grew even more relaxed, and we made our way to the chairs and I started asking my hypothetical questions.

After the show finished we headed back in. Some of us camped out in the karaoke room for a while, enjoying singers with... diverse amounts of talent. Some were very good. I was disappointed that Josh hadn't been called yet, though. After a while I got a text message from Jim - "Food and oxygen downstairs." I grabbed some of the ladies and headed down. I paused on the way to stare, impressed, at the dance floor: they had cleared out the center area where most of the food tables had been and set up a pretty amazing venue, with flashing lights and pillars and a really good sound system. The song selection was kind of pop-y as opposed to my preferred electronic dance music, but still sounded really good. After a brief pause I rejoined the others en route to the basement.

Sprint, which has traditionally been on the other side of the fence from BREW developers, was trying to ingratiate itself: they ran the Java Bar (clever name!) in the pavilion, serving high-quality coffee throughout the day. At BREWFest they ran an oxygen bar. I'd heard of these before, and earlier in the night had talked with Ray after he did it. He said that he got really agitated when he was on an apricot blend, but when we switched to some calmer flavors it got better. Jim was already hooked up to one station when I got there, so I took another and plugged in.

"Oxygen Bar" sounds pretty exotic. Essentially, what you have is a set of chambers filled with various liquids. Through some process that I don't really understand, pure oxygen runs through the liquids, absorbs the odors, then runs through tubes into your nose. I stayed on mine for several minutes, playing with the various flavors, but the only real difference I noticed was in the smell; I was kind of hoping for some of the mood-altering that Ray had experienced, or the consciousness-altering that the name had initially suggested to me, but nope: just different smells. Still, it was a nice break. Jim and I took pictures of each other, though he may have cheated by getting me while I still had rubber tubes in my nose.

We sat around and chatted a bit more, gradually acquiring more people as we seem to do. Someone came down to report that Josh was about to finally sing, so we high-tailed it back upstairs.

This was probably my high point of the night. It's just very, very funny to see people you know make spectacles of themselves in public. Josh and Graham were joined by James, another young'un, and they didn't just sing, they PERFORMED, with dramatic poses and dancing. I captured the entire song on video, and it is a treasured possession of mine.

Very soon after they left, Eric was called up, and he did a very good performance of CCR's Proud Mary. I took a video of this one as well, and shortly after it starts, you can see Cathy and Graham dancing into the frame. A great time for everyone. Cathy was called up later for The Beatles' "All You Need Is Love" (requested in honor of Rajiv, who was leaving for India to get married, but had left before she was called), but she was expecting to get more help than she got, so turned it down. Jim put in his name for a song, but the DJ announced that the night was almost over, so instead we headed down to catch the last few minutes of dancing.

Like I said, it was a really sweet setup. I'm not sure why, but the number of females present were much higher than what you would have expected based on what I saw during the conference. Whatever the reason, it was a lot less scary than hundreds of male nerds dancing would have been. We got down there for the last half of the Black Eyed Peas' "My Hump," an incredibly catchy song that I will never, ever be able to sing out loud. This was followed by the last song of the night, Bob Marley's "Every Little Thing Gonna Be Alright." It was fun. I enjoy dancing, and this was the perfect setup: no partners or couples or special steps, just a mass of people moving around to a beat.

It was a little after 1AM when we left. We were still really high from the event, and probably scared our bus driver - the whole way back to the hotel we were singing and doing percussion for the Marley song. There was a lot of general excited chatter, and I'm sure many things were said that were immediately forgotten.

I would like to take this moment to observe that the hotel's rooftop pool closes at 9PM. Therefore, it is logically impossible that we would have gone swimming in our boxers until after two o'clock in the morning.

Once again I woke up bright and early. Well, not THAT early - these days, 8AM is actually sleeping in for me. I did a shower and got breakfast, chatted with Eric, Ray, Shane and Richard, then headed in for the day's keynote.

The keynote was given by Peggy Johnson, and while she has been involved in every conference this was apparently her first actual keynote. There was no extravagent show opening it up, and she launched directly into the meat of her talk, which was "Exploring the Evolution of Data Services." It was supposed to run for 50 minutes but was much shorter. She gave up the stage for a representative from Telecom Italia, who gave a passionate speech that I somewhat understood. It was actually pretty cool from a market perspective; he talked about how the company was combining their landline and mobile divisions under one umbrella and encouraging convergence through unified portals and, eventually, content access. Europe is another area that's ahead of the US in mobile usage, and it was good to get a look at what was happening over there.

My next session was "Preparing for the next generation of BREW." At least, it was supposed to be. I got a call from Jim right before the session started about an emergency back at the office, so I grabbed my bag and dashed out. I ran into someone I had interviewed with at WeatherNews, which was unexpected and really nice - he said that I was one of their top one or two candidates ever and they were disappointed to not get me, which made me feel really good. We exchanged business cards and I excused myself before dashing off. Trying to be clever, I had checked my suitcase at the bell desk in the morning; unfortunately, I had put my laptop in there, so I needed to reclaim it to do work.

After taking care of that I went back down to the pavilion, which offered free wireless and a "Laptop Alley." I plugged in, saw my cell phone had run out of power, swore, then hopped on AIM and started contacting people. Everything worked out, which was good. Naum kept me company for a while, and once everything was under control I stumbled upstairs to get food.

Friday's lunch was similar to Tuesday's, tasty and relatively simple. After eating we returned to the pavilion again to sample the desserts, a different but equally tasty array of cake. I was summoned again to do some "real" work, and sat out the next session while investigating and coding.

I was now moving towards a moral dilemma: should I stay or should I go? The last session ended at 3:45 and our flight left at 5:55, which felt a little tight to me, especially given the horrible taxi situation on the way over. I loitered in the lobby for a while, hoping to find other nervous people to show up. Charles appeared and shared my concerns, and together we convinced Eric to leave with us. Sasha and Cathy were already ready, and when we ran into Wayne they bluntly told him, "We want to go home!"

So we took our taxis to the airport, checked in, and hung out. I found out that, while staying for the last session would have cut it close, leaving when we did had brought us to the airport way too early. Still, there are worse places to kill time than the San Diego airport. Once again we took over a section of a building, and as other Rocket Mobilers trickled in our numbers swelled. It was a final, low-key resolution for a hectic few days as we amiably chatted, shared the highlights of our time, or stuck our noses in books and earphones into ears. (I also found out that Ray just started reading The Big U, which made me happy. As I think I've mentioned before, this may be Stephenson's most underrated book.)

I sat next to Jenny on the flight back to San Jose. Once again I found myself giving a little spiel about my thoughts on moving to California. She has worked as a consultant in the past and worked all over the world, so we talked quite a bit about her experiences in Europe and Asia. I've done so little travelling outside the US, but I hope to increase it.

And, just like that, we were back! I rode the train back home, stumbled inside, cooked up some soup and soon went to bed. Then went back into work on Saturday, but that's another story. It's been about a week since I first headed out there but already it seems far away, a distant happy memory. I learned a lot, I grew a bit, and I had a heck of a fun time. It was really great of Wayne to send as many of us as he did, and I look forward to returning in the future.

For pictures, check out the Sprinkles.

Thursday, October 13, 2005

Looking for Trouble

I can thank Rajiv, my office-mate, for introducing me to Mobile Mondays. Apparently they started in Finland over a year ago, and since then chapters have sprung up all over. They are informal gatherings of people involved in mobile development, which covers a wide range of companies and positions, and gives people a chance to see what's going on outside their narrow range of interests. Here they are typically held on the first Monday of any given month, although for October it was delayed a week due to a conference conflict.

I really think this is a great idea. It's good for us engineers, because we can indulge in our natural curiosity, cross-pollinate ideas and get inspired for the potential of this technology. It's good for employers, because it's a chance to get access to a bunch of engineers in their field and do some casual networking/recruiting. And it's good for companies because they can show off their stuff and help build interest in their offerings.

Unfortunately, Rajiv was detained on business and unable to make it this time, so I went on my own. I'd been excited ever since the specifics were announced: this month's topic was "Mobile Search," and would be held in unison with the Search SIG. The location was Google's campus; that detail alone would have made me come, I've been entranced for years by stories of Google's unique working environment. The program also sounded solid; several companies would be represented in a panel discussion on the future of mobile search, and several would provide demonstrations as well.

Rajiv had worried earlier about how long it would take to get there. Leaving from work, I'd be driving from the southern tip of Silicon Valley all the way up to Mountain View. Google Maps suggested 20 minutes; I decided to give myself 30, since there was already a buffer of time for registration and food. The drive ended up going very smoothly; despite taking the wrong exit (not my fault, the 85/101 interchange is one of the most baffling and poorly-signed junctions I've seen) I still had time for a scenic tour of the neighborhood before pulling in. Unlike other tech titans who have basically established little fiefdoms, Google's campus feels like it's part of a research park; they share a street with Intuit and some other smaller companies, and while their signs grab your attention their small buildings don't tower like Sun's or Oracle's.

I had my first encounter with Google security pulling into the lot. Throughout the evening the various security guards were extremely friendly, helpful, courteous and visible. He directed me to the appropriate building, which also houses the company cafeteria. I parked a little ways away and enjoyed my walk there.

Google really does let their creativity permeate everything. The lawns were all well landscaped, with shrubbery cut into interesting geometric shapes. Their pedestrian walkways do not go directly from point A to B, but travel in a flattened sine curve. All of the buildings have walls of two-way glass. Each lobby that I passed looked completely different from the others, although each was certainly attractive. One of my favorites had a large plasma monitor hanging from the ceiling that was printing out little line fragments every second, like "inside ukraine" or "dirt bikes." It took me a few seconds to realize that I was probably watching a real-time sampling of actual Google queries.

The Google employees that I met looked friendly and happy. The sun was setting and some were heading home, though many more were visible inside their buildings. There were a TON of bike racks and bicycles around, which didn't surprise me but did please me.

I met up with some other conference guys and together we navigated the way to the cafeteria. Here I picked up my official Google visitor badge and made my way in to the conference room. It was a pretty large setup; they probably had about two hundred chairs set up. People were milling around, chatting, and nibbling on the little wraps Google provided.

I wish I could claim I am a networking genius but I'm really just lucky: that day I happened to be wearing a Wash U t-shirt (under a long-sleeved flannel), and quickly met a fellow alum (B-school, class of '01). We chatted briefly about how we wound up on the west coast and moved on. He's the only alumnus I met that day, but I'll definitely try something similar in the future. That's one of the nice things about the Wash U background, it does stand out here more than, say, Berkeley or Stanford.

Everyone took their seats and we began the panel. It included representatives from Google, Yahoo, two small search startups and Cingular Wireless. There was a designated moderator who kept things flowing smoothly. The general format was that the moderator would pose a question or make a statement, then each person would spend a minute or two giving their company's response. The goal was to share information about what was happening in mobile search and the challenges and opportunities in the future.

Before the panel started in earnest, the moderator gave a brief presentation as a sort of "state of the industry." He showed how the amount of revenue generated by mobile content (ringtones, games, etc., not counting airtime) globally is almost identical to the amount of revenue generated globally by online advertising. He also showed that the market cap of the five biggest leaders in online advertising is several hundred times larger than the market cap of the five leaders in mobile content (Jamdat, etc.). Over all, this implied that there is enormous growth potential in the industry, and that mobile search will prove crucial because search is required for people to find things they want to buy.

Most people reading this aren't as intrigued by the industry as I am so I'll spare you a blow-by-blow summary. The two startups came across as very scrappy and just a little desperate; each one has clawed its way into a niche, or is trying to get into one, and wanted to establish themselves as legitimate. One guy opened his first statement by saying "Wow, being up here between Yahoo and Google [he was actually to the side of them], I feel like a dime between nickels." There was a delay and then a big laugh. From that point on I don't think anybody liked him. He was like a bad but well-coached politician; every single time he talked it was only about how great his company's product was, even if it had nothing to do with the question. Supposedly it "solves the problem" of requiring too many steps for people to find what they're looking for. He would not shut up about it and would not vary his message.

The rest of the guys succeeded in running a good panel. It was very interesting to see the different perspectives people brought to the table. The Yahoo representative was very big on choice, pushing how they wanted to give people as many ways as possible to look for as many kinds of content they'd want to find. The other startup guy took the opposite tack; he said that search was all about limiting choices, about not even showing users things they don't care about and sending them down a narrow path. Google is relatively new to mobile initiatives and is keeping a deliberately open mind, monitoring the desires of consumers and businesses as they work out a strategic vision. And Cingular... the carriers (Cingular, Sprint, Verizon, etc.) are the unquestioned kings of this space, and EVERYONE else is limited by what they decide to permit on their handsets and their networks. Cingular is mindful of the future potential, but is making a great deal of money off the status quo, and wants to continue supporting legacy customers as new services are brought up.

Some interesting facts came out of the panel. Cingular mentioned that, of all its search offerings, the revenue it gets from 411 calls is several orders of magnitude higher than all other search methods combined. The tech companies talked about the various types of mobile search offered and how they are tuned for different platforms: SMS queries (texting a number with a message like "w sf" for "weather in san francisco" and getting back a message with the results), WAP sites (simple web pages designed for mobile devices), and clients (downloadable Java or BREW (yay!) stand-alone applications for search). One example that repeatedly came up is how hard it is for people to find a ringtone on their phone ("Just try to buy a Rolling Stones ringtone. Before you get to the R's you'll have given up or bought something else."); this is an area everyone wants to improve on, simply because it directly impacts how much money people are spending.

It was also a lot of fun to see the individual personalities, other than Mr. Annoying. The other startup guy seemed like a typical post-college startup, a tad slovenly but very passionate about the subject. The Yahoo and Google guys got in occasional humorous snipes at each other without ever mentioning the others' name. They were both engineers who had been coached in PR speak but were still on our side and would wink while giving their boilerplate answers. ("What are Google's plans for making money on online search?" "Google has not yet announced its plans for making money on online search.") The Cingular rep was the only person I saw in the whole room who was wearing a suit, albeit a stylish one, and he was probably the calmest and most open person up there. He was extremely frank about the mistakes carriers had made in the past, like the SMS message limits, and similarly frank about the fact that the carriers still rule the industry.

After the panel, there was a Q&A session. The questions ranged from nakedly hostile ("How can people make money on this when the carriers take up to 50% of the revenues off the top?") to the curious ("How long will it take mobile devices to supplant traditional computers?") to the avarical ("When will we start seeing advertising on mobile phones?") to the nerdy ("What's your backend architecture for load-balancing search queries?"). Each was typically handled by a single panelist. A surprising number of the questioners were foreigners, two were from French firms and another was from Virgin in the UK.

A short break followed, and then came the demos. Yahoo went first, and ran through a variety of their offerings in under five minutes. It all looked very useful and surprisingly responsive.

Google came next. The guy basically said "If you want to see what we're doing, go to mobile.google.com". He then plugged Google Sitemaps, encouraging those who run WAP sites to register with Google so that they get pulled into searches for mobile-specific content. The whole presentation was under a minute and he got even more applause.

The annoying startup guy ran into technical problems (not his fault) and just repeated everything he'd said before about his magical product, AGAIN.

The good startup guy showed off his app, which sadly wasn't as cool as him. It's supposed to basically perform context-sensitive searches, so if you look for, say, a cocktail, it will immediately send you how to make that cocktail, instead of a list of potential results and making you sift through it. It sounds good, but it became obvious that it's very keyword-based and not too intelligent. I wish them well, but they have a ways to go.

Finally, the Cingular guy showed off one of the points he'd made earlier, intended as a reality check for where technology is at today. He brought three people on the platform, gave them three different phones, and told each one that they'd be trying to find the address for a building he would give them. One was to use 411, another would use a WAP browser, and another would use an SMS search. First one to get the answer would win. The building was the Metropolitan Museum of Art in New York City. It took them FOREVER, well over a minute; several people in the audience got it before anyone on the stage. Finally the 411 caller got the answer. The conclusion was simple, "Mobile search has a long ways to go."

They then transitioned to the same ending that every Mobile Monday meeting has, "Open Night Geek." It's a time for people to take 30 seconds to say whatever they want. Quite a few people announced their startups and the positions they were hiring for. Others plugged their services (blogs, etc.) and mentioned their websites. Some gave announcements for other groups that were meeting in the next month.

About halfway through, a guy in a tie (very unusual for this crowd) came up to the mike. He flipped on the projector and set his phone down so everyone could see it. "Hello," he said. "I'm from a little startup called IBM." (Laughter.) "Did you all notice how long it took those people to find out the address of the Met? The Cingular person said it was a big problem to be solved. Well, we at IBM have solved that problem." He entered a program on his phone; I forget the name but the IBM logo was prominent. He picked up the phone and said, "Metropolitan Museum of Art, New York, New York," and set it back down. Within about FIVE SECONDS, it brought back a page of results, and at the very top it displayed the address and phone number of the museum. The ENTIRE ROOM burst into applause. We nerds had finally been impressed.

When the last announcements were done things dispersed pretty quickly. I regretfully took my leave of the campus. I'm not convinced that Google would be the best match for me, but it certainly was a charming place to visit, and I look forward to coming back sometime.

Here's a picture of the panelists, and another one showing yours truly, with my head helpfully circled in red so you can find it.







PS - I totally shouldn't have wasted "You can't always get what you want" on my last post, it would have been the perfect title for this one. Phooey. Also, the Civilization IV web site is now live! Gather ye rosebuds while you may!