Dave Metzener's Weblog

WTF Apple! Bjango Being Blackmailed Into Removing A Feature

Posted in General, Rant, iPhone/iPod touch by Dave M. on August 20, 2009

Icon 256 istat.png

OK, what the hell is the matter with you Apple! This blackmail tactic of threatening to remove an application from the AppStore because you don’t like a feature is really getting very very old!

I just learned that Apple is threatening to remove iStat from Bjango if they don’t remove a feature in the application that attempts to free up memory that is otherwise not being used.

istat-ss.png

As you can see from the screen shot to the right, the first section of the applications data is a pie chart of memory usage. Wired and Active is memory that is currently being used by applications, Inactive and Free is memory that is not being used. The “FREE MEMORY” button to the right of the pie chart allows the user to attempt to free up memory that is not being used at the time.

For this example, tapping the FREE MEMORY button would probably free up about a quarter of the memory currently being colored in the pie chart. This has been my experience with the app. It probably attempts to fill the device with used memory by allocating as much memory as it’s allowed, then freeing it up. This will force the device to “Page Out” memory, freeing up some memory for other apps.

Typically, the Mail, Phone and iPod apps don’t quit when you press the Home button. So they take up memory that may not be needed if you are not listening to music. You don’t need Mail in memory if you are not reading messages and you don’t need “most” of the Phone app in memory either.

The news hit Twitter just a few hours ago directly from Bjango. Here are the tweets from their Twitter account: http://twitter.com/bjango

We’ve been asked to remove iStat’s free memory feature. This leaves us with two choices. Resubmit with free mem gon (cont) http://tl.gd/dme8

You all know who asked ;) Keep the replies coming. User feedback is a VERY important part of this decision.

Those who want more info: we simply don’t have any. It is exactly what it is.

All the detail we have: iStat will be removed from the store unless the free mem feature goes.

If you don’t update iStat to version 1.1, then yes, you get to keep 1.0 as is, free mem included.

On the plus side: If we remove the free mem feature, we will be able to update iStat with all the features we’ve been wanting to add.

We haven’t made a decision yet but it seems like people would rather have updates even if it means free memory is gone.

Now, there were a lot of folks chiming in with suggestions including myself. I would personally like to keep iStat as is, and purchase a new iStat app that doesn’t have the free memory feature, but has the new features that Bjango is promising. Were not talking a huge amount of money here. If I paid full price for the app, it was $1.99. I would gladly eat that for a way of freeing memory other than turning off my phone, then back on. That is so annoying and is just because there is no memory free to run the application I am attempting to run.

I have seen symptoms in several apps I run. With PandoraBox, I’ll see application entries with all blank data, meaning that there wasn’t enough free memory to load the app description and icon into memory to display. I’ve seen apps shutdown seconds after starting. After I free the memory, the applications work fine.

I have to wonder what in the world Apple doesn’t like about the ability to “Page Out” memory not being used presently by other applications. It’s what a Paged Memory Management system is designed to do. If the “embeded” version of OS X is not capable of PMM, I would have to question Apple’s saying that the iPhone/iPod touch uses an Embeded OS X.

As usual, Apple is not stating way Bjango has to remove the feature from its app. Just that they remove it or the app is removed from the store. I’m actually surprised that Apple actually gave Bjango a warning that they would remove the app if they don’t comply. We have clearly seen examples of Apple pulling the plug on an application and surprising the developers with the news after the fact.

So, come on Apple, get your head out of your collective asses and fix this AppStore problem, or you are not going to be seeing the applications you would like to see in your wonderful AppStore in the future. Just hundreds of thousands of “Bulk” apps that we all enjoy so much right now. (You know what I’m talking about, don’t you Brighthouse Labs?)


2 Responses

Subscribe to comments with RSS.

  1. hargrove said, on August 21, 2009 at 8:36 am

    I haven’t used it (yet, just bought it) so I don’t have any experience with it. However, I’ve read at least one comment stating that this app consistently breaks email push. If Apple has been getting complaints from people regarding broken functionality on their iPhone and Apple has traced it back to iStat, I can understand the reasoning. It’d be nice if Apple stated their reasoning, but silence and confusion seem to be the rule these days.

    The process for getting apps on the App Store is broken, no doubt. Generally speaking (and there are always exceptions), if Apple has a problem with an app, it needs to be raised before the app is accepted into the store. Removing an app after the fact and especially after people have purchased it is not fair to anyone. Apple taks 30% of the sales but the developer is responsible for refunding 100% of the price. This is a recipe for bankruptcy if I ever saw one.

  2. Dave M. said, on August 21, 2009 at 9:40 am

    I did a search in Apple’s Discussion boards on the issue of Push not working and didn’t find any references to Push with iStat at all. So if Apple has been getting complaints, they are not in the discussion forums like most problems are. That’s not to say that they are not getting complaints. They could be coming in from Genius Bar techs, or AppleCare inquires. Still…

    Plus, the tools causes Page Outs. In theory, if Mail is still in memory, a push should Page In in the memory needed when an email arrives.

    I tested this on my phone. I reactivated my MobileMe mail, checked that it worked before freeing memory. Then, went into iStat, touched the FREE MEMORY button, and sent myself another email. Sure enough, I got the new email notification sound a second later followed by GPush telling me a new message arrived in Gmail. Heck, even the Gmail account got the message at the same time.

    I did the free memory test a second time and got the MobileMe and GPush notifications a second later. The Gmail notification came minutes later this time since it’s set to 15 minutes. It arrived when I went into Mail to delete the MobileMe message.

    Mind you, I’m only one of millions, so my results may not be what a majority are seeing. Still, I didn’t see any issues with Push not working when freeing memory.

    All that said, maybe Apple should do more with it’s iPhone OS to better handle memory. It’s not good when applications suddenly die with no warning including Apple’s own applications. Mind you, Apples apps very rarely die unexpectedly. Mobile Safari is the only Apple app I have had die suddenly, possibly due to memory. With Safari, it could be many other factors other than memory.

    It’s also very unprofessional to tell it’s users to “turn their iPhone/iPod touch off, then back on” to fix this memory issue.


Leave a Reply