Another example of why the tech industry and mobile operators don't get along

When you work in consumer electronics, one of the rules that gets drilled into you very early on is that you never do anything to disrupt the holiday selling season. In the US, the month between Thanksgiving and the end of the year can account for three months' worth of sales, if not more. During that time, you don't change prices, you don't alter your ad campaigns, and most of all you don't ever say anything about future products, because that might cause customers to hesitate before making a holiday purchase.

So the CEO of ATT, giving a speech this week in Silicon Valley of all places, says that a 3G version of the iPhone is in the works:

"Has Jobs announced that? I don't think he's announced that, but you'll have it next year."

Not only does he spill the beans, but he acknowledges that Apple hasn't announced it and then talks about it anyway (link). The next day the story is carried by the AP, MSNBC, the Times of London, Wall Street Journal, Bloomberg, the SJ Mercury News (which had the version of the quote above), and 318 other publications according to Google.

In the US, the assessment from a lot of commentators is that this won't have much impact because the iPhone is so popular anyway. Maybe, I guess, although the iPhone isn't sold out, so any loss in sales is still a loss. But in Europe, I think it could be a big problem. iPhone sales there are not going great to begin with, and folks in Europe are generally much more conscious of 3G vs. 2G issues. The acknowledgment that a 3G iPhone is coming could cause a lot of people to hesitate before buying.

If AT&T competed directly with Orange, O2, and T-Mobile Germany, I'd be tempted to speculate that they made the announcement on purpose to hurt the competition. But they don't, so I suspect this is just a case of a CEO who wanted to show that he's not controlled by Steve Jobs but instead demonstrated that he doesn't understand consumer electronics.

Google Maps Mobile - My Location

Google's Map application for mobile is one of the best things that happened to mobile devices. I've enjoyed it in the beginning on BlackBerry devices. As time progresses, they've developed .cab files for Windows Mobile devices which worked w/ some flaws in WM5 but near flawless within WM6. Yesterday, they released a new 2.0 beta for the application to support a new feature called "My Location". This is great for phones without built-in GPS (even if you do have GPS, chances are, your wireless carrier will charge you to use it) where they use nearby cell-tower and other GPS-enabled phone users signal to triangulate your location.

Yours truly downloaded the latest GMAP mobile application tonight to give it a whirl. Installation went fine as usual, however, from my apartment in the West Chelsea neighborhood of Manhattan, GMAP prompt that it can't find my current location. Bummer. I'll need to try this on my way to work tomorrow morning.

A Maze of Twisty Little Passages



The end of last week was Thanksgiving in the US, the tradition is to be with family, eat too much food and watch football (not necessarily in that order).



Apparently some folks took the chance to work on Android projects too. We are highlighting a few of the projects that caught our eye.



One of the coming of age rituals of any new platform is the porting of the Z-machine – the interpreter used in the Zork series of games from Infocom. Now Android has the Z-machine thanks to sussman and mariusm. The project, called Twisty, is available on Google code hosting. Thanks for the lost productivity you guys.



Testing is also a hot topic on our Google groups. While JUnit is bundled with the Android SDK to make it possible to do unit testing, there are many other kinds of testing, like automated acceptance testing. Positron builds on the Android instrumentation features from the SDK to make automated acceptance testing of Android applications possible. The author, phil.h.smith, has a pretty good introduction on how to use Positron as well.



Plugins for other IDEs are another favorite on the Android Google groups. While there are only rumblings about a NetBeans plugin at present, the idea-android project already has an early release for IntelliJ IDEA thanks to aefimov.box and intelliyole.



Dion Almaer also picked up on a crossover GWT/Android project which looks pretty amazing too. Chronoscope is an open source charting and visualization library written in GWT. The team were able to take the library, and with 8 hours of playing with Android, had a port to the Android platform.



Of course, there are many more Android projects springing up all the time, as a search of the android label on Google code hosting will demonstrate. It's great to see all this activity just a couple of weeks after the SDK was released.

Windows XP vs. Vista

I am sure people have been experience the "lag" from Windows Vista unless they had powerful machines and long hoped for the first service pack to be released. Well, some bad news is that a software development company in Florida, Devil Mountain Software, stated that Windows XP (beta Service Pack 3) has 2x the performance of Vista (Service Pack 1). Vista's first ever service pack is supposed to be released early next year and is supposedly said to boost the operating system's performance.

The competition resulted in Vista taking over 80 seconds to complete the test, compared to the XP's 35 seconds. Vista's performance increased less than 2% compared to the performance without SP1 while XP's SP3 improvement resulted in a 10% gain. The tests, run on a Dell XPS M1710 test bed with a 2GHz Core 2 Duo CPU and 1GB of RAM, put Microsoft Office 2007 through a set of productivity tasks, including creating a compound document and supporting workbooks and presentation materials.

This can definitely be an issue for Microsoft as it aspires to increase it's sales of Vista, especially to businesses. It's no wonder my notebook has to "think" to open a PowerPoint.

Questions about Verizon's new "open" attitude

More than half of the traffic to this weblog comes from outside the US, so there are times when I feel obligated (and a little embarrassed) to explain how the mobile market works here. This is one of those moments.

Verizon, the largest US mobile carrier, made headlines in the US today by announcing that by the end of 2008 it's going to make its network available to any device and any application that the user chooses to install (link).

