2.1 Breaks OpenClip

Posted on August 22, 2008 at 11:24 AM PDT

Yes, it's true. I mentioned before that this was definitely a possibility, but I don't believe it is an inevitability. But anyway, lets define breaking:

Apps that use OpenClip will no longer be able to copy and paste between applications. However, applications can still utilize a persistent way to store data inside the application, meaning that copy and paste within the app will still work fine. And on top of that, apps that utilize only one form (either copy or paste) can disable interface elements when Apple axes OpenClip.

However, even though apple is killing the concept behind the current OpenClip, that doesn't mean we can't change the concept. A shared clipboard could be stored in an Address Book card or even on a remote server. Those solutions aren't as good as the OpenClip implementation, but they aren't bad.

The address book version, would have to write a very weird looking address book card to your address book. It would probably get synced and it would show up on your Mac or PC or even MobileMe. I'm not too cracked up about that, but I would be interested to know what users think of that (email me). The network solution is impossible for Apple to shut down, but it is no easy task. Just ask Apple's MobileMe department.

I unfortunately found out about 2.1b4 closing off the sandbox about an hour after I was interviewed by Cali. It really didn't change my plans much and here's why:

- The goal is to bring the usefulness of copy/paste to light. Everyone thinks it would be useful on this device, but sometimes being able to actually use it can really make it obvious.
- Let developers experiment with copy/paste both in their UI and in the code. I modeled the API after NSPasteboard, Apple's OS X implementation of copy/paste. If apple would just implement NSPasteboard and nothing else (radar bug: 6158362), apps could get all the functionality that I'm proposing.
- Get some interesting functionality in apps *now* (well in the next few days...).

By debuting this framework, I hope to convince Apple that NSPasteboard or a similar API is needed on the iPhone. Lets not forget that 2.1 is not out yet and there is still time for Apple to either add public opt-in access to sandboxes (radar bug: 6156881) or NSPasteboard (radar bug: 6158362).

-Zac

P.S. I have a little problem when people point the the "access" quote. I certainly don't have "access" to your car, but I can definitely see in through your windows. And I've been informed that it used to read "read and write" and was later changed to "access", so that is very confusing. Read and write is probably what Apple meant, but why not put that in the legally binding document or be explicit about it in the users guide...

P.P.S Also, some seem to think that Apple is squashing OpenClip specifically. I don't really believe this to be the case. Even though I debuted to concept before the newest beta was release, I'm sure Apple had been planning to kill this kind of thing for a while.

OpenClip Concerns

Posted on August 20, 2008 at 5:21 PM PDT

Let me first explain how OpenClip works:

How it works is relatively simple and doesn't break the SDK agreement. OpenClip works by looking into the Documents folder of other applications to get their pastes. Applications are allowed to write all they want to their own Documents directory (for copy), so no foul there. Applications are also allowed to read outside their sandbox into the Documents directories for other apps (for paste), so no foul there.

How could that ever go wrong? What's the problem?

The problem is Apple is probably going to shut down reading into other application's boxes. I'm all for that as long as one of two things happens before:

- Apple ports NSPasteboard to the iPhone SDK (radar://6158362)

NSPasteboard is what I modeled OpenClip after. It allows copy and paste between applications, but more than that, it adds communication between applications. Porting NSPasteboard would make OpenClip moot and developers could easily respond by changing all references to OCPasteboard to NSPasteboard. Easy for everyone involved.

- Apple shuts down sandbox reading but creates a public folder for apps to write to. (radar://6156881)

If Apple does this, inter-app communication would still be possible through OpenClip or some other file communication method.

Applications need to work together. That's the Apple Way®. I don't know what you think, but to me the smaller and simpler an app is on the iPhone, the better it is. To make apps that are simple but powerful, developers need to make applications that can communicate.

What happens if Apple shuts it down?

Here's what happens if a new version of the iPhone OS comes out and OpenClip can't communicate anymore:

- Developers who implement OpenClip to either *only* copy or *only* paste can easily check if that will work before displaying any UI. If it breaks, those options just disappear.

- Developers who implement to do both copy and paste retain copy and paste within their application. That means that when and if the next update breaks OpenClip, applications won't stop launching, they won't crash when you try and copy and they won't get garbage data. All that will happen is the app will only be able to copy and paste in the application. Not a horrible way to degrade if you ask me.

What about the UI? There are going to be like 20 implementations for copy/paste!

UI is a hard problem to solve. One of OpenClips goals is to provide examples of UIs for copy and paste. But to be honest, the best thing you can do with OpenClip is use it only for simple data. Only copy interesting data that a user would want to copy and present UI similar to Apple's push to save image UI. Doing what MagicPad does and providing a whole way to select text is not what 90% of apps need. Look at what Twittelator did with copy in the video on GeekBrief.tv. Press and hold needs to be the way most apps utilize copy and paste.

You can check out Proximi's MagicPad UI proposal video here. It's worth a look.

Lets face it. Hardly anyone is not buying an iPhone because it doesn't copy and paste. It's useful, but not necessary. Apple knows this so they put it at the bottom of their to-do list. If Apple were to implement NSPasteboard, however, 90% of apps could gain some really great functionality. Until then, maybe OpenClip can serve as a sneak peek to Apple, developers and users that this kind of framework would benefit the iPhone greatly.

-Zac White

OpenClip on GeekBrief.TV!

Posted on August 19, 2008 at 8:30 AM PDT

An invitation to be featured on GeekBrief.tv? Needles to say, OpenClip was very excited!

The show, which was just published and graces our main page, gives a fantastic overview of OpenClip's mission, scope, and course of action. Cali Lewis, who was extremely nice, really took the time to delve into the details about app-to-app copy / paste for the iPhone.

As fans of GeekBrief.tv and Cali, and knowing she selects features based on issues, "a) exciting to me, b) extremely innovative, c) overwhelmingly newsworthy, or d) entertaining," we were honored for consideration. Though I do wonder which category we fell into, hmmm...