I get this question across my desk a half-dozen times a day, and that’s just friends, family, and random emails sent to me. Obviously, as a Mac nerd, I care deeply about the subject, and decided to investigate.
Short answer: We’re as close as you can get without being able to attach a definitive date.
Long, rambling, almost-irritating-in-a-way answer:
First, let me tell you a story about another company. This company, whom I shall not name, sucks. They make a great technology product that claimed they had Mac support. And when we called them, they said, “Yes, we support Macs. Just buy an Intel Mac, install Boot Camp, install Windows, and we’ll support your product.”
Say what?!?
We’re Mac fans around this place. The Apple store in the area keeps us on speed-dial to find out how many machines we’ll be picking up this week. Our marketing, IT, Development, and executive teams are now all Mac-based (many recent converts, to my delight!). No one feels the pain of a lack of Mac support here than me, since I’m the local Mac Support guy, and I have to set up duplicate iTunes libraries for our people in Parallels so we can use our own product. It’s a solution, but certainly not the one I would want for our customers.
I was around during the infancy of our company, and I know we had planned a simultaneous Mac and PC launch. The code was originally written for the PC platform, and we thought that we’d hire an outside developer to port our code.
We talked to a number of well-known Mac developers, and even the guy that wrote Coverflow (well before that was co-opted by Apple), but great Mac developers are always super-busy. So, in-house it was. We were sure it would be ready by mid-April. I was so excited, that I decided to try to speed things up by making an icon:

However, we were continually rebuffed in our development cycles. Fix this, add that, etc. We pushed back to July. Then September. Then December. The question became, “How hard can it be to port your code to Mac?” The answer: “Very.”
Another question was “Well, now that Mac has moved to Intel, is it easier to port your code to Mac OS?” The answer was again, a surprising “No, more difficult.” There was something about switching our code from Carbon to Cocoa that slowed it down tremendously. I won’t pretend to understand all the ins and outs of coding for the Mac, but it’s a totally different animal. Our developers have been working really hard on a lot of things, but about 8 weeks ago, the Mac finally found its place at the top of the list.
Now, it’s Februrary, and I’ve been working in the office all weekend. Our entire development team has been there this weekend, as well, and I had to rub my eyes when I saw what they were doing.
Podfitness created its first workout on the Mac today. At this point, it’s a Dr. Frankenstein thing (you really don’t want to see programs before they’re tied up in their neat little packages, trust me), and of course there were some small issues, but the Mac made its first Podfitness workout today. That’s no small breakthrough.
It’s taken too long, I know. I think it’s funny that I can’t find any statistics on the percentage of users of iPods or other MP3 players use each player, but I would venture a guess that somewhere between 15-25% of iPod owners use a Mac. That’s a pretty big chunk of people that we’ve had to turn away over the last year.
Another thing that was noted (first by me, and subsequently by many, many potential Podfitness members): It’s ironic that a program designed for MP3 players, which Apple largely popularized, isn’t yet compatible with Apple computers. Rest assured, we’re very close to announcing a date that will finally end the tragic irony.
Note: Since starting this post, I received two emails from people hoping to find the status of Podfitness for Mac. I hope they find their way to this blog. Stay tuned for official announcements from Podfitness about this.