You may have heard the news that “Apple’s sandbox deadline has arrived” for the Mac App Store, and that it might cause headaches for some developers and their apps. There’s a lot to talk about in terms of this “sandbox” thing that Apple’s pushing, but I want to skip to the important part for you, our wonderful customers and readers: the Mac App Store version of 1Password has been ready for sandboxing since its debut in September 2011. For bonus points, the latest website and Mac App Store versions are even ready for Mountain Lion, too!
That means you have nothing to worry about as to whether Apple’s sandboxing rules will affect 1Password and its many excellent features. Our valiant developers started doing a ton of work on 1Password a long time ago—as soon as we heard sandboxing was coming to OS X. AgileBits has been humming along just fine since then, dreaming up new features, listening closely to your feedback, staying one step ahead in security, and building new foundation for the future of 1Password.
Now, if you’re interested to learn more about sandboxing and what it means for both developers and users, we’ve discussed it a little bit here on the Agile Blog. In a nutshell: Apple realized that if it added some restrictions to the files and parts of the system that applications can access, OS X can become more secure and resilient to malware or your typical rogue app. I guess you could say Apple gave these rules a test drive in iOS, since that’s how its apps have worked since the original iPhone in 2007.
Generally speaking, most users probably won’t notice any difference in day-to-day use of Mac App Store apps. But Apple’s new sandboxing restrictions for apps in its store can pose challenges for some developers whose apps have had free reign all these years. In some cases, developers might have to change or remove features, but some might have to remove their apps from the Mac App Store entirely. Again, 1Password has fortunately been prepared for these rules for nearly a year.