Michael Jones

Michael is a software engineer, security enthusiast, mobile developer & all-around jack-of-all-trades geek. With experience ranging from telephony & call center operations to airline reservation systems to financial billing platforms, he has worked with a diverse range of tech throughout his career. But at the end of the day, Apple has always held a special place in his heart and on his desk -- from the Apple II range and assortment of Mac Pluses, LC's, and other models that he grew up with to the workhorse Mac Pro line to nearly every generation of today's iOS devices. Here at TUAW, he occasionally writes about the latest news in the Apple world, but he mostly uses his development skills to support the rest of the team behind the scenes. He lives with his family in Salt Lake City, Utah. Follow @TuxToaster!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');

Articles by Michael Jones

Snow Leopard quirk prevents opening groups of recently downloaded files
Reports of an odd bug affecting downloaded files in Snow Leopard have been circulating Apple's discussion boards recently. As reported by TidBITS, the issue appears to be affecting all computers running Snow Leopard. While different users have reported varying symptoms and differing circumstances, it essentially boils down to this: if you download a group of files, and then attempt to open the entire group of files at once (rather than opening each file individually), chances are either some or all of the selected files will not open. My initial response to this was that it could possibly be one of those "it's not a bug, it's a feature" ordeals. We have already seen some indications that Apple is working on enhanced security and virus protection in Snow Leopard, so it stands to reason that the operating system may be simply trying to prevent what it thinks is malicious activity by imposing restrictions on what you can and can't do with a newly downloaded file. Of course, that's just my theory, but I'm apparently not the only one who has explored that possibility -- a reader on the Mac OS X Hints forum discovered some hard evidence supporting that theory. In OS X, newly downloaded files are flagged with a "quarantine" attribute, which remains until the file is opened. If this attribute is set when the file is launched, and the file is an application, you would receive the typical "This application was downloaded from the Internet" confirmation before the application is allowed to continue launching. This is nothing new in Snow Leopard, but it would seem that the additional protections and scanning that were added to Snow Leopard most likely prevent opening multiple files so that each file can be individually checked before it is launched. Whether or not this is a serious bug or a minor inconvenience depends entirely on your workflow. Personally, I find that I don't often open multiple files from Finder, as most of the applications I use have the ability to select multiple files from their Open dialog. I can easily see where this might pose significant problems, however. For example, if you do a lot of work with graphics, you might download a several photos from a client, highlight them and open them with a custom tool that automatically resizes and processes for you. With this bug in play, that task would become much more difficult if you had to open each file individually. So what about you? Is this bug bugging you, or is it a non-issue? If you are affected, feel free to chime in with your experiences on the discussion boards, and be sure to let us know in the comments!
Dropbox the iPhone app has dropped
If you've been waiting patiently for the Dropbox app [iTunes link] to hit the App Store, your wait is over. The app has arrived, and brings with it the simplicity that Dropbox users have come to know and love. Since Dropbox itself is a free service, it's a pleasant surprise to see a simple, easy method for creating a new Dropbox account right off the bat if you don't happen to already have one. The app just asks for a name, e-mail address and password, prompts you to accept the terms of service, and creates the account. During my testing, I did encounter a problem where I would receive a nondescript "Account creation failed (null). Please try again." message, which I'm guessing may be due to high load on their servers. Still, this is not an encouraging encounter for new users. Once logged in, everything worked pretty smoothly. On first login, You are presented with a brief welcome document that highlights some of the features of the app. Backing out of the document will take you to your Dropbox, which quickly lists any of the files and folders you may have in there. The app features built-in document preview for several types of files, including PDFs, text documents, spreadsheets, pictures and videos. You can also tag files as a favorite by tapping the star at the bottom of the file viewer, which adds the item to the favorites panel and caches a copy locally on the device so that it's immediately available. An unexpected feature is the ability to take pictures, video, or use existing media and upload them directly to the Dropbox. This could definitely be handy if you need to take a quick video and have it available on another machine without having to plug in your phone and wait for it to sync. Also unexpected, but incredibly welcome, is the massive amount of documentation that is available from inside the app's settings panel. In addition to giving you general details about your account, the settings panel offers a link to watch a video about how Dropbox works, take a tour of the features, or browse their complete online help library, without having to leave the app. As many apps fall short in this area, it's refreshing to see such detailed documention available, let alone right from the app. A couple of side notes: As I mentioned above, the new user signup does not appear to work properly sometimes. I'm guessing this will be fixed in short order, though. You can log out of your Dropbox account by tapping the Unlink iPhone from Dropbox button on the settings panel, but beware that you will loose any favorites you have stored (the app does warn you of this). And finally, when you do logout of your account, the app just disappears from the screen, as if it crashed, although you are successfully logged out. In my eyes, these are minor issues (well, aside from the signup problem), and will likely be addressed with future updates, but still good to watch out for. All in all, this is a very well done, simple app that connects you with an already great (and free) service. It's available now in the App Store for free. %Gallery-74280%
Apple sets out to prove that there is an app for just about everything
Since the birth of the App Store, Apple has oft stated "there is an app for just about everything." Now, it seems they have come up with a great way to prove their claim. Apple has added an "Apps for Everything" section to their website, complete with a wide range of selections from Apps for Cooks, to Apps for Managing Money, to Apps for Moms and Dads. Each section is then broken down into different tasks or activities that are associated with the group, and highlighting a particular app for that item, complete with screenshots and a link to the App Store. Based on recent trends, including our own "5 Apps" series, it's easy to see that breaking down the massive list of apps available in the App Store and grouping them by different occupations or activities is a great way to bring otherwise hard-to-find apps to the spotlight. It's good to see that Apple has come up with a nice, clean way to do this on their own website, and I'm sure it will serve as a great resource to users who are looking for the perfect app. [via LoopInsight]
It's a bird! No, it's an app! No, it's Tweetie 2 for iPhone!
Users of Tweetie, the popular Twitter client for both Mac and iPhone, have reason to be excited: a new version of the iPhone app, Tweetie 2 (aptly codenamed "Bigbird"), is confirmed to be on the way. In a preview of the new version, Scott Kleinberg of ChicagoNow detailed his experiences with beta builds of the upcoming release. From the screenshots provided, it's clear that several interface improvements have been made, including a quick menu that provides easy access to several new features while posting a tweet. Other improvements include the ability to send video tweets, persistent session handling that restores the app to its previous state, conversation threading, draft management, and geotagging. While Scott's review suggests that the changes and improvements make Tweetie 2 feel like a whole new app, Tweetie developer Loren Brichter indicates that it really is -- it's a complete rewrite from the original app. In addition to the major features, the new version also boasts integration with several 3rd party services, and a host of configuration options, from new gesture options to custom Twitter API settings. Of course, not everyone will be happy with the update. There is already a stir among beta testers over the app's use of pinstripe backgrounds on the profile and single tweet views. Also, there is the issue of cost: Tweetie 2 will set you back $2.99, as it is being offered as a new app instead of a free upgrade to existing users. When it comes to upgrades, most desktop applications follow a pattern where minor updates (such as upgrading from version 1.0 to 1.1 or 1.1.2 -- often refered to as "point releases") are provided free of charge, and major updates (from version 1.0 to 2.0) usually require the user to purchase the new version of the software. With iPhone apps, however, Apple does not provide a system to allow developers to do this. Developers can release upgrades and bug fixes as free updates to their applications, but if they invest a lot of time into a major update to their app, they have to submit it as a new, different version of the application rather than an upgrade to the old version, and there is no option to allow users who have perviously purchased the original app to receive a discount on the new version. So users are faced with having to pay full price for the upgrade, which in this case, is another $2.99. In my opinion, this is not an unreasonable amount to pay for a major upgrade to an already great application, but there are users who feel they shouldn't have to pay for the upgrade. My advice to them? If you can't spare $3 for the amount of time and effort that was put into making a decent, feature-rich upgrade, don't bother using it. Stick with the original Tweetie or find another app that you're willing to pay for. So, controversy aside, Tweetie 2 looks very promising. The latest beta build that was provided to developers is expected to be the final build, and if things go well, we should see it hit the App Store in the coming weeks. An update to the desktop version of Tweetie is also in the works, and will probably surface after the iPhone app is released. Update: TUAW reader Ahmed drew our attention to this tweet, indicating that Tweetie 2 has been submitted to Apple! Assuming there are no hold-ups, we can probably expect to see it hit the App Store in a few weeks. What do you think of the new version? Will you be upgrading when it's released? Let us know in the comments!
USB-IF to Palm: "Oh really? You've got some explaining to do."
Didn't you hate it when you were a kid, and you would complain to an adult about something one of your siblings was doing, just to end up getting yourself in more trouble than they ended up in? Well, you might say that's exactly what is happening to Palm and the ongoing dispute with Apple over the Pre's ability to sync with iTunes. The company has landed itself in some hot water after drawing the attention of the USB Implementers Forum (USB-IF) by filing a complaint against Apple for violating "the letter and spirit of the USB-IF Membership Agreement," which is "intended to facilitate interoperability between USB devices." What that's referring to, of course, are Apple's repeated attempts to block the Palm Pre from syncing with iTunes. The whole question of whether or not Apple is in the wrong by doing so is entirely debatable, but the USB-IF seems to be of the opinion that Apple is following the letter of the law: "In the view of the USB-IF, Palm's allegation (if true) does not establish that Apple is using its Vendor ID (VID) contrary to the USB-IF's policies... Therefore, under present USB-IF policies, the USB-IF does not consider the alleged use, without more, to be 'improper.'" To summarize, the USB-IF does not believe that Apple is in violation of the agreement, based on the information provided in Palm's complaint. What is interesting with this chain of events is how Palm continues to shoot itself in the foot trying to find a resolution. Rather than work out a deal with Apple or write a custom application to legitimately communicate with iTunes, Palm has chosen the sly path of attempting to trick iTunes into working with the Pre, first by simply identifying the device as an iPod that was made by Palm, to actually using Apple's assigned USB vendor identifiers to completely masquerade as a true Apple iPod. Perhaps even more startling, however, is that Palm is completely open about the whole process, even going as far as detailing the workaround in the complaint to the USB-IF, saying "Palm will shortly issue an update of its WebOS operating system that uses Apple's Vendor ID number for the sole purpose of restoring the Palm media sync functionality." Although openness is usually a good thing, it seems that Palm may have encountered too much of a good thing: the USB-IF turned the tables, and hinted that Palm itself may be in violation of its own agreement (emphasis added): I attach for your information the USB-IF's adopted and published policy regarding Vendor Identification Numbers (VIDs). Under the Policy, Palm may only use the single Vendor ID issued to Palm for Palm's usage. Usage of any other company's Vendor ID is specifically precluded. Palm's expressed intent to use Apple's VID appears to violate the attached policy. Please clarify Palm's intent and respond to this potential violation within seven days. What's next for Palm? Will the company finally decide to work something out with Apple? Will Palm start embedding USB chips out of refurbished iPhones so that it isn't technically misreporting the device's identity? Only time will tell, and in the meantime, at least we can look back and say "Palm, we told you so."
Push for Gmail: it's here, it works, and it's limited
If you use Gmail, you have something to be excited about today, because you can finally have new email messages pushed directly to your iPhone when they arrive. For many users, however, their first response is "it's about time!" and others have even gone as far as saying "it's finally here, no thanks to Apple." This new feature, unveiled this morning by Google, has even been called a "workaround" to Apple's alleged refusal to support push email, but in reality this isn't the case. Push: What is it, and how does it work? To understand why push services have not been available before, let's first discuss what exactly push is. When a client (be it a mail program, Twitter client, or web browser) needs to notify a user when new content or information is available, it has to periodically connect to the server and check for changes. This is the way email clients have worked for years: the client checks with the server at a defined interval (usually every 5-15 minutes), downloads any new messages, and notifies the user that new mail has arrived. Many other services, such as RSS feeds, Twitter, Facebook, and even the Gmail website work the same way; they just check the server more often, which gives the appearance of real-time notifications. Other services, such as instant messaging clients, maintain a constant, active connection to the server at all times. When new information is available for the client, the server sends, or "pushes" the information directly to the client as soon as it is available. In corporate environments, mail services such as Microsoft Exchange have paved the way for push email, by having the mail client (usually Outlook, Entourage, or other clients that support Exchange) maintain an active connection to the mail server, which allows the server to notify the client immediately when new mail arrives. Read on to find out how Gmail push works, and what you need to know to get it set up on your phone.
AT&T & MMS: So close, some of us can taste it
Well, it looks like they were telling the truth, for once. Last weekend, a friend of mine just happened to forget that my iPhone couldn't receive MMS messages, and sent me a picture he had taken. So needless to say, I was surprised when I saw the MMS notification, complete with picture, show up on my phone. I was fully prepared to hop on to TUAW and write up a post, letting everyone know that MMS was turned on a full three weeks ahead of schedule. To be on the safe side, I decided to check with others to see if MMS was working for them. Unfortunately, everyone I asked said MMS was still not working on their phones. Here at TUAW, we have received several tips over the past few months from individuals who have indicated MMS had suddenly started working for them. Many of these were from people who had also installed an updated carrier settings profile to their phones, which has produced mixed results across the board, ranging from MMS actually working to accidentally removing Visual Voicemail and even the basic ability to make phone calls. Even with these profiles installed, however, most people were still unable to use MMS due to settings on their AT&T account which prevent iPhones from sending media messages and filter incoming messages through their web-based "Multimedia Messaging" platform. For the record, I was running the iPhone 3.0 software, and I had previously modified my carrier settings, although that hadn't really made much of a difference until now. I had been lucky, in that I had found a profile that did not break anything, and had even temporarily enabled tethering on my phone, which I successfully used for about five minutes to try it out (although when I later tried to use the tethering during a recent power outage, the option mysteriously disappeared from the settings panel after I turned it on). So I had to draw the conclusion that my newfound ability to send and receive MMS messages was probably related to the carrier settings I had previously tinkered with, and I was doubtful that it would last. Now here we are a week later, and MMS is still working for me. But what's even better: reports are flowing in from around the country that MMS has started working in different markets. There are still quite a number of people out there that don't have it yet, but it looks like AT&T is actually serious about meeting the September 25th deadline. Yeah, it's definitely not "later this summer" as promised, but at least we are finally seeing some progress instead of just vapor dates and promises. For those who are wondering where MMS has landed, HowardForums has a thread running with many people reporting which locations are up and running. Also, it's worth mentioning that the majority of users who have reported MMS as working have the "AT&T 5.0" carrier profile installed, which is included as part of the iPhone 3.1 update. So be sure to update if you haven't already! Thanks to everyone who has sent tips in regarding MMS in their area.
Apple Store is currently down
Yes folks, it looks like the online Apple Store is currently down. Given that it is 10:00 PM on a Saturday night over in Cupertino, I'd say chances are pretty good that it could just be some simple maintenance, but you never know. We'll keep an eye out for any changes and post an update if anything exciting happens!
Apple Remote Desktop 3.3 now available
Apple has released version 3.3 of its remote administration tool, Apple Remote Desktop (ARD). The update is available both via Software Update, and from the Apple website. According to the release notes, the update comes with a number of improvements, including the long-desired ability to send function keys and system shortcuts (Force Quit, cmd-Tab for application switching, cmd-shift-Q to log out) to the remote Mac; previously those commands would execute on the administrator's machine, which could cause undesired behavior. Also included are support for wide-area Bonjour connections and improved performance when using a shared screen. If you're just starting out with ARD, be sure to check out some of the great tutorials Apple has posted online. From getting set up, to providing remote assistance to users, to automating routine tasks; as Apple might say, "there's a tutorial for that." Thanks to TUAW reader Jim for giving us the heads up!
Clarification on the iPhone Spotlight email issue
Earlier today, I posted about the ability to find previously deleted emails using the Spotlight search on the iPhone, adding to the already intense swarm of news surrounding this issue. My findings were that, by ensuring your trash folder was emptied and refreshed, the problem appeared to be solved. However, many of you responded indicating that this did not work for you, and that you were still seeing cached messages. Then Cult of Mac posted an update to their original piece, suggesting that the problem was more specific to POP accounts. Although I had tested both POP and IMAP accounts with similar results, I decided to investigate further. First, to clarify: The problem here is *not* with Spotlight caching the contents of your email, as many have suggested. Spotlight simply indexes the available content on your phone, and logs a pointer to it. When you tap a search result, it opens the associated application and tells that app to view the content. In this case, it sees an email message and asks Mail.app to open it, which it does, because Mail.app still has the message content stored locally. Secondly, this appears to be specific to POP accounts. On IMAP or Exchange accounts, deleted email messages do appear in Spotlight results until the trash folder is emptied, as described in my earlier post. I created a fresh account and configured it for POP access, then downloaded the mail. Searching spotlight, I could see the message I was looking for. I then went back to the message and deleted it, and that's where the fun starts. I conducted this same test multiple times, and found that sometimes, the message would now show up in Spotlight twice, one result opened the message, intact, with the Inbox listed as the folder to return to; the other displaying a message in the trash folder, but with an error displaying the body of the message. Other times, I would only see one result, pointed directly to the trash.
Prevent Spotlight from resurrecting your deleted emails on iPhone
Note: The problem discussed below behaves differently depending on the type of email account being used. Users of POP mail accounts are indeed noticing a problem with deleted email messages appearing in Spotlight search results. Please see this post for updated information. Our friends over at Engadget have highlighted a Cult of Mac post that, at first glance, appears to have found a bug in Spotlight's caching of email search results on the iPhone. The idea is that after you delete an email from your inbox in the iPhone's Mail.app client, you can still locate and open the e-mail using Spotlight search, if you know the subject of the message. What's really happening, though, is what Apple might otherwise call "user confusion." When you delete an e-mail message in most mail clients, the message isn't magically deleted, but instead moved to a "trash" or "deleted messages" folder. Being a folder, it is indexed by Mail to provide an unread count, as well as by Spotlight so that you can easily find messages in the folder. When you search for the email, it shows up in Spotlight and opens in Mail because the message still exists in your trash folder. All right, so what can you do to avoid this? Well, you need to empty the trash folder from your email. With many providers, you can just go to the trash folder, and delete the message from there to permanently remove it. The problem there is that, if you use a service like Gmail, the message doesn't really get deleted when you do this because of the way Gmail translates its labels into folders. Gmail's Trash folder is also set to purge itself after 30 days by default. Your options? You either have to use the Gmail web interface in Safari, or if you don't mind tweaking your Gmail settings, you can enable the Advanced IMAP Controls Lab and then change your Gmail settings to immediately delete messages instead of using the trash folder. (Note that if you have your "All Mail" label configured to show up in IMAP, you will need to either disable it, or delete the message from that folder on the iPhone as well. See this thread for more information.) Once you've deleted the message, go in to the Trash folder and hit the refresh button to ensure that the message is no longer listed, which will remove it from the local mail cache. This should also clear up Spotlight's index so that the message no longer appears. By now, you're probably wondering if this is really something to worry about. In my opinion, it really depends on how you manage your email. If you rarely delete messages, or you just delete things that are not of interest to you, they will most likely disappear from your trash folder after a specified time period that is set by your email provider (usually somewhere between 7 and 30 days.) However, if you intentionally delete messages with the idea that the message is unretreivable, then you should probably consider testing this out for yourself to see if it affects you. Again, with many providers, just periodically deleting the contents of the trash folder will do the trick. If you use Gmail, or your company's email services are hosted by Google, then you may need to log in to the web interface periodically to empty the trash, or you can look into the available configuration options, if you feel comfortable doing so. So in reality, this isn't really a bug as much as it is what I would call "intended, but unexpected behavior." Many people simply forget that the trash folder exists, particularly on the iPhone where you don't always see it sitting off to the left hand side of your inbox. Checking your trash folder for any unintentionally deleted items, and cleaning out the old messages periodically, isn't really a bad habit to get into. With that said, however, I do think that Apple could improve this behavior by implementing some simple changes like adding an "Empty Trash" button to the trash folder, showing the count of all messages in the trash instead of just unread messages (so that it's easier to notice there are messages in there), and having Spotlight either ignore deleted messages like Leopard's Spotlight does, or at least indicate that they were found in the trash. What are your thoughts on this? Do you consider this to be a bug, or do you think it's just a place that Apple could improve the experience on? Let us know in the comments! Update: Leander Kahney has posted an update to the original Cult of Mac post that clarifies this issue a bit more. It seems that accounts using POP are configured by default to remove messages after one day or one week, thus causing them to continue to appear in Spotlight search results. Unfortunately, there isn't an option to remove them immediately, however, only after a day, one week, one month, or never. Because of this, Spotlight still sees them in the index, and Mail still contains a cached copy of the message until the time limit configured in the settings is reached. If you'd like to check out this setting for yourself, go to the Settings app, tap on Mail, Contacts & Calendars, and choose the POP mail account you want to modify. Scroll down and choose Advanced, and the retention settings will be at the top of that page under Deleted Messages. It appears the default for a new account is to retain messages up to one week. So this is still the OS doing what it's configured to do, but there really should be an option to remove messages immediately here. If Apple were to add an option there, and/or remove Spotlight's ability to index deleted messages, the problem would be solved. Update 2: After further investigation, it appears that some messages deleted on POP accounts do disappear from Spotlight, while others show up long after the message is deleted. I have conducted several tests on this situation, including on different versions of the iPhone OS, and have posted an update with details.
Yeah, there's an app for that. But for how long, and at what cost?
With the recent kerfuffle surrounding the removal and rejection of Google Voice apps from the App Store, many developers are beginning to question the trust they have placed in Apple to provide them with a reliable system for developing and distributing applications.Generally, the major hurdle associated with iPhone development is getting approved by Apple. It's no secret that this process is often quite frustrating, and sometimes downright arduous. Developers often wait several weeks without any response before they are suddenly rejected, and then they must make the requested changes (if possible), resubmit their application, and again wait for a response. But once they have put your app through the paces, and presumably have double and triple checked to ensure that you have complied with the terms, you're safe, right? Your hard work has paid off, Apple has accepted your app, and now you can move on.Wrong. As the developers of GV Mobile and VoiceCentral recently discovered, Apple can take an app that was previously given the all-clear, decide that it now duplicates native functionality of the iPhone, and yank it from the App Store in a matter of minutes. Needless to say, there are some serious flaws in this process. First, the functionality provided by both of these apps isn't actually provided by the iPhone, so there's really nothing to duplicate, unless Apple is going to start expecting developers to predict future features and avoid duplicating those too. Then you have the fact that the feature sets provided by the apps and the iPhone itself have not changed since Apple approved them in the first place, so if they truly are duplicating native functionality, they should have been rejected from the start, not months after they were approved.Now one might also argue that some features offered by Google Voice do overlap with the iPhone, such as the SMS and voicemail functions, although contrary to popular belief, Google Voice is not a VoIP service and doesn't really compete against AT&T. But even if you concede that point to Apple, couldn't they just ask the developers to remove those features and resubmit? What about the other apps -- like Skype, TextFree, or iCall -- that offer similar feature sets, are they going to disappear too? And if AT&T is really responsible for this, as has been suggested previously, why was the app pulled from the App Stores of other countries? Why not just honestly tell the developer that the app is being pulled at the request of the carrier?
iDisk iPhone app arrives, there is much rejoicing
You have waited with varying degrees of patience, but your wait is over: the MobileMe iDisk app, in all its officialness, is now available on the App Store.The iDisk app allows you to view the contents of your MobileMe iDisk straight from your iPhone, and offers some nice options, such as adjusting the amount of local storage used on the phone for recently viewed files.Does it live up to your expectations? Check it out, and be sure to tell us in the comments what you think about it![H/T AppAdvice.com]
Update: Promo codes again allowed for 17+ apps
Recently, we reported that developers were not able to request promo codes for their iPhone apps if the app had received a 17+ rating due to having an embedded web browser, unfiltered 3rd party content, or contained excessive violence or sexual content. This restriction severely limited the ability of the developers to distribute promotional copies of their software to generate publicity and awareness of the app.Several other outlets picked up on the story, and developers sounded off as well. Luckily, it seems that Apple has been listening: over the past few days, we have received word from a number of developers stating that they are now able to request promo codes for their 17+ apps. While Apple has not made any official comment on the issue, it appears that they have quietly conceded this battle to the developers, once again enabling them to distribute promo codes as needed for all of their apps.Considering the many other issues developers have faced with the App Store, it's obvious that the process is far from perfect. And given the sheer volume of apps and developers that Apple has to deal with, even the smallest of hiccups can become quite frustrating for those developers out there who invest significant amounts of time and money into their apps and then hit a roadblock at full speed. There are still a number of issues with -- as well as improvements to -- the development process that need to be addressed, however, I believe it is an good sign to see that Apple is indeed listening and willing to make some changes to the process. It may only be one small step in the long road ahead, but I think many of the affected developers will agree that it was a step in the right direction.Thanks to the developers who sent this in!
The Pre in iPod's clothing
Palm has quite a checkered history when it comes to syncing your Pre with iTunes, going as far as to make the device report itself as an iPod, and leaving lingering speculation that Apple would block the device with future iTunes updates -- which is exactly what has happened. But many Pre owners were surprised (and relieved) to hear that Palm had already fixed the issue, only a week after the problem surfaced.So, how did Palm manage to get sync working again? Well, the good folks over at PreCentral have discovered that they pulled it off by making the Pre report that its USB chipset is developed by Apple. This change effectively makes the device appear even more like an iPod, as well as further ensnares Palm into what could potentially be a nasty web of legal issues. While it may not seem like such a bad thing to let iTunes recognize the Pre as an iPod, the problem lies in how Palm is going about doing it. All USB devices report a plethora of information back to the operating system when they are plugged in, including a device ID, a vendor ID that usually identifies the chipset manufacturer, a manufacturer string to identify the name of the company that built the device, as well as other information that identifies various capabilities that the device might have. USB device information as shown in System Profiler Typically, a combination of the vendor ID and device ID can be easily used to identify a specific device, which is how most applications and drivers communicate with USB devices. When you plug in your iPhone, for example, the system sees a device with a vendor ID of 0x05ac (which identifies it as an Apple device), and a product ID like 0x1294. The system then checks to see if any drivers have registered to be notified when this device combination is plugged in, and it continues from there. In the case of the Pre, however, Palm is identifying the vendor ID as 0x05ac, tricking the operating system into thinking it sees an Apple USB device.As you can see, this process relies on the IDs provided to be correct in order for things to work properly. Because of this, the USB Implementers Forum (commonly called USB-IF) oversees the assignment and handling of these IDs to ensure that things go smoothly. Companies who wish to manufacture USB chipsets have to apply for a vendor ID number, as well as pay annual membership or licensing fees to the USB-IF to be an authorized vendor. So not only is Palm causing technical problems by misrepresenting the device to the computer, but it is doing so by using an ID that Apple has paid for and has the sole legal right to use. Palm, on the other hand, is likely in violation of their own agreement with the USB-IF, which clearly states that "Unauthorized use of assigned or unassigned USB Vendor ID Numbers and associated Product ID Numbers are strictly prohibited." And yes, they do have their own ID for use on their other hardware.So what does Palm have to say about all of this? They have turned the tables back on Apple, saying that they believe Apple is improperly using the vendor ID to limit the devices that consumers are able to use with iTunes. Wait, what? Isn't that *exactly* what the ID is there for? Most programs that communicate with any USB device check the vendor and device IDs to ensure that they are talking to the right device. If you've ever used the tools that came with your scanner, you've seen this before. HP's Scan Pro checks the USB devices to see if any of them are supported scanners. This is the sole reason these IDs exist, so that the software can identify a connected piece of hardware, and determine whether or not it is compatible. You wouldn't expect HP's Scan Pro to be able to download pictures from your Fujitsu ScanSnap, so why expect iTunes to show the Pre some love?Don't take this the wrong way, I do think that iTunes and the Pre should get along, but Palm needs to go about it the proper way. Disguising the Pre as an iPod is just like a wolf dressing in sheep's clothing, but things won't go well for the wolf when the shepherd catches up with it.
App Store Lessons: No promo codes for apps rated 17+
Developers whose apps meet the criteria for a 17+ rating in the App Store are now running into yet another roadblock, but this time it's not about getting their apps approved, it's about distributing them. Or, more specifically, distributing promo codes for them.Typically, when a developer uploads a new version of an application to the App Store, they have the ability to create up to 50 promo codes, which they can then provide to media outlets for reviewing the application, give away to users in a contest, etc. Aside from some reasonable restrictions on their usage (you can't sell them, they expire after 28 days and are one-time use only), promo codes provide quite a bit of flexibility to developers of paid apps who wish to freely distribute their app to select individuals without having to worry about the hassles of exchanging device information and doing special ad-hoc builds. So where is the problem? It's in the new app rating system that was released a few weeks ago. As it stands, neither the 3.0 software nor iTunes display parental warnings when using a promo code to purchase apps with a mature (17+) rating, so Apple has made the promo code functionality unavailable for apps that fall into that category. We were informed of this condition by a developer who prefers to remain anonymous.This obviously puts developers of these apps in a bit of a bind, as well as eliminates the potential amount of sales that could come from being able to distribute promo copies. Developers in this position may be stuck doing ad-hoc builds or going back to the questionable practice of sending iTunes gift cards to reviewers.And if you're thinking this just applies to the massive number of adult-oriented apps that have recently poured into the App Store, you're wrong. Apple specifies that any application that may contain high levels of offensive language, violence, sexual content, or references to drugs or alcohol receive a rating of 17+. But, according to Apple, apps that feature an embedded web browser or provide access to 3rd party content also automatically require the 17+ rating, regardless of the application's content or intended audience.Here's hoping that Apple is already working on a solution to this, as the lost potential sales caused by this not only affect the developers of the individual apps, but the overall success of the App Store as well.Update: Several developers have reported that they are now able to request promo codes for their 17+ rated apps. We have an updated post with details here.
iTunes Store & App Store problems
With the App Store celebrating its first birthday, there is a fair amount of news coverage, and with Michael Jackson's memorial service being broadcast, his fans are sure to be hitting iTunes up for some of their favorite songs. So it stands to reason that today is probably not a good day for the iTunes store to be having problems. Don't you just love Murphy's Law? Reports have been steadily coming in for the past few hours that users are unable to download songs, searches are timing out, and the App Store is not working properly from the iPhone. Several users have also posted threads on the iTunes discussion board with connection problems. I myself had troubles with searching for music from iTunes earlier today, but things seemed to be working better a short while later, so I figured things were fixed. Since then, however, we have received several other reports of troubles, yet things are working fine for me still. So it seems that this could be chalked up to routing troubles depending on your location, or it may just be intermittent and I've been lucky.Either way, it's safe to say that there is definitely something going on, although exactly what it is remains a question. Searching seems to be working, albeit a bit slowly, and downloads are working fine for me, but others have reported not being able to download at all. As they say, YMMV (your mileage may vary).Are you having troubles with either of the stores? Let us know in the comments.Thanks to everyone who sent this in!
App Store Rejections: Apple rejects iKaraoke app, patent filed published for a karaoke player
As if the waters surrounding the App Store approval process weren't murky enough, one developer has just hit an unprecedented wall. Apple rejected his app, iKaraoke, citing that it duplicated functionality of the iPod application. Of course, the "duplicate functionality" reason is nothing new, but Apple's next step is: just a few weeks after rejecting the application, they have filed a patent for including karaoke functionality into the iPod app.A brief look at the demo iKaraoke's website will quickly tell you that, while the app does bear a light resemblance to some of the menus found in the iPod application, the actual interface that the user interacts with to select and download a song is far from duplicating the iPod's polished interface. Another key point is that the file format used by iKaraoke is known as the .kar format -- an unofficial extension of the MIDI specification that enables lyrics to appear in time with music. The lyrics are then displayed on the screen, and highlighted as the song is played. Does any of this sound like functionality found in the iPod app? We didn't think so.So what exactly was duplicated then? According to apple, iKaraoke "duplicates the functionality of the built-in iPhone application, iPod, without providing sufficient differentiation or added functionality." But they didn't just stop there. The reviewer went on to say that the application "downloads media files that are not managed by the iTunes application, which also manages media files, we believe this would be confusing to the user." Now, hold on a minute here... it's fine for several other apps to stream and download media files that are supported by the iPod without being managed by iTunes, but it's not OK for an app to download media that isn't natively supported, and provide functionality that isn't natively provided by the iPod? This wouldn't be much different from your typical app rejection if the story stopped there, but it doesn't. This morning, Apple filed a patent [application here] which details built-in Karaoke functionality being added as part of the iPod application, with some additional bells and whistles such as monitoring the pitch of the user's voice. So it seems the functionality that was duplicated is functionality that Apple has not yet released, and possibly not yet even begun to develop. Maybe the $99 iPhone Developer Program fee should include a crystal ball for testing apps before submitting them.As with the many other patents Apple has filed, this feature may never see the light of day. But is it really acceptable to reject an application, based solely on what appears to be a duplication of a feature that may or may not even be released in the future? Let us know your thoughts in the comments.Update: As a few of you have pointed out in the comments, although the patent application was published today, it actually was originally filed back in April of 2008. While this does indicate that the patent was indeed filed long before the SDK was even released, questions still remain about whether or not Apple may choose to reject applications based on functionality found in unreleased features. Similar rejections have occurred with apps that offered podcast downloads prior to the inclusion of podcasting functionality in iTunes, for example. Essentially, what needs to happen is that Apple needs to clear the air on what exactly is considered a duplication of functionality, and to be clear with the developer on exactly what aspects of their application are in violation of this requirement, rather than sending a vague form letter and ignoring inquiries for additional information from the developer.
Psystar emerges from Chapter 11, and still making applesauce
The infamous Mac-clone maker Psystar is apparently set to emerge from Chapter 11 bankruptcy, and it seems that they are planning on getting right back into their previous routine with a new hardware offering to boot.In an e-mail newsletter that went out to subscribers today, the company states that the Chapter 11 protection was "critical" to their daily operations, and that they are now ready to "emerge and again battle Goliath." More information is expected to be available "in the coming days" when they are formally discharged by the Bankruptcy court. Along with the announcement, the newsletter also introduces Psystar's newest hardware offering, the Open(7), which "brings together OS X and Intel Nehalem Xeon technology" in what they are calling their "fastest and most quiet computing configuration." In addition, they are stating that all new systems will feature a new bootloader, called the Darwin Universal Boot Loader (DUBL), and mentioned plans of an open source release in the near future.The e-mail was wrapped up with a simple anecdote: When life gives you apples, make applesauce. So this begs the question, are they referring to the fruit, or the company? Thanks to Sean Wightman for the tip!
Staying Safe: securing your wireless connection
Recently, we reported on AT&T's push to make it easier for iPhone & iPod touch users to connect to their Wi-Fi Hot Spots. One of our readers, Jamie Phelps, pointed out on his blog that AT&T's Wi-Fi service is not actually a "secure connection," as is advertised in various places on their website; we had overlooked this, and mistakenly reinforced the company's shaky claim in our post.This brings to light an important point about wireless networks and security, however. It's really easy (and sadly all too common) to hop on to an available wireless signal in your office, at the hotel, or your favorite coffee spot and not even think twice about logging in to your e-mail or checking your bank balance. What many users don't realize is even though the server you are connecting to (i.e. your bank's website) may employ several layers of security, the connection between your computer and the wireless access point is very likely to be unsecured. Anyone who is within range of your computer can trivially monitor the traffic being sent between your computer and the access point, allowing them to see what websites you may be visiting or capture details about other services that you may be connected to. This isn't because of some gaping vulnerability or software bug, it's just an inherent part of how wireless networks work.So, what can you do to protect yourself? Read on for a list of simple steps you can take to ensure that your wireless connection is safe and secure.