September, 2009

...now browsing by month

 

iPod Nano Pushes Polar into a Freeze

Thursday, September 10th, 2009

Here is another example of how single-purpose devices are being co-opted by Apple’s general purpose devices.  I am a weekend-warrior (i.e. prosumer) who bikes and runs for enjoyment, and competes occasionally in triathlons.  Put simply, I am exactly the kind of market Polar needs to capture to remain viable. A few years back I spent $300+ on a Polar watch that provided fancy heart-rate monitoring and motion sensors to capture my running rate.  Put that same purchase decision in front of me today and there is no way I would buy the Polar watch again; instead I would buy the iPod Nano.  It supports all of the capabilities on my Polar watch that I actually used. Not a good day  for a Polar Product Manager when a single purpose device like the Polar cannot do its single task better then a general purpose device like the iPod Nano.

iPod Nano | $199

  • Watch
  • Music/video player
  • FM receiver
  • Video camera
  • Pedometer
  • Heart-rate monitor (coming soon)
  • On device training tools (i.e. graphs and charts)
  • Online training communities

Polar FT80 | $349

  • Watch
  • Heart-rate monitor
  • GPS (in my own personal experience 50% of connections time-out)
  • On device training tools
  • Online training tools (very poor links and even worse communities)

I see two choices for Polar:

  • Go Exclusively Professional:
    • Sell to professional athletes and most shut down their prosumer “weekend warrior” business which requires significant investment in marketing and distribution.  Frankly, this is a tiny market — you are basically selling to college and pro athletes.
  • Embrace and extend general purpose devices
    • Build add-on devices like a heart-rate sensor for the iPod Nano.
    • Polar is a brand I trust in this space and I would be willing to spend $40 on a Polar heart-rate sensor.

The Next Phase of the Apple App Store

Tuesday, September 1st, 2009

While the media enjoyed the conflict fest between Apple and Google, the conflict itself became a distraction.   Yes, the approval process needs to be totally revamped – our Inquisitor iPhone app spent six frustrating weeks in the approval process.  But there are core App Store issues like poor discoverability, installation (needlessly cumbersome), and a strategy for web apps that are key to the success of AppStore yet mostly ignored.

These embarrassing numbers from the Android marketplace serve as a reminder; developing a thriving mobile application ecosystem is really hard.  No other company has all the tools (hardware, software, marketing, global footprint) to bring about the revolution in mobile we are witnessing, and the App Store is a key component of this revolution.   If it fails then it risks shifting power back to carriers. Apple knows how to creatively move products into their next phase (e.g. iPod becoming a feature of the iPhone), and the time has come for Apple to move the App Store into its next phase with:

1.) App Discovery Revolution:

If you can’t find it, it does not exist.  There are hundreds of great apps not being used and enjoyed because of the poor App discovery tools.

  • Provide App Store data feed including number of downloads, aggregate reviews, and snippets of individual reviews to help third party discovery sites blossom.
  • “Genius” for Apps. Genius algorithms needs to be vastly improved, steal a page from Netflix and throw open a $2M competition to improve Genius.
  • Search.  This topic deserves its own post, but very quickly the federated approach is broken.

2.) Dead Simple App Installation

Getting an App onto my phone from my computer is a massive hassle that includes connecting cables.  I find it odd that I can remote wipe my phone but I can’t install an app remotely. One-Click Remote Install would bring a frictionless install process. Here is how it works, from any web page when I click on “Get this App” rather then opening iTunes the process would

  • Open a widget, inline web form, etc. where I authenticate with my AppleId
  • If its a paid App confirm payment.
  • Send a notification to my phone to install the app.
  • Next time I grab my phone a small notification appears reminding me that it installed the app.

Rather then flowing all transactions back into iTunes provide the tools to enable distributed transactions.

3.) Expand App Store for Web Apps

Why do I have to write a product in Objective-C in order to monetize it. Lots of  valuable web apps optimized for the iPhone webkit browser are struggling to generate meaningful revenues via ads or don’t have time to deal with hassles of PayPal.  These web developers are looking for distribution and monetization, while Apple is looking to keep web developers within the Apple tent.  This solves both parties problem.

4.)  Tough Blocking and Tackling (i.e. Better Developer Tools)

This is the blocking and tackling component to the ecosystem.  Developer tools don’t make headlines but they are the tools that we use everyday:  xCode,  iTunes Connect, and the App Developer Portal are all beautiful yet frustrating and limiting tools.