Don’t mistake my statements as a knock on Android. Android is great. I love it. My statements in this post are not directed at Android. The G1 is an unfortunate first hardware release of that OS.

There are certain laws mobile manufacturers must follow: You may not offer a media device without a standard headset jack. You may not offer navigation with a week GPS. You may not double the actual required width soley to add a physical qwerty foldout keypad. Above all else, you may not offer a lifestyle device without style.

Now, I’ve said all this based on reading the spec, viewing the pictures, and palming it for 10 minutes. I’ve owned and reviewed many HTC made devices and this a completely obvious failure to me. Perhaps that’s not fair without real-world use though?

So I’m going to endure some pain and suffering so you don’t have to (not that you would buy a G1 – you wouldn’t). I’m going to replace my N82 for the rest of this week with a device I know has no hope. I’m going to use it side-by-side with my iPhone 3G. Wish me luck.

Today I hit 100 miles of running with Nike+. It shows how poorly I’ve been keeping up with running (Galina is in to 200+ now). It’s a nice feature they offer… Rewards keep participants interested. I’d still like to see more non-flash integration with blogs.

The stats for my first hundred with Nike+:

• 26 runs
• 3.81 miles per run
• Average pace of 7′24″

I’m still tracking with both Nike+ (today’s) and Nokia SportsTracker (today’s). The SportsTracker, with GPS, is slightly more interesting because it maps your progress while on the run and offers live mapping. I’d still like to have SportsTracker integrated in a blog – it’s a pain to share otherwise.

Something else of interest during today’s run… Everyone on the trail was in a great mood! I offered, “Good Morning!” to eight people and received eight positive responses. In Philadelphia this is a first. Maybe it’s the weather. Maybe it’s a fluke. But either way, it’s awesome to return from vacation with a strong positive vibe.

Good Morning!

Twicecream – a fake service to demonstrate a point about single sign-on…

In web 2.0 there is a determination to screw up potentially great services. It’s my number #1 pet peeve with software development these days. Here’s a fictitious example of a service you might create…

You’ve built a service that automatically Twitters your geo-position and the name of an ice cream parlor when you’re in front of it. Your phone buzzes when an ice cream parlor is detected and begins sending photos to SnapTweet and TwitPic, including Zagats ratings and commentary. Other patrons respond back and generate conversations. This is your social network: Twicecream – a social network for twittering ice cream enthusiasts.

In front of Ben & Jerry’s on the Wharf, Zagats 4-stars, pics: http://twicecream.com/abc123

Congratulations! You just failed.

You didn’t fail by creating a service few would use. You failed because you didn’t utilize the authentication mechanism your patrons preferred. You built an unnecessary barrier to your garden by requiring an unnecessary account creation. Don’t do this, it’s arrogant and inefficient.

Your patrons have Twitter accounts. Twitter has an API. Your service should have asked the patron to log in with their Twitter credentials.

This isn’t just for social networking. This goes for all web services. SaaS solutions that require secondary account creations are a bad idea. Single sign-on, whenever possible, should be used.

The whole idea is to simplify access to what the customer needs. If you’re requiring unnecessary account creations, you’re screwing it all up.

Link to today’s run

I love running. I skip wearing headphones or listening to music because I love hearing the world race past me. Things that interfere with the actual experience of being there aren’t interesting to me.

Nike+ on an iPod (a music player first and foremost) thankfully has the option to do a workout without music (and without a headset). I’ve been using this since Christmas 2007 when my wife gave it to me. It’s great! Nike has training programs you can follow to get you the next level.

Recently discovered when I got an N82 is the Nokia Sportstracker app. It keeps track with GPS and gives an amazing amount of live metadata. Not only are you able to follow your speed, pace, average pace, distance, location, etc, in real time, you can pump the data live to the web.

There are a couple things lacking with both systems: Social interaction outside their gardens. Both offer links to back to your workout pages, but neither supports easy placement of the data elsewhere (read: No RSS feeds of the content).

An RSS feed of the workouts would be an ideal next step for either company. RSS being available would allow WordPress and TypePad widget development much more easily.

It would also be slick to have Twitter and Facebook integrations (Nike+ has some Facebook apps written by third parties – I haven’t been impressed with these since they’re all Flash).

Running profiles:

