3/29/2025 at 7:18:45 PM
I use Keynote to make my presentations, and one time I wanted to build a presentation with someone else. I asked my friend who has worked at Apple for 20 years, "How do you guys build Keynote presentations together? There doesn't seem to be an easy way to do that?".He said, "We don't collaborate at Apple because of the (perceived) risk of leaks. None of our tools are built for collaboration". Apple is famously closed about information sharing, to the point where on some floors every office requires its own badge, and sometimes even the cabinets within.
So it doesn't surprise me that their video editing tools are designed for a single user at a time.
Edit: This happened about six years ago, they have since added some collaboration tools, however it's more about the attitude at Apple in general and why their own tools lag on collaboration.
Edit 2: After the replies I thought I was going crazy. I actually checked my message history and found the discussion. I knew this happened pre-COVID, but it was actually in 2013, 12 years ago. I didn't think it was that long ago.
by jedberg
3/29/2025 at 7:38:20 PM
I've been working at Apple for almost 12 years. While secrecy is indeed paramount, once a tool is internally blessed, we collaborate normally using it. Keynote collaboration is actually pretty standard nowadays.Opinions are my own and do not reflect those of my employer.
by aschobel
3/29/2025 at 8:43:27 PM
Not to mention that blanket statements about Apple are absurd. I was a developer there for a decade, and every group was different.I love reading articles that purport to tell the public how things at Apple work. They're almost always laughably full of shit.
by DidYaWipe
3/29/2025 at 9:26:07 PM
Didn't the article say some floors require keys for different offices and sometimes filing cabinets.That implies every floor is different which matches what you are saying.
Most of the stories that have come out felt like they were the image Apple wanted to give. It started with Apple going after missing iphone that was left at a bar. We've heard those working on latest design for the next iphone were sequestered away from the rest of the company. I've always thought it was marketing spin and I'm glad we have an ex-apple employee confirming this. Back in the 'Lisa' days Apple did split and silo divisions, Apple did closely guard new iPhone designs with very few leaks happening but the rest of the mythology is more marketing.
by ipaddr
3/30/2025 at 2:30:13 AM
I think you are drawing the wrong conclusions here. I have never worked at Apple, but know many people that have. Every team is different but the overarching theme is that they are very secretive internally, especially around hardware. They are so secretive that someone I know was working on a project that their own manager wasn’t allowed to know about.by blackguardx
3/30/2025 at 3:08:29 PM
Anecdotally, the two times in my career I have had a project like that, apple was the customer.by amalcon
3/30/2025 at 7:59:04 AM
Was it like a temporary assignment to another team? Did the manager at least know what team that was? Or have any idea when the employee is going to return full-time to the tasks of their primary team?by owl57
3/30/2025 at 10:37:18 AM
Apple uses functional organizational structure. Every product needs a cooperation of all functions to produce results. So engineer on os team working on drivers could be working on driver for the new hw part, but other team members including their manager are not necessarily disclosed on that hw.by aliher1911
3/30/2025 at 5:52:01 PM
[dead]by unit149
3/30/2025 at 7:48:37 AM
> Not to mention that blanket statements about Apple are absurdIt isn't absurd as what GP mentions was imported into Amazon by Dave Limp, a former Apple C-suite. It was a terrible culture shock for most of the ICs in my team being reorg'd reporting in to Limp, after Steve Kessel (of Kindle fame), the previous leader, went on a sabbatical.
by ignoramous
3/29/2025 at 9:33:49 PM
Anything Apple gets attention. But any large organization does various forms of segmentation. Many of these stories are “true”, but also bullshit.I worked for a company that did some work for the federal government. Boring stuff. Their compliance rules essentially required that we firewall the folks with operational access to their data from the rest of the company. We included the physical offices in that to avoid certain expenses and controls companywide.
by Spooky23
3/30/2025 at 4:05:55 PM
What do you risk by not giving that disclaimer?by tehnub
3/30/2025 at 5:51:31 PM
The company claiming something you said, even out of context, could be interpreted as coming from the company. If you choose to disclose you work for a company, you become a spokesperson for that company unless you disclaim those words (even then, there are other considerations to make regardless of whose opinion is being expressed, because you linked yourself to the company.).By putting that, they decrease the likelihood of reprocussion in the workplace for things said outside of the workplace.
You can still get in hot water for anything you say that ties back to you or the company regardless if you disclose who your employer is.
This is the grey-area that corporations typically carve out in a social-media policy so that employees can engage in discussions around their employer without being on behalf of their employer.
It's still a perilous position to put yourself in as an employee. Innocent and innocuous things can always be misunderstood or misinterpreted.
What happens when you use that disclaimer and are self-employed though?
by gorlilla
3/29/2025 at 7:25:51 PM
That's a weird answer, Keynote can shares presentations, and multiple people can work on the same presentation in real-time, either on the macOS/iOS or the web version. The feature has been available for years: https://support.apple.com/en-us/guide/keynote/tan4e89e275c/m...by galad87
3/29/2025 at 7:35:32 PM
> Note: Not all Keynote features are available for a shared presentation.That's the main issue. But also this happened about six years ago.
by jedberg
3/29/2025 at 7:51:36 PM
The collaboration features were introduced in 2013 on the web version, and in 2016 on the native versions. And maybe check which features are actually not available before dismissing it.by galad87
3/29/2025 at 8:09:35 PM
Maybe the person who the op was talking about doesn’t work on Keynote and … secrecy … they missed the memo?by rad_gruchalski
3/30/2025 at 10:35:02 AM
What memo? :)by LoganDark
3/29/2025 at 7:51:39 PM
Six years ago Keynote supported simultaneous editing through share with iCloudby jbverschoor
3/30/2025 at 1:33:39 AM
yeah, that's where all the top level production places want to store their pre release.by gorfian_robot
3/30/2025 at 1:27:49 PM
They say that iCloud is end to end encrypted so…by ezfe
3/29/2025 at 8:27:42 PM
> To collaborate on a shared presentation, people you share with need any of the following:>
> A Mac with macOS 14.0 or later and Keynote 14.3 or later
>
> An iPhone with iOS 17.0 or later and Keynote 14.3 or later
>
> An iPad with iPadOS 17.0 or later and Keynote 14.3 or later
Those OSes were released around June of 2023, so a little over a year?
by cptskippy
3/29/2025 at 8:53:06 PM
The documentation always refers to the current versions of the software, and the latest version of iWork always requires being on latest or near-latest OS. Collaboration also requires all clients to be on the latest version of the software.by dcrazy
3/29/2025 at 10:02:23 PM
[flagged]by mort96
3/29/2025 at 11:03:22 PM
Then the question becomes why raise this irrelevant anecdote? The OP didn't research either.by Andrex
3/30/2025 at 2:04:12 AM
The anecdote is both relevant and interesting, even if a little dated.I think it's kinda bizarre to accuse someone of not "researching" their own recollections. How would one accomplish that?
by jahsome
3/30/2025 at 3:47:14 AM
Well the issue is that stories from “friends of friends” tend to get super unreliable very fast. Unless someone is coming on the record as having been employed themselves, stories from friends are almost always a lot of BS.by jeromegv
3/30/2025 at 3:42:35 PM
Which is likely why it's clearly introduced as an anecdote and not a fact.by jahsome
3/29/2025 at 10:49:21 PM
They were BSing you or working in a different part of the company than SWE.Back in the day Keynote files would just be passed around via a shared server so you and the people you were collaborating with could make and merge changes between them, eg I’d do one part of a presentation, Rick would do another part, and we’d copy our slides out of and paste them into each others’ decks to get a complete version for rehearsing with. If we had notes for each other, we’d give each other the notes out of hand rather than just directly change each others’ slides.
There’s a lot of mythology that people just make up about how secrecy works at Apple. It’s mostly sensible.
by eschaton
3/29/2025 at 9:46:49 PM
>Apple is famously closed about information sharing, to the point where on some floors every office requires its own badge, and sometimes even the cabinets within.The severed floor.
by carlmr
3/29/2025 at 10:52:28 PM
“Severance” is exactly how Apple’s New Product Security and Public Relations organizations would like all employees to be, to an absolute T. However, the rest of the company is much more pragmatic and understands well the value of collaboration and employees having enriched lives that they share with the workplace, since that leads to greater innovation and works well as a recruiting tool as well.by eschaton
3/30/2025 at 1:47:40 PM
> We don't collaborate at Apple because of the (perceived) risk of leaks.That sentence, by itself, is more or less correct (from my 26 years at Apple). However, it suggests/implies things that are not correct.
1) In case you got the impression: Apple certainly does not design software to be non-collaborative simply because it would enable sharing/leaking when used within Apple. I would say that Apple has been focused since Day 1 on a mindset where one-computer equals one-user. The mindset was that way really until Jobs was fired, discovered UNIX, and then returned with Log In and Permissions. To this day though I think collaboration is often an afterthought.
So too do they seem to be focused on the singular creative. I suspect Google's push into Web-based (and collaborative) productivity apps (Google Docs, etc.) forced Apple's hand in that department — forced Apple to push collaborative features in their productivity suite.
2) Of course Apple collaborates internally. But to be sure it is based on need-to-know. No one on the hardware team is going to give an open preso in an Apple lunchroom on their hardware roadmap. But you can bet there are private meetings with leads from the Kernel Team on that very roadmap.
That internal secrecy, where engineers from different teams could no longer just hang out in the cafeteria and chat about what they were working on went away when Jobs came back. It probably goes without saying it was rigorously enforced when the iPhone was a twinkle in Apple's eye.
The internal secrecy was sold to employees as preserving the "surprise and delight" when a product is finally unveiled but at the same time, as Apple moved to the top of the S&P500, there were a lot of outsiders that very definitely wanted to know Apple's plans.
3) Lastly, yes, plenty of floors and wings of buildings are accessible only with those with the correct badge permissions. I could not, for example, as an engineer badge in to the Design floor.
Individual cabinets needing badge access? I have no idea about that. I am aware of employees hanging black curtains in their office windows when secret hardware would come out of their (key-locked) drawers. (On a floor that is locked down to only those disclosed, obviously the black curtains become unnecessary.)
by JKCalhoun
3/30/2025 at 6:45:00 PM
This matches my experience. In addition I was advised/strongly encouraged to "go dark" on social media and refrain from ever discussing work at lunch, even with teammates.My badge only worked where I had explicitly been given access, and desks were to be kept clear and all prototypes or hardware had to be locked in drawers and/or covered with black cloths. Almost every door was a blind door with a second door inside, so that if the outer one opened, it was not possible to see into the inner space.
by daniel_reetz
3/29/2025 at 7:49:31 PM
Keynote and Numbers are interesting apps.Both are designed to replicate the same functionality as Concurrence and Quantrix (itself a clone of Lotus Improv) both by Lighthouse Design, who made lots of apps for NeXTSTEP and were purchased by Sun.
Steve Jobs used Concurrence on a ThinkPad and also a Toshiba laptop to make presentations prior to Keynote (which I believe was created internally for him at first) even while back at Apple.
by mattl
3/29/2025 at 9:36:06 PM
> I knew this happened pre-COVID, but it was actually in 2013.Real-time collaboration was added in Keynote 7.0 released in Sept 2016.
https://www.macworld.com/article/228811/keynote-pages-and-nu...
by js2
3/30/2025 at 12:32:11 AM
>So it doesn't surprise me that their video editing tools are designed for a single user at a time.The editors of Severance are actually using Avid. For music composition they're using Albeton. Neither are Apple products. The remote desktop product they're using is Jump Desktop.
While the show is an Apple TV+ show, and they happen to use to Macs in the process, this has shockingly little to do with Apple tools or products.
by llm_nerd
3/30/2025 at 7:54:36 AM
Good point. No Final Cut. No Logic Pro. Apple & Adobe are missing out.by sinoue
3/29/2025 at 7:30:04 PM
I seem to recall an anecdote from a colleague that interviewed with one of Apple's security teams. The actual room where the interview took place was locked from the outside and you had to use a badge reader on the inside to leave. I guess they didn't want folks wandering if someone needed to make a restroom break, but I can't help but wonder about issues like, say, a fire...by jc__denton
3/29/2025 at 7:44:45 PM
Presumably it unlocks if there's a fire alarm. The security team aren't more powerful than the fire marshal.by astrange
3/29/2025 at 7:57:18 PM
One wonders how well that is tested, as well as what happens if a fire goes detected, or if someone's badge stops working, or if there are technical difficulties with the badge reader or its infrastructure...There are far too many things that can go wrong with such a setup.
by JoshTriplett
3/29/2025 at 8:28:43 PM
This is a "midbrow dismissal".Yes, the fire marshal has also thought of the first thing you just thought of to post. They aren't stupid.
by astrange
3/29/2025 at 11:01:14 PM
I have personally worked in buildings that had a "badge readers all stopped working for a while" problem. Fortunately, the badge readers only affected ingress and not egress, and only controlled exterior doors and labs; that's easily solved with a doorstop and a person checking badges. I can very easily imagine what could have happened in those buildings if a badge was required to leave a conference room.And if you want to make that scenario terrifying, imagine being there on a weekend or holiday.
by JoshTriplett
3/30/2025 at 7:24:09 AM
You're doing it again!> I can very easily imagine what could have happened in those buildings if a badge was required to leave a conference room.
The facilities team and fire marshal are also easily capable of imagining this, already have, and you can ask them about it.
In this case the doors would fail open, or are made of glass and can be broken down. It's not a /really/ secure location. It's just a tech company that likes to seem secure during work hours. After hours of course the janitors get to see everything.
by astrange
3/30/2025 at 8:30:11 AM
You are utterly missing the point, to the point that you are analyzing this conversation through entirely the incorrect lens, in an effort to belittle.In an effort to steelman your comment, you may have incorrectly interpreted the earlier "I wonder how well that is tested" as "this is unsafe and illegal" rather than "among the many things wrong with this, this has increased the number of things that can go wrong, and is less safe on an absolute scale, whether or not it's strictly legal and up to code", and then assumed everything else in subsequent comments was about fire safety, rather than being a series of points in support of locking people into a building is a bad idea.
You are asserting the competence of the fire marshal, as an argument in a conversation about locking employees and interviewees and visitors inside a company's office rooms.
What you may think was happening here: "heh, nerds think they're smarter than the fire marshal and nobody involved thought of this until they came along; of course there'd be a way for sufficiently capable humans to get out of a room if something went wrong, and of course this will have been made to pass fire code, which is the only thing being talked about here".
What was actually happening here: While with sufficient analysis (which has most likely been done) it is possible to provide a sufficient degree of fire safety to make it not against fire code to lock people into a building, that doesn't make it right or zero-cost or risk-free, nor does it alleviate the stress and potential problematic-but-non-fatal situations that could arise. At no point was the primary purpose of the comment "people might burn in a fire", even though the risk of that is not zero at any time and has likely been raised (within presumably-acceptable-to-fire-code levels) by such a setup.
When I said "I can very easily imagine what could have happened", I was not imagining a fire burning down the people with the building inside. I was imagining how few failures it would require to end up with people being trapped in a room for long enough to reach the level of stress required to physically break out of a room, compounded by having worked in labs where the air conditioning was sometimes woefully insufficient.
It takes a lot of stress to get normal people to the point that they're willing to break windows or doors or walls in order to escape a room, and nobody should be subjected to such things, because there's zero security justification for a company locking people inside at any time.
by JoshTriplett
3/30/2025 at 5:47:57 PM
[flagged]by _dain_
3/29/2025 at 11:51:53 PM
Grenfell Tower was "fireproof", and yet...by floriannn
3/30/2025 at 11:20:08 AM
Grenfell Tower was fireproof as originally designed. The problem was renovations that compromised the original design, by adding highly flammable cladding panels to the exterior that allowed the fire to spread easily around the entire building.by Reason077
3/30/2025 at 7:37:34 AM
Old, poorly-maintained social housing vs the brand new flagship HQ of the largest company in the world. Right.by ascorbic
3/30/2025 at 7:23:47 PM
More importantly, the HQ is built in California, which despite appearances isn't a capitalist dystopia but a local government dystopia.Any random local government staffer is the most powerful person in the universe and obeying them is a religious edict. Apple has zero power to disobey anything in the fire code and they're probably not even capable of imagining doing so. That's why the random suburb they're in has the best public schools in the country and all the houses are like $5 million.
As an example there's currently a big empty lot next to said HQ where the mall used to be, because a random woman on the city council has blocked apartment construction for the last decade, because she thinks Apple employees will move in and molest local high school students.
by astrange
3/30/2025 at 6:39:48 AM
The obvious solution if you want to badge on exits but maintain fire safety is emergency exits trigger the fire alarm when opened.by smadge
3/29/2025 at 8:41:10 PM
arent most of these doors magnetic, ie the power goes down, all doors openby heavenlyblue
3/29/2025 at 10:59:16 PM
Power failure is a best case. I've observed firsthand cases of "badge access system went down, none of the doors open". That's less of a problem for external doors that allow people out but not in, because it can be solved by propping the door and posting a guard who checks badges. It's a massive problem when conference rooms and offices lock people in.by JoshTriplett
3/30/2025 at 1:35:52 AM
there is also the earthquake issue where interior doors (badge access or no) can become jammed. thus god invented the crowbar. my Big Company emergency response team folks all had one. also good for head crabs.by gorfian_robot
3/30/2025 at 7:56:54 AM
And what about the goats??!by DonHopkins
3/30/2025 at 8:47:02 AM
Apple was bribing the police with ipads. Surely they could bribe the fire marshall too.by throwaway48476
3/29/2025 at 7:54:06 PM
Presumably. We wouldn't know until it's too late.by abenga
3/29/2025 at 8:39:07 PM
A few times in my life I really had to get through a locked door and asked myself "What would Kojak do?" and always got through with at most three kicks.by PaulHoule
3/30/2025 at 7:58:01 AM
It took Milchick a lot more kicks than that to get out of the bathroom!by DonHopkins
3/29/2025 at 9:29:58 PM
I just go up and over through the drop ceiling.by throwaway173738
3/29/2025 at 8:17:35 PM
It probably still opens, just sets of an alarm if you don't badge out.by jedberg
3/30/2025 at 1:20:14 AM
>but it was actually in 2013, 12 years ago. I didn't think it was that long ago.I know some people will say this is because of age. But I want to suggest I often thought of COVID years 2019 to 2023s as a single year / event. For reasons I cant quite fathom. So when I think of 2015 it would only be like a 2023-2019, 2018, 2017, 2016. So around 4-5 years ago.
by ksec
3/30/2025 at 12:35:53 PM
You are not alone.by blacklion
3/29/2025 at 7:59:25 PM
Obviously a huge bias here (I work for Figma), but it’s one of my favorite things about Figma Slides. The product still has a ways to go, but man being able to actually be collaborative and not feel like you’re fighting against the software is a game changer.Video is a harder game due to the processing and data requirements, but I know that there are a lot of startups trying to make it collaborative first. I’m really excited for that to be the default.
by jjcm
3/29/2025 at 8:57:52 PM
A lot video work can be done on proxies that any M-equipped device should be able to process a dozen or so without breaking a sweat.by SSLy
3/30/2025 at 5:12:27 AM
A quick note on this for non-editing folks: in context, a "proxy" here is a low-res version of your actual footage. It's common to use them while editing a cut together, and then to replace them with the full-res versions at the very end.by nrclark
3/29/2025 at 7:28:55 PM
Wut ?Keynote works just fine with multiple simultaneous users. I work at Apple (for now) and do it all the time with managers/EPMs etc.
by spacedcowboy
3/29/2025 at 7:35:54 PM
This was about six years ago.by jedberg
3/29/2025 at 9:40:46 PM
I worked at Apple over a decade ago and no idea what OP is talking about.There is plenty of collaboration in the company but it's typically constrained to the current project you're working on. And working in enterprise companies today it is no different.
by threeseed
3/29/2025 at 7:52:32 PM
Was working like that six years agoby jbverschoor
3/30/2025 at 4:12:34 PM
Apple is famously a company that encourages cross functional collaboration, as anyone who’s ever interviewed there could attest to, or known more than your friend. They’re secretive yes, but also collaborative.You can even read any accounts of famous shipped products to back up that cross functional collaboration has been their culture for many decades. Jobs mentioned it many times, and many articles have been written about it.
Additionally keynote (and the entire iWorks suite) has had collaborative editing for years now.
I suspect your friend is likely misinformed or not reliable?
by dagmx
3/29/2025 at 7:58:45 PM
I wouldn't be surprised if their attitude toward remote collaboration probably changed pretty significantly around 5 years ago. But fair enough that it may not yet be a primary consideration in all of their software.by nerevarthelame
3/30/2025 at 12:44:17 PM
“A guy that I talked to 12 years ago that worked at Apple.”I’m reminded of my friend in grade school that had “an uncle that worked at Nintendo”.
Not saying he didn’t, but just because someone works there doesn’t mean they know what’s going on.
by 486sx33
3/31/2025 at 4:50:51 PM
Except "uncle that works at Nintendo" is a meme because Nintendo of America is a small business doesn't develop almost anything, whereas "friend that works at Apple" is less unreasonable for an American tech worker forum to purport.by bigyabai
3/29/2025 at 8:13:48 PM
Apple is not like that anymore. Well, not where it concerns remote tools and cloud use.by rcarmo
3/29/2025 at 8:14:10 PM
Isn't it also true that Apple have dozens of different scm / developer platforms scattered around the company? e.g. some teams use gitlab, others phabricator etc etcby mhh__
3/29/2025 at 8:18:52 PM
I think so as I just saw this on their jobs website:> We are seeking an experienced Software Architect specialized in source control systems to join our dynamic team. The ideal candidate will have expertise in designing, implementing, and managing systems like GitHub, GitLab, Perforce, Bitbucket, and Artifactory.
by mattl
3/29/2025 at 9:55:22 PM
Almost certainly yes because Apple acquires a lot of companies.Many of which take time to be migrated into the mothership.
by threeseed
3/29/2025 at 7:26:27 PM
Huh. At my last company, probably less so presentation collaboration (in my case, less though still some if I were co-presenting) but shared documents with editors and so forth were huge. Better built-in workflows would have been nice ut it worked well enough with a bit of discipline, e.g. once you do a handoff you (mostly) don't make further changes unless you noting a typo or something.by ghaff
3/30/2025 at 5:14:19 PM
The article isn't about Apple lagging on collaboration. The article is about Apple lagging on virtual desktop infrastructure.by Thorrez