Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple uses a lot of third-party SW to drive its hardware (I worked for a company supplying them and other phone integrators). They usually operate by initially licensing it, but after a couple of years stop paying the license fees, claiming they are using their own SW. That's either a blatant lie, or their own SW is just a crude copy. In this case, they apparently did not even bother licensing.

This is the DNA of Apple. They are so big and wealthy, they use their size to bully small companies. The other large tech companies do the same in their determination to get their own way.
It’s even worse when FOSS is targeted. Your post made me think about FFmpeg calling Google out recently. Many big companies rely on FOSS but don’t donate or help maintain with their much larger, advanced dev team. Now, FFmpeg has devs who say Google has been super helpful in funding and maintaining, but a Gemini powered bug finder with a default disclosure clock is a bad look.
 
In our case, they just decided to stop paying license fees, claiming that they now used their own SW in the then-current iPhone. But reverse engineering showed conclusively that they were actually using our original SW. The details of the financial settlement were mandated by Apple to be confidential (of course!).

Well, this isn’t a court. Spill it! Were you paid out properly?
 
Cute... but I'm pretty sure NDAs don't work that way.

Oh quit being paranoid. By simply saying “we were paid handsomely” or “we ended up not made whole” there’s nothing identifying revealed, including the type of software or even the partner’s hemisphere.
 
Oh quit being paranoid. By simply saying “we were paid handsomely” or “we ended up not made whole” there’s nothing identifying revealed, including the type of software or even the partner’s hemisphere.
Chris chose to answer you appropriately enough -- but he was under no obligation at all to respond, and in his place, I likely would not have responded at all. It's not paranoia to read the warnings that they give you in the NDA, and realize that they could successfully sue your a** into oblivion if you cross the line. Choosing not to make any comment that might be construed as crossing the line is simply prudence.
 
  • Like
Reactions: jcxdev
What's funny is I hadn't been able to get Continuity Camera to work on my Mac since it was introduced as a feature, and about a year ago I stumbled on Camo while working on another project… it works great! And even today, Continuity Camera STILL only works about a quarter of the time. Because there is no user interface with it, getting it to work is akin to having to "stand on your head, spin around three times, and kill a chicken". Whereas with Camo, I launch it, it shows a list of devices, and I chose the camera-device I want—AND it works with my iPad mini and older iPhone! Seems like Apple didn't steal enough… which tells me that Reincubate is likely to prevail at some level here.
I cannot get continuity camera to work either but camo which I already owned works well. It just doesn’t have desk view.
 
While their version of events might be true, it’s also possible that it is not true and this lawsuit is completely without merit. Why are the people in the company that instigated that lawsuit automatically more trustworthy than Apple? Do you know them personally and know the history of what really happened?

I think the wisest approach is to withhold judgment until the case is done.
Most sane stance until what I have read through this thread.

The other thing is, why is there even a patent for this? This is getting borderline “if you make a camera and use it as a camera you have to pay someone somewhere that said they invented first the usage of a camera as a camera”.

Give me a break, usb webcams, embedded webcams, FaceTime from the phone, etc is all the same… this functionality, which is very neat, is just connecting a camera (wirelessly in this case) to your computer. A cameta that happens to come with your phone. The end.

Imagine if there were lawsuits for every single thing the phone does besides making phone calls: mp3 player lawsuits, video player lawsuits, internet browsing lawsuits, etc-times-infinite.

This shouldn’t be a patent, I got a camera, I got a computer, Apple lets connect one to the other, that’s it.
 
While their version of events might be true, it’s also possible that it is not true and this lawsuit is completely without merit. Why are the people in the company that instigated that lawsuit automatically more trustworthy than Apple? Do you know them personally and know the history of what really happened?

I think the wisest approach is to withhold judgment until the case is done.

Why yes, I do know them personally—in fact, I was one of about 15–20 people who worked there at the time! (Proof.)

Apple’s Continuity Camera was widely praised by users when it launched—after all, it lets any modern iPhone double as a high-quality webcam with minimal setup. However, this case highlights the perennial tension between Big Tech platforms and independent developers. It’s not unusual for Apple to integrate ideas pioneered by third-party apps or the jailbreak community (the practice even has a nickname, “getting Sherlocked”). Over the years Apple has rolled popular app features into iOS—from night-mode blue light filters to swipe keyboards (e.g., FlickType)—often to the dismay of the original creators. What’s different here is that Reincubate secured patents on its implementation, and is willing to take on Apple in court. That adds legal weight to what would otherwise be a one-sided fight over “who copied whom.”

From a technical standpoint, it’s easy to see why Apple pursued its own version of Camo. Seamless iPhone–Mac webcam integration is a compelling feature for the ecosystem, especially after the remote-work boom. But the allegations, if true, paint Apple’s behaviour as underhanded—essentially stringing along an indie developer, gleaning their solution, then leveraging platform control to edge them out. It’s the sort of move that antitrust regulators are increasingly interested in, blurring the line between healthy platform improvement and stifling a potential competitor. On the other hand, Apple claims that there’s nothing nefarious here, and it’s certainly possible that its engineers tackled the problem independently (Apple undoubtedly was aware of the general demand for better webcams). The outcome of this lawsuit may hinge on the specific patent claims—e.g., whether Continuity Camera’s inner workings truly mirror Reincubate’s patented methods for splitting and coordinating video tasks between devices. If they do, Apple could face an injunction or monetary damages; if not, Reincubate’s case might fizzle on technical grounds.

