What you need to know
- Apple lost out to Facebook when trying to lease another building.
- Now it's turned its attentions to 11 Penn Plaza.
- Apple wants 200,000 square feet.
Apple is looking to pick up around 200,000 square feet of New York City office space, according to a New York Post report.
The company had previously tried its luck with the historic Farley Building but was beaten out by Facebook. That left Apple without the space it required, but now it may have found it.
While this move would give Apple enough square footage right now, the report also notes that there's a chance more will be needed in the future. However, a source told the New York Post that Apple seems happy to meet its needs in the short term. At least for now.
Apple will reportedly have to hand over around $60 per square foot, which is a bargain compared to some buildings where rents can be almost double that.
Get the best of iMore in in your inbox, every day!
Oliver Haslam has written about Apple and the wider technology business for more than a decade with bylines on How-To Geek, PC Mag, iDownloadBlog, and many more. He has also been published in print for Macworld, including cover stories. At iMore, Oliver is involved in daily news coverage and, not being short of opinions, has been known to 'explain' those thoughts in more detail, too.
Having grown up using PCs and spending far too much money on graphics card and flashy RAM, Oliver switched to the Mac with a G5 iMac and hasn't looked back. Since then he's seen the growth of the smartphone world, backed by iPhone, and new product categories come and go. Current expertise includes iOS, macOS, streaming services, and pretty much anything that has a battery or plugs into a wall. Oliver also covers mobile gaming for iMore, with Apple Arcade a particular focus. He's been gaming since the Atari 2600 days and still struggles to comprehend the fact he can play console quality titles on his pocket computer.
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.