Archive for the ‘FatWatch’ Category

Don’t call it a comeback!

Wednesday, December 9th, 2009

I confess, I have some minor narcissistic tendencies. For example, the App Store search bar on my iPhone usually contains my own name, so I can check on the ratings of my apps at a glance.

That’s how I noticed this new review of FatWatch, my weight tracking app for iPhone:

It does exactly what it says it does, but it’s far too expensive and the developer seems to have abandoned it. Get one of the free weight apps and save yourself the dough.

Ouch!

In a world of disposable mobile apps, FatWatch might seem expensive, but it’s actually quite cheap for what it does: tracking your weight against a moving average in a well-designed application. The average is key; it’s the only useful way to track a human being’s weight, and none of the free apps can do the math for you.

For devotees of The Hacker’s Diet, it also lets you import your weight history from the old Palm Eat Watch app and export it to your computer any time you choose.

As for the other concern, I assure you that FatWatch has not been abandoned. I use it every day! I suppose it is overdue for an update, but that’s only to add new features, as (save for a minor cosmetic issue) no bugs have been reported in FatWatch 1.4.

The good news is that I recently completed a contract project that puts me in a comfortable enough financial position to devote time to a FatWatch update. So, watch this space, and if you’re interested in beta testing, wait for an announcement soon.

FatWatch 1.4.1

Wednesday, June 24th, 2009

I intended FatWatch 1.4.1 to be a minor update, primarily to fix a display issue that appears on iPhone OS 3.0. If you’ve upgraded, you may have noticed that when you switch between Variance and BMI in the Log view, the table rows no longer update immediately; you must scroll to force them to redraw.

I submitted an update to Apple, changing as little else as possible, hoping that it would get through their review process in time for the public release of 3.0. Unfortunately, it was rejected for violating the iPhone Human Interface Guidelines. That’s right: I was nailed for something that they previously approved.

What I got away with

I could bitch about it, but they were right: the objection was to the Wi-Fi Import/Export feature, which in FatWatch 1.4 was enabled by a simple switch.

fw140-wifi-off

If you want to import or export a CSV file containing your weight history, all you had to do was turn that switch, and a new row would appear beneath it with an IP address to connect to.

fw140-wifi-active

If you didn’t know what to do with all those geeky numbers and slashes, hopefully you would tap on it, because doing so would display an alert explaining that you are supposed to enter that into the address bar of a web browser on your computer.

Even when working properly, this is a spartan interface. I’d honestly be surprised if anybody who doesn’t describe themselves as a “geek” figured it out. What’s worse (and this is where I got into trouble with Apple) is when you turn on Wi-Fi Import/Export and you’re not even connected to a Wi-Fi network. You get a blank row.

fw140-wifi-airplane

So yes, I could say to Apple, but that’s how it worked all along! But that’s like telling the police officer you shouldn’t get a ticket because you run this red light every day and nobody gave you a ticket before.

Making things right

Initially, I tried to fix things by detecting whether a Wi-Fi connection was available and, if not, snapping the switch back to the OFF position and displaying an alert with an error message. While that would have been an improvement, it still felt… terrible.

After sleeping on it (always more productive than hammering away all night, will I ever learn?) I realized that Wi-Fi Import/Export really deserves its own screen, rather than the series of alert views I had allocated it. In practice, you aren’t going to use your iPhone or iPod touch for anything else while you are importing or exporting a file, so there’s no need for it to operate in the “background” of the app.

So in FatWatch 1.4.1, the Wi-Fi Import/Export changes from a switch to a menu item.

fw141-wifi-off

When you tap it, you see a screen that explains what Wi-Fi Import/Export does and how to use it. It also tells you that you can use Bonjour, instead of typing in a series of dots and colons and numbers. FatWatch always used Bonjour, but there wasn’t enough space in the old interface to explain it.

fw141-wifi-active

FatWatch will now remember the last time you imported or exported a file; very useful if you want to export a file as a backup every so often and you can’t remember when you did it last.

But, most importantly, if you are not connected to a Wi-Fi network, FatWatch now makes it abundantly clear.

fw141-wifi-airplane

As a bonus, now that I have a whole screen for this feature, I was able to get rid of the alerts and do some nice things, like display a progress bar so that you know things are working when you’re importing a large file.

fw141-import-1 fw141-import-2 fw141-import-3

I won’t claim it’s perfect: even now I want to edit some of the text in those screenshots. I held myself to a fairly tight schedule because I didn’t want people to be waiting too long for the bug fixes that was supposed to be the primary focus of this release. However, I am glad Apple challenged me to improve this feature, because it has gone from an embarrassment to something I can feel mildly proud of.

More

A few other improvements that are coming in 1.4.1:

  • The Wi-Fi Import/Export web pages are easier on the eyes.
  • FatWatch puts today’s date in the exported file name, for example: weight-2009-06-29.csv. Useful if you let those files accumulate in your downloads folder.
  • The Go To Date screen displays its buttons in a navigation bar; looks a lot nicer.
  • Fixed a bug where BMI values were calculated incorrectly. Basically, if you select your height in feet and inches, FatWatch always added an extra centimeter to your height. That has been fixed.

Everybody cross your fingers, and hopefully it will appear on iTunes soon!

FatWatch and iPhone OS 3.0

Wednesday, June 17th, 2009

iPhone OS 3.0 update is supposed to be available via iTunes any minute now, which means this post is long overdue.

If you are using FatWatch 1.4 (the latest version at the time of this writing) then you can safely upgrade to iPhone OS 3.0 if you are willing to suffer a cosmetic issue. Specifically, if you have BMI Monitoring enabled and use the control on the top of the Log view to switch between BMI and Variance, the values will not update unless you force them to by either scrolling the table or switching to and back from another view. It’s annoying, but not fatal.

I submitted an update to Apple that fixes this issue (and a few others), hoping it would be available on iTunes before the 3.0 update was released. Unfortunately, Apple rejected the update for a human interface issue concerning a feature that I hadn’t changed. It feels a little unfair to be rejected for something that was previously approved, but “I got away with it before” is not really a defense. They are right, it is something I should fix, it’s just that the timing is obviously less than ideal.

I intend to fix this issue and resubmit today or tomorrow, which means that FatWatch 1.4.1 should hopefully be available sometime next week. Or maybe not. I wish I could say. In the meantime, should you want to install the iPhone OS 3.0 update you can continue to use FatWatch 1.4 and be mildly annoyed at the display issue.