When a developer submits a "Pull My Finger" application, you've kind of got to expect it's going to be rejected. iFartz was rejected. Ibrate was rejected -- and that one was even raising money for breast cancer research. Today, over at Mac Rumors, I read about "Pull My Finger"'s rejection for limited utility. Right at the bottom of the rejection letter was the name "Victor Wang".
Mr. Wang has become a near legend for his rejection letters, usually long, delayed (I suspect he's second- or third-tier in the review process) and for aesthetic reasons that leave developers blinking with surprise. While "Pull My Finger" would probably not meet "Koi Pond" levels of user reach (here's our look at Koi Pond), it could have a solid audience. It's a simple, stupid joke app (notice how I'm not pulling punches here) but it's the kind of simple, stupid joke app that a lot of people would download and use because people like simple, stupid joke apps.
I've complained about this before, so apologies to everyone who has heard this point -- the next post is just a wee bit below this one, feel free to scroll -- but until Apple offers developers a firm set of guidelines, developers will continue to be ticked off by seemingly arbitrary rejections like this one. Apple is clearly refusing applications that fail the sniff test -- and yes, I know that's a little more apt a metaphor than this application deserves. "Pull My Finger" is tasteless. Apple should have rejected it for that reason, rather than pulling new reasons out from thin air.
Apple needs to step forward, and do so soon, with a clear set of guidelines that explain to developers exactly what to expect when they press that "submit" button for their new app. Developers shouldn't be wasting Apple's time with unpublishable software. Apple should not be wasting Developers' time with a secretive and arbitrary review process.
Is Apple's oldest NYC retail store causing agita for its well-heeled neighbors in SoHo? AFP and Dow Jones are reporting that the SoHo Alliance, an umbrella community organization, has complained to city officials and Apple execs about a litany of issues with the popular outlet. Crowds outside the store (sometimes overnight) have blocked streets and left trash behind, to the frustration of nearby residents.
The recent Jonas Brothers in-store concert may have been the final indignity for alliance director Sean Sweeney. "This concert attracted thousands of young teenage girls who screamed incessantly on the street for hours for their idols, blocking traffic, injuring one resident in the crush, and inconveniencing scores of other people and businesses."
I suppose there's a price to pay for being busy and popular. Considering that the immediate vicinity of the store is home to scores of restaurants, bars and high-end boutiques, it's surprising that Apple is the biggest quality-of-life offender in the area, but maybe it's time for some of the bigger draws to move to the 14th Street store instead.
An Apple Premium reseller in the UK sent us these photos of an Apple recycling information mailer they received: but the mailer itself was sent in a decidedly non-green way.
From photos the reseller sent, it appears the mailer consisted of two sheets of standard A4-sized paper. Those sheets of paper were placed inside a large, yellow clasp envelope. That envelope was then placed inside a corrugated cardboard box. The box was then mailed to the UK from Switzerland.
While all of these materials are recyclable, it seems like a little bit of a waste to send what could have fit in an everyday DL-sized envelope (that's about the size of a number 10 envelope for us Americans) in ridiculously oversized packaging. Plus, it probably would have saved them a bundle on postage.
Apple has been making a concerted effort to reduce its environmental footprint: not only with the program mentioned in this mailer, but for everything from iPhone packaging to how it makes its displays. Surely this isolated incident isn't representative of the company as a whole, but still. Sheesh.
On Monday, a group of Apple technical staffers filed suit against Apple alleging that the company denied them overtime pay and meal compensation. Both the pay and meal compensation are required by California state law. The suit also claims that many Apple employees are subjected to working conditions that are similar to indentured servitude.
The lead plaintiff in the lawsuit, David Walsh, was an Apple network engineer from 1995 to 2007. He stated that he was often required to work more than 40 hours a week, miss meals, and spend evenings and weekends on call without any overtime pay or meal compensation. [Author's personal comment: this is not unusual in the tech industry]
Walsh alleges that Apple deliberately classified Walsh and others as management employees so that they would not receive overtime compensation as required by California law for hourly employees. The class action suit also seeks to include the staffers at Apple Stores as plaintiffs.
Should the plaintiffs win, Apple could be required to revise its compensation practices and pay retroactive compensation to many present and past employees. Apple has not responded to the complaint.
iPhone Atlas is reporting that Apple has a way to blacklist and remotely remove applications from your iPhone. According to the post, the iPhone will remotely "phone home" and check a posted blacklist of bad applications. These speculations are based on a URL found on Apple's site with references for a blacklisting mechanism:
Jonathan Zdziarski, an iPhone hacker, says nothing has been blacklisted as of yet. However, the mechanism is there, and the iPhone could call in on occasion to see what has been blacklisted. Zdziarski says that Apple could have the ability to shut down applications you've purchased from the App Store.
While this may sound like a privacy violation, our sources tell us that Apple has put this tool into place as a security measure to shut down rogue apps if needed, and it could simply be a proof of concept that hasn't yet been implemented for actual takedowns. We're not convinced that this is new, considering that the only entry in the unauthorizedApps list is dated "2004" and is clearly a test entry.
How often does Apple admit a mistake? It's a once-in-a-blue-iMoon occurrence, but now that Ars Technica is reporting the contents of an internal Steve Jobs all-hands email regarding the MobileMe launch challenges we can add one more instance to the tally board. Jobs apparently acknowledges that trying to rush the MobileMe migration while pushing iPhone 3G hardware and iPhone 2.0 software out the door (not to mention the iTunes App Store) may have been too much to bite off at once.
The money quote from the letter (yet to be confirmed by TUAW sources) is here:
"The MobileMe launch clearly demonstrates that we have more to learn about Internet services," Jobs says. "And learn we will. The vision of MobileMe is both exciting and ambitious, and we will press on to make it a service we are all proud of by the end of this year."
Ars also notes that MobileMe management will now be centralized under iTunes exec VP Eddy Cue, who will be leading the charge for all Apple internet services across the board. We've all been through the MobileMe ups and downs during the first weeks of the service; it's nice to know (belatedly) that Apple top brass is clued in.
Put yourselves in Nullriver's shoes for a minute: you create an app (NetShare - see TUAW passim), which as far as you can tell does not break any of the App Store rules. You submit it to Apple for inclusion. It passes the vetting procedure (so it must be OK, right?) and goes live online, for sale to real people.
Then it disappears, with no warning. No explanation is given. Then it returns. For a while. Again, no explanation. Then it goes offline again. (I've now lost count how many times NetShare has been online, then offline, rinse and repeat.)
And throughout all this, you get nothing from Apple. No explanation. No reason. No polite email asking you to wait. Not even an impolite email. Nothing.
The distance between good intentions and actual results seems to be getting longer and longer. While Apple did release a security patch yesterday that included a fix to BIND for the highly publicized cache poisoning exploit -- some time after most other vendors got updates out to customers -- that fix doesn't seem to be, you know, actually working.
Multiple sources have noted that Apple's DNS patch, at least on Mac OS X 10.4 and 10.5 client versions, isn't implementing the key feature that's meant to block cache poisoning: port randomization on requests. While the same version of BIND running on Linux systems behaves as expected, Mac OS X machines doggedly issue DNS requests on sequential ports, making them far more vulnerable to spoofing by malicious folk.
This may seem like an esoteric vulnerability, and indeed for most Mac users the more important question is whether or not your ISP or network manager has patched the primary DNS servers you rely on (you can check your DNS server status via Dan Kaminsky's tool here). The behavior of Apple on this security issue, however, is very troubling. Waiting weeks to issue a patch for a key vulnerability and lagging behind other OS vendors is bad enough; shipping that patch only to have the user community discover that it doesn't work worth a bucket of warm spit ... that's not the act of a company that claims to care deeply about the security of its customers.
Update: Kaminsky suggests that we lighten up; Mac OS X Server (which would be the most vulnerable to attack, if it serves as the primary DNS for your network) has been patched, even if the client patch isn't behaving properly yet.
When faced with the dilemma of upgrading my iBook G4 in June, I started looking for a replacement that would have the same performance as my Intel iMac. I decided upon getting a MacBook Pro 15". With money in hand, I eagerly clicked the "buy now" button on Apple's website. Little did I know that I would be trading in my MacBook Pro more than 6 times over the next 2 months.
I received my first MacBook Pro, and it was beautiful. I loved everything about it. However, after 2 weeks of use, I started noticing the screen striping symptom that others before me have noted. This problem usually occurred after charging the computer from a half-filled battery and unplugging the MagSafe power cable. I didn't think anything of this problem, since it only happened once or twice. After another week of use, the striping problem started becoming an everyday part of charging the computer. I called Apple and even emailed them the picture that you see above (minus the additional note) -- they did nothing and said it was a "software glitch."
The first MacBook Pro did have another problem: When I went to check my email one day, every program would crash repeatedly. I immediately ran the Apple hardware test (AHT) to find out what was going on. As any unlucky person (me) would have it, the memory sticks were dead. I called AppleCare, told them all of the problems I was having and then told them about the AHT results. They set up a replacement order since I was having hardware problems within the first month of ownership.
Continue reading to learn more about my MacBook Pro woes.
Good old David G., the mysterious author of Apple's MobileMe Status blog, has good news for that unfortunate 1% of MobileMe users who couldn't use their email accounts. All email services, including 'historical messages,' have been restored (it is unclear if this means all messages are back in their right place).
Apple has set up a special MobileMe Mail Dedicated Chat Support to help those folks who had email issues sort everything out. If you were one of the chosen few, head on over there to discuss what happened with a friendly, and helpful, Apple support tech.
In addition to resolving the email issue, David G. says that nasty syncing issue (you remember, the one that was wiping people's iPhones of any and all contacts) has been corrected as well. Most MobileMe users didn't see this issue, and for the few that did it seems to have sorted itself out, however, if you're still having this issue check out Apple's KB article for the solution to your syncing woes.
Hey, David G., since it looks like you have MobileMe under control can I report a bug about the MobileMe Status blog? Thanks! There is no way to link directly to a post, like the post I'm talking about right this second, which makes it hard to make sure people see the entry I'm talking about. I'm sure you just forgot to click a button in iWeb or something.
Another day, another new way for MobileMe to anger folks. Today we are hearing lots of grumbling about people seeing their contacts and calendars disappearing from their iPhones after a sync with MobileMe. Luckily, it looks like it is only the iPhone that is wiped, the contacts/events are still on their Macs.
Wyn called Apple support and they suggested disabling automatic syncing and manually syncing to clear up the problem. That gives a new definition to push.
This seems like a good time to remind people to back up your data before you enable any sort of automatic syncing. Read on after the jump to see how to backup your Address Book and iCal events, just in case. Thanks to everyone who sent this in and thanks to FailMe for the graphic.
Update: It is 8:30pm on the east coast of the US, and Apple has just posted this note on the MobileMe System Status: "Some MobileMe members may be unable to sync new, edited, or deleted contacts, calendars, and bookmarks over the air between computers and mobile devices (iPhone and iPod Touch). Service will be restored ASAP. We apologize for any inconvenience."
How big is one percent? If it's a surcharge on your restaurant check, not that much; if it's a point on your mortgage, ow. If it's a chunk of .Mac/MobileMe email account holders who are left hanging for a week without access to their email... well, let's just say that anyone in that select and sorry lot who used a mac.com email address for professional or vital communications is justifiably furious right now.
The good news, if you can say that under the circumstances, is that the outage that started July 18 may be coming to a close. Apple has posted a tech note on the ongoing issues, launched a blog to cover the MobileMe introduction challenges, and provided some additional details about what happened. As of 10 pm PDT last night, the one-percenters should be able to log into MobileMe webmail and retrieve messages from the July 18–25 outage window, though none from before the problem started are available yet. Apple also warns affected users NOT to change MobileMe passwords, aliases or storage allocations until the problem is cleared up, so be alert.
As the problem was triggered by a "serious issue" on one of Apple's mail servers, some messages got dropped in the bit bucket and will never come back (unless you have them cached in a local client like Mail.app, Entourage, Thunderbird or Outlook). Apple's statement:
While the vast majority of your email messages will be fully restored, a small percentage of email messages in the affected accounts have regrettably been lost. This includes approximately 10% of messages received between 5:00 a.m. PDT on July 16 and 10:20 a.m. PDT on July 18. We sincerely apologize for any email messages you may have lost.
Apologies are well and good -- but considering the MobileMe terms of service, that's about all you can expect to see, as Apple isn't liable for lost business or damages due to the outage. If there's a lesson in this, maybe it's that mission-critical users should own their own domains and public-facing email addresses, so that they can redirect incoming mail in a crisis. Depending on a single provider for mail (even ones with a reputation for reliability) can bite you. Written by Michael Rose. Thanks to everyone who sent this in.
Imagine you are a software development company that has been around for 11 years, with award-winning titles for mobile computing devices. You follow the rules, you submit iPhone versions of your applications to the App Store, and yet you still haven't seen your programs make it to the store.
This is the boat that a lot of developers are in, but it is particularly frustrating for Ilium Software. Ilium has sold two well-respected applications -- eWallet and ListPro -- for Palm OS and Windows Mobile devices for years, and has a number of other commercial and free mobile applications on the market.
According to Ilium spokesperson Ellen Craw, eWallet has been "in the queue" at Apple for over two weeks, and they can't get any word from App Store personnel on when their highly anticipated app will actually appear online. The comments in Ilium's blog are particularly revealing, as longtime customers are also frustrated by the black hole at Apple.
Having used Ilium's products before, I'm waiting for both ListPro and eWallet to show up in the store to fill those niches on my iPhone. What other great products are being held up by Apple? We'd love to know!
As I'm sure many of you have noticed, many of the applications from the App Store are crashing frequently. Basically, an app I want to launch opens a blank screen, pauses for a moment, and then drops me back to my home screen without so much as an apology. Worse, it may even reset the phone. I've found with most of them that a simple reboot will allow them to launch again, but that's getting old and doesn't always help. You're probably, like me, thinking that it's a shame that so many developers rushed so quickly to make the App Store deadline and ended up putting out unstable applications. According to the development community, though, it's not their fault ... it's Apple's.
Anonymous developer sources are reporting that they've been poring over crash logs and discovering that the reported crash has nothing to do with their application. There's a growing consensus that Apple has released a highly unstable "final" version of the 2.0 firmware. So, maybe it's more of a shame that Apple, who laid the groundwork for a multitude of useful and exciting applications, rushed development and failed to build a better foundation.
Personally, I haven't seen the crash logs, and I am -- legitimately, in my opinion -- accepting the word of veteran developers. I also can't speak for individual applications, there are some pretty shoddy offerings in the App Store which may have their own reasons for crashing (i.e. "I look like I was written by a Windows developer, I can't show my face!"). There are also several applications whose requisite servers were overloaded initially, but are getting back on their feet now. But for a lot of the random crashes, it has nothing to do with the app itself ... so, before you write that complaint email, check your tone ... you might be getting snarky with the wrong party.
A few days ago I posted about the problems that the 10.5.2 update was causing with audio recording hardware and software from various manufacturers. Today, in a follow-up post to his original roundup of the issues at hand, Peter Kirn weighs in on Apple's accountability.
Kirn's position is that Apple is responsible because all the evidence suggests that the problems lie with the 10.5.2 update, not any one vendor's drivers. "Problems haven't affected everyone," says Kirn, "but they have been widespread enough that we have a right to be disappointed. As a user, I think I have the right to be disappointed. As a writer, it's my obligation to point it out. And I hope they do better in the future."
Of course, as Peter points out, rumor is that 10.5.3 is right around the corner, so hopefully these problems will disappear and Trent Reznor can get back to making music instead of standing in for angry Mac-using music geeks in my music-related posts.
Is Apple's 
An Apple Premium reseller in the UK 
On Monday, a group of Apple technical staffers filed suit against Apple alleging that the company denied them overtime pay and meal compensation. Both the pay and meal compensation are required by California state law. The suit also claims that many Apple employees are subjected to working conditions that are similar to 
How often does Apple admit a mistake? It's a once-in-a-blue-iMoon occurrence, but 
The distance between good intentions and actual results seems to be getting longer and longer. While Apple did 
Good old David G., the mysterious author of Apple's 
Another day, another new way for MobileMe to anger folks. Today we are hearing lots of 
Imagine you are a software development company that has been around for 11 years, with 
As I'm sure many of you have noticed, many of the applications from the App Store are crashing frequently. Basically, an app I want to launch opens a blank screen, pauses for a moment, and then drops me back to my home screen without so much as an apology. Worse, it may even reset the phone. I've found with most of them that a simple reboot will allow them to launch again, but that's getting old and doesn't always help. You're probably, like me, thinking that it's a shame that so many developers rushed so quickly to make the App Store deadline and ended up putting out unstable applications. According to the development community, though, it's not their fault ... it's Apple's.
A few days ago I posted about the 