This will seem remarkable to people living in GSM countries where it's normal to choose any device you want. But in the US, it's an unusual idea. Here mobile usage is split between GSM and CDMA. GSM phones have SIM cards, which technically allow you to switch your account to any phone you want. But in practice, almost no users are willing to give up the several hundred dollar subsidy for buying a phone and service plan together, so they only choose phones that come through the operator.

Things are even more restrictive in the CDMA space, where there are no SIM cards. If you buy a Verizon phone, it can only be used with a Verizon account. Same thing for Sprint.

So Verizon's announcement is a nice change, on the face of it. It's also something of a pleasant shock, since Verizon has the reputation of being the most conservative and controlling US operator. But the announcement's actual impact on the market is going to depend on several questions that Verizon hasn't answered yet:

--How will open access be implemented? Verizon says it's going to define a process by which phones can be certified to work on its network. That could be routine or it could turn into a huge barrier to entry. We also don't know how a user's account will be switched between phones. Is Verizon planning to start installing SIM cards in its phones (something that has been done with CDMA in China)? If not, will you have to take the phone to a Verizon store to get it activated? How much will that cost?

Verizon apparently said something about doing activation through a toll-free number, which could be cool.

--How will the service be priced? Verizon's service plans include recovery of the several hundred dollar subsidy for hardware. You pay for the subsidy as part of your monthly bill. Since Verizon doesn't have to recover a subsidy cost on its open access phones, there's about $10 or more a month that it could pass along to consumers in the form of lower bills.

If Verizon doesn't price the open service lower, what happens to the extra money? Does Verizon pocket it? Or will they offer some sort of rebate on purchase of open access phones?

The answer to this one is critical. The US GSM carriers are technically open, but the subsidy prevents significant sales of alternate phones. If Verizon pockets the subsidy money, very few people will take advantage of the open service. The whole thing could turn out to be a PR gesture rather than a genuine change.

But in the hope that Verizon wants it to be more, here's what they ought to do:

--Make the monthly cost of the open plan lower than a traditional service plan, reflecting the absence of a subsidy.
--Make the handset certification process simple and low cost.
--Make it easy for users to switch their account to a new phone (preferably via a SIM card or website or that 800 number, so they don't have to come to a store).

That's an announcement I'd stand up and cheer for.


Impact on the industry

Until we hear the answers to the questions above, it's impossible to guess how impactful this announcement will be. The most important factor may be how the other US operators react. The best result would be if they start competing with each other to see who can make their network more open. If that dynamic takes hold, competitive forces might drive them to really open up even if they don't intend to.

Pesky iPhoto Function "Original" and "Modified" Folders

iPhoto to me is a mediocre photo viewer. I prefer ACDSEE or PICASA but these options aren't available to Mac users. One of the most annoying features in iPhotos is its ability to duplicate sets after sets of photos in the "Originals" and "Modified" photos. I am dedicating this entry to help combat this annoying feature and share with you, what I deemed to be the more "PC" way to manage photo library utilizing iPhoto.

1. Managing the source - after taking a serious amount of pictures from my trusty camera or (downloaded from the internet), I usually like to keep my photos in a dedicated location on my computer (along with my other important documents). By default, I never keep it in where the OS is suggesting me to (ie. Never in "My Documents" on PCs or "[username] - Documents" on OSX). I find my own location being a much easier way to centralize my files (music, photo, or docs) when it comes time to backing things up.

2. iPhoto - Turn off its ability to duplicate a copy into its "Original" photo.
Under iPhoto>Preference>Advanced, check off the box that sayings "Importing: Copy Items to the iPhoto Library". When you are importing, try to go through the iPhoto interface (File>Importing>) instead of dragging the source images by mouse dragging. This step will prevent your images from being duplicated into the "Originals". With this move, you'll find that the images are merely shortcuts to your source. (Its easy to locate the iPhoto Library Originals folder under iPhoto '06, for iPhoto 08, use this Show Package Content reference to get to the Originals folder.

3. Modified folders - I tend to avoid editing in iPhotos (I'd rather use Photoshop to edit the the source). However, in bizarre occasions such as dealing with iPhone's images (no matter how you import photos off of your iPhone, it automatically assumes a modified set is necessary). There is a quick way to fix the problem. Just simple right click on the photos you've just imported into iPhoto and select "Revert to Original". This will get rid of the duplicates in the modified folders.

If this is done right, when you right click on a photo in iPhoto, only "Show File" can be selected (while "Show Original" is gray'd out). Selecting "Show File" should point you right to where your source file location. Whereas the iPhoto default whould give you "Show File" as the modified folder and "Show Original" as the original folder. Boo...

*Important Warning: This article is assuming that you do not want to take advantage of iPhoto's ability to help you keep duplicates while modifying your photos. You are minimizing iPhoto's built-in protection to keep a duplicate in the "Originals" and "Modified" folders. I personally find this iPhoto feature extremely annoying as it triples the size of hard disk space. I am also assuming you've got a clean canvas to work with, meaning you haven't already gone ahead and modified a bunch of images in an old iPhoto library. If you are pretty far along in using iPhoto for its features and have modified a good amount of pictures, you'll have to just start from clean slate and make copies/backups of your "originals" and "modified" photos.

Tip: iPhoneDrive Brings Disc Mode to iPhones

iPhoneDrive ($9.95), from Ecamm Network, allows you to use your iPhone for file storage, something you can't do with Apple's iPod/smartphone combo out-of-the-box, as there's no disk mode for iPhones like there is for iPods.Launching iPhoneDrive brings up the utility’s browser window and toolbar. It is from there you can transfer files and folders back and forth between your Mac OS X computer and