Wandle SoftwareI see that a new version of the iPhone firmware is now available for download. Unfortunately not all developers get to see new releases before you do, so I have not had the chance to check that everything still works as before. I do not anticipate any issues but will have a look as soon as I can.
If you see any problems please let me know. I will do what I can to help.
Although activity here recently might lead you to conclude otherwise, I am busy working on the next version of Yummy. I have my own internal hit-list of features that I want to include — I use Yummy as well as write it — but I thought now might be a good time to solicit feedback.
What new features would you like to see in the next version?
Feel free to add your suggestions in the comments below or directly by email. I won’t make any promises but I will always do what I can.
One of the hard things about buying an iPhone application is that, unlike Mac or Windows programs, there is no way that you can see the program in action without actually buying it. Even when the cost is less than a latte at your local coffee franchise, the thought of putting down money for something without seeing it in action makes the process harder than it might be.
Much is in Apple’s court. There is no way, for example, that I can make available a demo version. I can, however, do one better one better than screenshots. With apologies for the poor audio quality, here is a “screencast,” a quick overview of Yummy’s key features in video form.
What do you think? Does this give you a better idea of what Yummy is like to use?
From time to time users of Yummy ask me how often it synchronises its bookmarks with Delicious.com. I hope to answer that question in this post.
First a quick aside. How did I envisage people using Yummy when I was designing it? The idea was that it should pretty much stay out of the way. You’d open Yummy, search or browse for a bookmark and immediately flip over to Safari to see it. Or you’d start in Safari, add a bookmark that you want to read later and return to what you were doing.
In this usage pattern, if you have Yummy open for more than a couple of minutes at a time I’ve probably failed. Which means that doing a full refresh every, say, thirty minutes would be a waste of time.
Instead, Yummy checks to see whether there are any new updates to download every time you start it. Usually there are not and the refresh is almost instant. In fact, most users should never really need to use the refresh button at all — indeed I almost did not include it in the finish application.
But, with great power comes great responsibility. If you refresh very frequently occasionally Yummy will tell you “Delicious says that you’re refreshing too quickly.” The cause of this is, well, exactly as it says. Delicious will only allow a client to do a full refresh once every thirty minutes or so (the exact time seems to vary). This is not a limitation of Yummy; it’s a limit imposed by Delicious.