• Nike+: http://nikeplus.nike.com/nikeplus/?l=runners,runs,1089318170
• Nokia: http://sportstracker.nokia.com/nts/user/profile.do?u=solyoung

Having some fun with the iPod Nike+ and Nokia GPS at the same time while running down to the John Kelly statue along the Schuylkill. While stretching decided to shoot a quick video (didn’t Qik).

The results for the Nike+ are extremely accurate. Since the iPod measures pauses, I believe both devices were pretty much in sync.

Results:

• Nike+
• Nokia SportsTracker

I picked up the Nokia N82 yesterday from Import GSM, a great hybrid brick-and-mortage / online store. Think Dynamism for phones. It was my first visit, right at closing, and despite trying to get stuff out the door for the evening shipment the guys helped out with descriptions and subtle nuances between the N95 and N82 (special thanks to Eric – good guy).

Anyway, so why the heck would someone get a Nokia N82 when the iPhone 3G is getting released tomorrow? There are five reasons, one for each megapixel, and a lot of backup arguments. The iPhone 3G doesn’t hold a candle to the image sensor quality, flash, or lens quality.

This wasn’t meant to be an N82 vs. iPhone 3G post. They’re both the best mobile equipment one can get (imo).

The N82 is going to be my net enabled camera and broadcast machine. No more notebook + Canon SD-1000 combo!

The iPhone 3G is for everything else. I had the iPhone (1.0 / original / whatever). iPhones are the best for usability and communication. I gave it to my wife and she’s gone from check-email-and-browse-at-home to check-email-send-texts-and-monitor-weather-while-away. The wife-o-meter was pegged.

The Nokia’s OS, after 30 hours of tweaking, is finally usable for me. Very steep appreciation curve. I would only recommend such a phone to a power user needing the best tool for quality images… I can’t wait to start posting and qik’ing them.

• sol on Qik
• solyoung on Viddler
• sol on Twitter

Steven Hodson, in a post over on Mashable, describes security risks and the waste of information that mobile phone GPS use brings (when pinpointing and announcing our locations). He poses some extremely valid points in regards to announcing one’s geolocation via Twitter, Brightkite, or FriendFeed being useless noise.

Telling people via a highly conversational medium such as instant messaging or an SMS text that you are currently at 13th St and Ash Lane is nothing more than noise. It’s a waste of precious conversation. To a few of your closer friends it may be relevant, such as a buddy that would meet you for coffee. But for the masses, it is unimportant and you’re guilty for wasting their time.

I’m guilty of this lately. I’ve been trying various mobile phone GPS services. It’s been fun and interesting, but I’m in agreement with Steven about this announcement being a waste (at least if it’s without background information). Steven doesn’t mention it, but my thought on optimal geolocation announcement is in a widget placed on one’s blog. It’s there for interested followers, but not intrusive or annoying.

But that’s where we agree. He describes broadcasting one’s geolocation as a security risk and I strongly disagree. Yes, there are some situations where it is. US soldiers in Iraq will not benefit from this feature. Folks in witness protection programs, runaways, victims of domestic violence, those being stalked, cheating spouses, and those in organized crime probably won’t either.

The typical citizen without conflict is not at risk. It’s easy to figure out when someone is normally at work, so knowing an optimal time to break in to someone’s home is already simple. It’s easy to find a person in a public place, so it’s already easy to find the optimal time to commit physical harm.

Note: If one is being stalked or believes him or herself to be in a situation where announcing location is dangerous, it’s simple to turn the feature off.

As I’ve said before, people are inherently good. They don’t go around looking for someone to damage or rob. There are some people who commit these crimes. These people use crow-bars instead of Facebook, and are stopped by alarm systems and deadbolts rather than a lack of geolocation data.

Photo courtesy U.S. Department of Defense

Just a couple ideas on GPS, tied to proximity of a mobile phone…

• Proximity based ads (walk by Banana Republic and get a coupon via SMS)
• Location based music (Last.fm channels playing artists from your location)
• Mobile OnStar

Think of your favorite services on the net and add a GPS component… It probably enhances it.

view in Google Earth

This morning’s run was notable. Honeysuckle and other sweet flowers filled the air next to the Schuykill River… Far better than the expected dead fish, exhaust, and port-a-potties.