In my opinion, Apple's communications with Reincubate regarding this issue demonstrate a clear disregard for smaller app developers. Despite actively supporting Camo's development by encouraging internal testing of the application, Apple's subsequent release of Continuity Camera appears as though they abused their position to leverage Camo as an effective pilot. Reincubate invested their own capital in proving the feature and Apple benefitted at a reduced cost—and a significant cost to Camo. Apple was contacted by Reincubate about the issue soon after Continuity Camera was released, but consistently went back on their word, doing little to address the situation. Perhaps they thought that awarding Camo "finalist" status at the 2023 Apple Design Awards would sedate the issue—however, it is clear that they underestimated Reincubate's integrity. While working at Reincubate (a small team of roughly 15–20 people), I recall it being a touchy subject, and was even advised not to speak on the matter when attending an Apple Developer Session with a prototype of the Apple Vision Pro in late 2023. Ironically, Apple damaged my iPhone during this session while applying tape to its cameras, promised to contact me and resolve it afterwards—but then never did.

Either way, it’s a notable test of how far a smaller developer can go in challenging a platform owner’s appropriation of an app idea. Many developers worry about being Sherlocked, but few have the resources (or legal basis) to fight it. Reincubate’s CEO, Aidan Fitzpatrick, has framed the dispute as about more than just Camo—it’s about whether developers can safely build innovative device-integrations “that level the experience between platforms” without having the rug pulled out from under them. A court win for Reincubate could set an interesting precedent, perhaps pressuring Apple to approach third-party innovations more cautiously (or at least license the tech). However, taking on a tech giant is always an uphill battle. As a tech enthusiast, former jailbreak tweak developer, and former employee of Reincubate, I’m keen to see how this unfolds and am heartened that someone has finally taken a stand against Apple—it could influence Apple’s future relationship with developers and the balance of openness vs. lock-in in its ecosystem, which is something I care very deeply about.
 
Last edited:
... Either way, it’s a notable test of how far a smaller developer can go in challenging a platform owner’s appropriation of an app idea. Many developers worry about being Sherlocked, but few have the resources (or legal basis) to fight it. ...

But it seems that even fewer are truly cognizant of the history behind the term itself. (If you haven't already noticed, this is a bit of a pet peeve of mine.) For those who haven't read the linked previous post, and perhaps don't have the time to do so, the TLDR looks something like this:

The term is a misnomer: The original "Sherlocking" incident was actually a small company (Karelia) appropriating Apple's idea... and basically reskinning it a bit. Then Karelia cried foul when Apple responded in kind, but they had no legal ground on which to stand and they knew it.

When you use that term to compare your situation to Karelia's situation, you're actually doing your case a disservice. If your company's case has any merit at all, it would be far wiser to not compare it to a previous failed case.

The big guy isn't always the bad guy... and lawsuits don't always go the way of the supposed "underdog."
 
  • Like
Reactions: I7guy and jcxdev
When you use that term to compare your situation to Karelia's situation, you're actually doing your case a disservice.

Perhaps you have a point here (and thank you for informing me!), but language often adopts a social meaning which differs to its origins. Most people understand the intent behind usage of the term, and are otherwise oblivious—it’s an unfortunate reality that the rest of us might find irritating, but must accept in some capacity. I have a similar thing with various other terms 😅.

Also, I ought to clarify that I am a former employee—I moved on from my role in 2024. Reincubate, however, remains the most welcoming, kind, understanding, and values-led group of people with whom I’ve ever had the privilege to work. I will defend and support them throughout this lawsuit, and truthfully, they don’t get nearly enough recognition for the brilliant and innovative work they do—even if on a small scale.
 
However, taking on a tech giant is always an uphill battle. As a tech enthusiast, former jailbreak tweak developer, and former employee of Reincubate, I’m keen to see how this unfolds and am heartened that someone has finally taken a stand against Apple—it could influence Apple’s future relationship with developers and the balance of openness vs. lock-in in its ecosystem, which is something I care very deeply about.


It will be interesting, for sure. The big question is does Reincubate have the money to fight to the end and at what cost to the better use of their time. I suspect Apple will try to get their patents invalidated as well as use their patents for counterclaims, but IANAL, so who nows.

The other question is what was Apple shown and under what terms? Some companies want to see everything and not be held to not using it or developiing simlar products; and becasue they are big it's tempting.

Developers are always at risk of a big company coming out with a product that mimics what thy do, especially if the functionality becomes popular. If they have some unique tech, being bought is a possiblity but many no doubt simply get copied.
 
  • Like
Reactions: jcxdev
Developers are always at risk of a big company coming out with a product that mimics what thy do, especially if the functionality becomes popular. If they have some unique tech, being bought is a possiblity but many no doubt simply get copied.
And, companies with good ideas and a vision for the future can take what’s a “feature” and turn it into something that can keep them going. That’s what Dropbox did, and they’re one of the 10 big cloud storage companies still. Companies that feel they have something to offer prove it. Those that don’t try to get a legal payout on their way out.
 
  • Like
Reactions: jlc1978
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.