Channels ▼
RSS

Open Source

Have Apple's Sandboxing Requirements Stifled App Development?


Personal moves taken by one developer who had previously targeted Apple's App Store for his OS X compatible application could point to wider incompatibilities between the tech giant and the programmer community.

Author of the Vico text editor Martin Hedenfalk says that he has moved his previously proprietary, closed-source App Store project to open source under a "BSD-like" license, as he can no longer spend as much time on development as he would like.

NOTE: Vico itself is a "modal" vi-keystroke-compatible editor: This means there are different modes in which you interact with the editor…the most fundamental modes are the insert mode and normal mode. According to Vico's help pages, "Regular keys pressed while in insert mode causes text to be inserted. In contrast, while in normal mode, regular keys are attached to editing commands such as delete, change, or copy text."

"I'm releasing the source code on GitHub and encourage the community to contribute and help build a truly kick-ass editor," wrote Hedenfalk on his blog. "Vico will be removed from the App Store. Being there in the first place has been problematic, and the sandboxing requirement makes it finally incompatible. A new build is available on the download page without any trial restrictions."

Reports at the end of last year suggested that Apple's incoming sandboxing requirements for App Store apps will require support for Apple's own sandboxing routines.

Apple itself stated in November of last year the following, "The vast majority of Mac users have been free from malware and we're working on technologies to help keep it that way. As of March 1, 2012 all apps submitted to the Mac App Store must implement sandboxing. Sandboxing your app is a great way to protect systems and users by limiting the resources apps can access and making it more difficult for malicious software to compromise users' systems."


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video