Panic Blog Dispatches from Panic HQ in Portland, Oregon Tue, 25 Aug 2015 18:48:04 +0000 en-US hourly 1 Status Board 2 is Here Also Tue, 04 Aug 2015 20:30:50 +0000 icon-statusboard2@2x

There’s a funny thing I’ve noticed in the Panic office: our beautiful status board is second only to our weird-snack wall as the office conversation spot. We often gather in front of our status board to discuss funny tweets, or look at our sales charts and figure out what’s next. It’s a center point. And you should have one too — for your home, your office, your business, anywhere.

We built Status Board so that everyone can make an incredible status board.

And now, Status Board has hit version 2.0, free update to our powerful iPad app that makes beautiful status board creation as easy as dragging, dropping, and configuring.

We started with multiple board support: now you can set up an infinite number of status boards, and automatically rotate between them. It’s great. There’s also a brand-new UI, built from scratch. There’s some new panel types. There’s publish and subscribe, so you can create a beautiful board for your organization and automatically update everyone’s boards remotely.

There’s also an interesting pricing change: the app is FREE. Yes, you can try Status Board without paying a cent, including six panel types. If you like Status Board, and you want to do more, six more panel types are only $9.99 in our “expansion pack”.

If you bought Status Board 1, don’t worry: we’ll automatically unlock all twelve panels for you. It’s our thanks for your continued support.

You can read all about Status Board 2 here — or,  just go ahead and get it on the App Store.

Like Coda for iOS, it took us a little while to get this out the door, but we think it’s worth it. It’s packed with new stuff.

When you set up your cool status board, please tweet us a photo!

]]> 9
Coda 2 for iOS is Here Thu, 16 Jul 2015 19:34:48 +0000 icon-coda-ios_2x

Diet Coda just got an update so big, we didn’t feel comfortable calling it “Diet” anymore. (Ho-ho.)

Introducing Coda for iOS (formerly Diet Coda) version 2.0, a massive, free update to our incredible, desktop-class text editor. It gives you an incredible amount of power tucked into your iPad or, now… also your iPhone.

iPhone support is not the only new thing. There’s a brand-new UI redone from scratch. Full Panic Sync support. More syntax modes. Better file management including our dual-pane file browser. The latest SSH engine from Prompt. Javascript Playgrounds. More nice touches around every corner.

And, once again, this is a free update for Diet Coda owners. (You may already have it.)

For everyone else, we just reduced the price: $9.99. To be honest, that feels nuts for the amount of work put into the app. But a bargain is a bargain! (You should grab it now before we change our minds.)

Read all about Coda for iOS here. (Or, if you want, just grab it on the App Store!)

Thank you for your patience while we worked on this enormous overhaul. We truly hope you enjoy it. Tell us what you make with it! And if you find any bugs or have ideas, send us an e-mail!

]]> 12
Firewatch. Mac, PC, and now, PlayStation 4. Tue, 16 Jun 2015 01:40:24 +0000 firewatch-ps4

Have you heard of our upcoming game, Firewatch? (It’s a first-person mystery/drama/adventure set in the Wyoming wilderness. You’re Henry. You just got a job in a Firewatch tower. You make contact with another watcher who only exists on the other end of a handheld radio. And then… things happen.)

Being developed by a talented bunch of smarties at Campo Santo, we’re immensely excited to be publishing what’s shaping up to be something special.

We’ve already announced that Firewatch will be coming first to the Mac and PC. (And at WWDC we announced that the Mac version will support Metal for ultimate performance and fidelity! We’re really excited about this.)

But we just announced the other half of the equation…

Firewatch will also be coming to your PlayStation 4.

And there’s more:

Here’s the brand new trailer we just unveiled at Sony’s E3 Keynote:

And here are some fresh in-game screenshots of Firewatch:







We haven’t announced a release date yet — or the release date for the PlayStation 4 version — but keep an eye on our Twitter and we’ll let you know the moment we know.

We can’t wait to take you to this place!

UPDATE 6/16: Some further reading. Jake discusses how we put together the trailer for Sony’s crazy huge screen. And over on Sony’s PlayStation Blog, Chris talks about how we landed on PlayStation 4.

]]> 13
Violet Beep Wed, 11 Mar 2015 19:49:10 +0000 I have a 1-year-old daughter named Violet.

For whatever reason, we began calling her Beep. Sometimes Beepy. Usually Beep. Rarely Violet. These things happen.

Yesterday, Ashur and Heather revealed to me a tiny little easter egg they snuck into our SSH app, Prompt 2.1

With the right set of steps, you can switch the normally-white visual beep to be… violet.

Heather coded it up and Ashur made this graphic to reveal the secret:

Basically, I will know you are the deepest of Panic fan if you are rocking the purple flash. (Someday I’ll explain this to Violet. Probably her first question will be, “Wait, you called me what?”.)

There aren’t a lot of secrets in Panic apps, but I’ll never forget this one.

]]> 8
Firewatch Demo Day at GDC Mon, 09 Mar 2015 23:56:09 +0000 You knew Panic was making a game, right?

Technically, we’re not actually making the game — we provided the funds to launch both a brand new game studio, Campo Santo, and an ambitious upcoming game… Firewatch.

Panic is, I guess, the “publisher”, although to me that conjures up imagery of a guy in a suit slamming a table and yelling “If you don’t add a goddamn assault rifle in the first five minutes of this snooze-fest we’re shutting this whole thing down!”. We are not that publisher. Campo Santo has become extended Panic family, and we feel as strongly about Firewatch as we do any of our apps.

“In Firewatch, you play as a man named Henry who has retreated from his messy life to work as a fire lookout in the Wyoming wilderness. Perched high atop a mountain, it’s your job to look for smoke and keep the wilderness safe. Your supervisor, a woman named Delilah, is available to you at all times over a small, handheld radio — and is your only contact with the world you’ve left behind.”

You can watch 17 minutes of gameplay here. The game already looks incredible:




Now, while Campo builds the game, it’s Panic’s job to help sell it.

We talked a lot about how we wanted to do that. Should we get a booth at PAX? E3? What’ll get the word out best? Trade show booths are notoriously expensive — I’ll never forget getting yelled at once because I was carrying in a single box to our Macworld Booth one year, that was the Union’s job!, not to mention the $1,500 three-day internet — plus your game gets lost in a giant sea of bright lights and loud garbage.

So, we focused on GDC — the Game Developer’s Conference — a time when a lot of press and peers are in one place. Then, we thought it’d be more cost effective and possibly more powerful to do something “off-campus” — make a destination for attendees. And since not everyone can afford to attend GDC, we thought it’d be incredible to do a Public Demo Day, where anyone in town could play an early build of Firewatch for themselves, for free.

Sounds great. But how could we make this event feel amazing for our guests?

We needed to find the right space… and lights… and trees.

Because we brought Firewatch to life.

Firewatch (1 of 11)

Guests were greeted with some helpful signage. To the right, we built a full recreation of Henry’s tower and desk… down to the smallest Olly Moss-crafted detail.

Firewatch (2 of 11)

Firewatch (6 of 11)

Firewatch (5 of 11)

On the left, we set up these demo stations with the latest build of the game right in the middle of our own tiny forest.

Firewatch (11 of 13)

Firewatch (10 of 11)

Firewatch (12 of 3)

(That’s Rich Sommer, the voice of Henry in our game — you know him as Harry Crane from Mad Men. I asked if it was weird playing a game with his own voice but he said that kind of out-of-body experience doesn’t really affect him anymore.)

We even included some cool special effects, like this magic poster at the entry stairs:


(FYI, the secret to an eye-fooling projection is to project onto a textured surface — in our case, canvas — and layer a lighting effect on top that spills outside the primary surface — in this case, faux window light.)

The doors opened and we were slammed. Nearly a thousand people showed up to our (quickly-very-toasty) venue and played the game. We got a giant stack of feedback forms and learned a lot about what was, and what wasn’t, working. The experience was invaluable for us.

Firewatch (13 of 3)

Plus, the reactions to the demo have blown us away:

Rock Paper Shotgun: “It was agonising when the demo ended – I desperately wanted to play more. I wanted to know what happens next! Despite the fact that, looking back, what had happened so far was so relatively mundane. It was the strength of the characters, and the wonderful sense of place, that made me not want to have to leave.”

gameinformer:Firewatch is my favorite game from GDC. It immediately hooked me, and I never knew what I would find next. […]  I’m still thinking a lot about my time with Firewatch, and that says something.”

Spectre Collie: “If we get enough people pointing at a beautiful, engaging, and mature experience and saying, ‘This. We want to make more of this,’ then the entire medium will be better off.”

Firewatch has been teed up.

The goal is in our sights.

Now we just have to hit a home run.

I’m not good with sports analogies.

We hope to release Firewatch in late 2015 for Mac, PC, and an as-yet-undisclosed console.

(Production notes! The bulk of the planning, design, and hard work for this event was done by Greg here at Panic, who really did an incredible job. Beautiful photos courtesy Sebastiaan De With. The venue was The Box SF, which was already laden with warm wood and tower-ready windows. Lighting and sound was installed by Got Light. Props came from the incredible Prop House. Our ambient forest sound loops were crafted by Jared Emerson-Johnson. Boombox audio from the incredible Cheap Talk as discovered by Chris Remo. PCs were provided by Nvidia. Our stump tables and chairs came from Campo’s downstairs neighbor, a woodworker, and they were heavy as all hell as it turns out trees are heavy. When we unloaded the stumps to the Campo office, a random San-Fran-coolguy quickly roosted on one and we love him. Secret party weapon: ambient pine scent provided by a hidden Accuscent HD, which delighted me to no end. And everyone at Campo, of course, worked incredibly hard to guide players, talk to press, make everyone feel welcome! Thanks!)


]]> 30
EditorConfig for Coda 2.5 Tue, 17 Feb 2015 23:44:27 +0000 edcon_color_transbg2

EditorConfig is a clever idea: a simple text file you can put anywhere in your code source that automatically changes settings in your favorite text editor.

For example, let’s say someone decided one project had to use space indentation (for Python?) even though everybody usually uses tabs. With EditorConfig, you can easily declare this setting in an .editorconfig file in the root of the project…

  1. # top-most EditorConfig file
  2. root = true
  4. # 4 space indentation
  5. [*]
  6. indent_style = space
  7. indent_size = 4

…or you could put this file in any folder in your project, and the editor will automatically pick it up. Then, you can easily check this file in to your source control system. Anyone who checks out your project — and uses a EditorConfig-capable editor — will automatically inherit the recommended editor settings.

We thought this was pretty cool, and so did our users, so we went ahead and built an EditorConfig plug-in for Coda 2.5. It currently supports everything except for the text encoding setting.

If that install link didn’t work, or you don’t want to install it right now, you can browse our plug-ins here.

When you’re ready, read up on the file format here. We hope you enjoy it!

]]> 11
ShrinkIt 1.3 Tue, 10 Feb 2015 23:53:47 +0000 ShrinkIt 1.2 icon

Quite some time ago, we made a quick, free, handy tool called ShrinkIt®.

(Yes, we actually have a registered trademark on ShrinkIt®. Why not!)

ShrinkIt takes bloated Adobe-saved graphic PDFs, runs them through Apple’s PDF renderer, and saves them back out, making many of them smaller without any quality loss.

Note, though: it’s not really for long complex PDF documents or bitmap images. It’s generally for simple PDF symbols and glyphs you might use in your apps, where saving space is critical.

We’ve just updated ShrinkIt to version 1.3, and wanted to let you know!

ShrinkIt Release Notes:

  • Processing is now threaded and significantly faster.
  • It’s now properly signed with our Developer ID
  • There’s a new icon
  • And it’s now Retina-ready
  • 1.3 — Fixed exception when dealing with Unicode file paths
  • 1.3 — Added cool progress bar and gratuitous animation

Two important ShrinkIt instructions:

  1. If a finished file is not smaller after being processed, it will not be saved.
  2. Your original files are renamed with the prefix “_org_” just in case.

We hope it serves you well.

UPDATE 2/11: We bumped it to 1.3.
UPDATE 2/13: Aaaaaand 1.3.2 fixes some problems with 10.7 and 10.8.

]]> 7
Transmit User Survey Tue, 03 Feb 2015 18:28:25 +0000 What would you like from Transmit in the future? Here’s your chance to let us know.


]]> 17
The 2014 Panic Report Mon, 05 Jan 2015 19:33:48 +0000 XOXO photobooth

It ended with a bang.

For the last year or so, Panic was typically heads-down quiet. But as 2014 drew to a close, our furious typing came to fruition and a whole lot of magic happened. It felt great.

If you’ll indulge me, I’d like to write a little more about our business than we normally do. Why not?


So many wonderful things shipped in 2014:

Transmit iOS (1.0, 1.0.1, 1.0.2, 1.1, 1.1.1, and 1.1.2)
Transmit iOSYes, a brand new iOS app from Panic! This extremely capable iOS file transfer client is an idea we’d considered in the past but didn’t green-light until Sharing Extensions were formally announced at WWDC — bringing file transfer to other iOS apps made this idea sing. It helps that our engine had already been ported (thanks to Diet Coda), but one interesting note: from start to finish this was a three-month project. I think that’s a tremendous accomplishment given its meaty features and beautiful fit and finish. Feedback has been spectacular — from MacStories to MacUser, people love it.

Prompt 2 (2.0, 2.0.1, 2.0.2, and 2.0.3)
Prompt 2A very welcome update to our popular SSH client for iOS at last went out the door. With a new engineer focused on this project full-time, we updated the UI, added some much-requested new features, and brought Prompt into the modern era. Plus, it was the perfect candidate to help test and implement Panic Sync.

Coda 2.5 (2.5 and 2.5.1)
Coda 2.5A monumental — and free — update to our already-monumental OS X web coding app. It took too long to get out the door — I’ll say it’s no fault of the team, but rather a series of difficult decisions (that I’ll detail below) that meant a lot of wasted time followed by writing our own sync server. But we added huge features (local indexer! indentation guides! plugin improvements!) and cleaned up the UI and I think we ultimately delivered on the original promise of Coda 2.0 in a way I think our Coda customers have deeply appreciated.

Panic Sync
Panic SyncAfter lots of discussion, we decided the only way to provide a truly great sync experience for our customers was to control both sides of the equation — the server and the client. So, after a ton of research into what was available, we wrote our own. After successfully launching Panic Sync service, and its web interface, we’ve been adding it to all of our apps, with more to come. At last count, there were over 400,000 sites being synced with Panic Sync — and nearly zero downtime. I’m especially proud of the transparency on our Panic Sync webpage — no solution can be perfect or fully secure, so we thought it was best to put all of our cards on the table.

MiscEach of the app launches has meant we’ve also been continuously updating our webpages and UI to our latest style and palette, and that always feels good. We also created PunchClock, our cool open-source iBeacon project. We discontinued Unison to free up resources for the future, a difficult decision but one that most people seemed to understand. And 2014 was also the year that our video game project, Firewatch, funded by us and built by a great team in San Francisco, started full-scale production. We are extremely excited about this.


Not everything was super easy, of course. Here are some standout difficulties.

iOS Upgrades

We decided to make Prompt 2 a brand-new app. Amazingly, customer reaction was surprisingly neutral or positive — I was prepared for a 6-foot shitstorm and there was none. Why did we charge? The market for Prompt is small, and its revenue would not wholly cover the cost of infinite future development. The only way we could afford to do a 2.0 was to charge for it. The first problem: we have no idea who bought the app, so how do we let them know? Fortunately, we planned ahead, and added our home-grown Soapbox code to all of our apps, including Prompt 1. It allows us to push out a custom web page, one time, to customers on launch, based on a variety of criteria. So we were able to alert Prompt 1 owners that Prompt 2 exists. But still, we’re sure many people dismissed it immediately, and those people will never know they’re stuck with a version of Prompt that will never be updated. There’s also the matter of when it’s too soon to charge for a new version — as we prepare some new iOS updates, we’re still debating if we want to charge for those as well. My gut says no, that full price every single time is rough, but then we’re setting the precedent that maybe not all of our major upgrades are paid upgrades, which we’ve been pretty consistent about in the past. If we could offer traditional discounted upgrades via the App Store, this paragraph wouldn’t exist. This is one area where the App Store feels like one of those novelty peanut cans with the snake inside.

Leaving the Mac App Store

We’ve well-documented our struggles with Coda 2.5, Sandboxing, and the Mac App Store — first a warning in 2012, then this year when 2.5 shipped. Apple tried their best but realistically speaking we simply would have had to cut numerous Coda features, like the Terminal, MySQL local access, editing files as root, and more. To be honest, I was pretty nervous to be pulling Coda from the Mac App Store. But when we finally did it, I felt an incredible, almost indescribable sense of relief — mostly because as we began to wrap up bug fix releases, we were able to immediately post them to our customers within minutes of qualifying them. My god. That’s how it should be. There’s just no other way to put it — that’s how you treat your customers well, by reacting quickly and having total control over your destiny. To not be beholden to someone else to do our job feels just fantastic. (Also to not pay someone 30% in exchange for frequent stress is a fine deal.)

So, how’d it go? After running the numbers, it looks like Coda’s sales have not suffered significantly since leaving the Mac App Store. 

Coda was removed from the Mac App Store in mid-October, at the same time version 2.5 was released. Since new releases always generate a short-term sales spike and we wanted the numbers to be fairly representative of “typical sales”, we looked at one month on either side  — September and November.

The results were interesting. We sold a couple hundred fewer units of Coda post-App Store removal, but revenue from it went up by about 44%.

Now, two explanations for that: in addition to keeping the 30% that would have normally gone to Apple, we also returned Coda from its sale price ($79) to its regular price ($99) alongside the release of 2.5. Even if those factors hadn’t been in play, though, I don’t think the decline in Coda revenue would have been as dramatic as we originally feared it might be.

Of course we have it easy — it’s an established app with a dedicated customer base. If Coda did not already exist or Panic was not well-known, ignoring the Mac App Store would’ve been a much harder decision with possibly larger ramifications.

App Review

The last couple of months of 2014 got classically “exciting” as Transmit iOS was suddenly flagged by the App Review team for a violation — a well-documented situation, both on our blog, and sites like Daring Fireball and MacStories. Thanks almost exclusively to these articles, we very quickly got a very nice call from a contact at Apple, and the situation reversed almost immediately. Everything ended up just fine.

But I can’t comfortably say “the system worked”. It’s still an awful and nerve-wracking feeling to know that, at any minute, we could get thrown into a quagmire of e-mails, phone calls, code removal, and sadness, just by trying to ship something cool.

There’s a little more history here than I’m letting on. We had a very long, very torturous situation with Status Board almost being pulled that we’ve never written up out of sensitivity to our relationship with Apple. I only mention it here because it proves that it is possible to fix these awkward rejection situations without Apple suffering negative PR in the public eye — we did that “offline”. But it took an absolutely massive amount of mental energy and time to work through — positively Sisyphean. I would never want to do it again — I’ve run out of patience, I guess. I can say for certain that the “bad PR” version of the app dispute process is monumentally more effective. Which is a shame.

The ultimate irony, though, is that the press, and the pulling, totally temporarily bolstered Transmit iOS’s sales. It probably introduced the app to a lot of people for the first time. Here’s our sales chart… guess where the news hit?


When these things happen, the hardest part for me is knowing that Apple has a whole lot of good people we admire doing great work that we are inspired by, and that they are often overshadowed by teams and forces beyond their control. It must be infuriating.

Low iOS Revenue

This is the biggest problem we’ve been grappling with all year: we simply don’t make enough money from our iOS apps. We’re building apps that are, if I may say so, world-class and desktop-quality. They are packed with features, they look stunning, we offer excellent support for them, and development is constant. I’m deeply proud of our iOS apps. But… they’re hard to justify working on.

Here’s a way to visualize the situation. First up is a sample look at Units Sold for the month of November 2014:


Wow! 51% of our unit sales came from iOS apps! That’s great!

But now look at this revenue chart for the same month…


Despite selling more than half of our total units, iOS represents just 17% of our total revenue.

There are a few things at work here:

1. We’re not charging enough for our iOS apps. Or Mac users are simply willing to pay more for apps. Or both.
2. We’re not getting the word out well enough about our iOS apps.
3. The type of software we make just isn’t as compelling to iOS users as it is to Mac users. Our professional tools are geared for a type of user that simply might not exist on the iPad — admins and coders. We might have misjudged that market.

It’s really hard to say for sure. One thing is for certain: we are more likely to increase the price of our iOS software over time in an effort to make it make sense. And we’re less likely to tackle any huge new iOS projects until we get this figured out.


We generally don’t like to talk about future plans because it almost inevitably comes back to haunt us in some way. But I can confirm at least two things that will happen in 2015: a significant update to Diet Coda that will overhaul the UI, and the brand new Status Board 2 which adds fantastic features and is already entering beta. Also, Panic Sync will be added to Transmit for Mac in some form. Beyond that, we’ll have to see…


A handful of changes:

  • We formally moved onto Slack for team communication. We had nothing like this before, just e-mail. It’s been a huge boost for us, mostly because it keeps everybody on the same page a lot more efficiently, and it’s really good at searching. It can be overwhelming to keep on top of, but the good far outweighs the bad. I basically don’t get much e-mail anymore.
  • We moved the majority of our credit card processing over to Stripe.
  • We migrated our website into Git, using Vagrant and VirtualBox to allow each web developer here to run a virtualized version of the site on their desktop machine. It’s been great.
  • All of our other code projects began migrating into Git and GitLab. This was hard — it’s a lot of change and years of habits —  but we’re hoping it will be worth it down the road.
  • QA has become a lot more formalized thanks to some heroic efforts.
  • We also started to establish the idea that there are two tracks of Panic Projects: evergreens and seedlings. We want to give constant attention to the apps that people love — and the apps that bring in good money. At the same time we want to continuously experiment with new ideas, some that might succeed and some that may never see the light of day. So far, this is actually working, and it’s exciting. (The only challenge with this system is giving a chance for the evergreen engineers to work on seedling projects — their extensive knowledge of critical apps makes it hard to ‘remove’ them. We’ve gotta work on that for 2015.)


Panic is a multi-million dollar business that has turned a profit for 17 years straight.

It just hit me, typing those words, that that’s a pretty insane thing to be able to say. (And, sure, we barely qualify). Believe me, I know it won’t last forever — but wow, what a kind of crazy deal.

If you’re curious about some business stuff, our setup couldn’t be more cut-and-dry. We still have no investors or debt. The overwhelming majority of our revenue goes to employee salaries and benefits, which is just the way we want it. Then there’s our rent, our internet, some donuts and chips, etc. Anything left over goes into the magical Panic Savings Account for future projects or emergencies — we’ve always felt it was important to have some wiggle room for who-knows-what. (In the past we’ve actually reduced that warchest by simply distributing it to employees as a bonus.) We also continue to operate on standard office hours, avoiding weekends and crunchtimes with ferocious overprotectiveness, for better or worse. Maybe the most controversial thing we have is an open office, but since we have no sales or marketing teams things are usually library-quiet.


It’s been a long time since Steve and I started writing apps in our apartment — fifty lifetimes in computer years.

But the story of Panic is not about Steve and I anymore. These days, while both of us constantly dig in all sorts of trenches, more often we’re just the loud (well, I’m loud) backseat drivers — backseat drivers that often unfairly get all the glory. Let me be clear: Panic’s true asset, the thing I’m most proud of building, is the incredible team of 20 people who truly make everything happen, people who design and create these great things as a team, people who aren’t comfortable creating anything less than excellence, people I actually like.

Stepping back, of course, we’d have zero employees if it wasn’t for you — the person who buys our software and supports our work. When I’d play NES games as a kid I always thought it was corny when, at the end of the credits, the game would say “Special thanks to: you!!“. But now I get it. This is not a joke: without you we don’t exist.

We’ve just renewed our lease for another 9 years.

Here’s to the further adventures of Panic!

]]> 69
Transmit iOS 1.1.1 [Updated] Mon, 08 Dec 2014 19:30:01 +0000 UPDATE 12/11/14: After a considerate conversation with Apple, Transmit iOS 1.1.2 has been released with restored “Send To” functionality.

While the process feels less-than-perfect, this resolution is a nice reminder that, just as we thought, there are good people at Apple who will push hard to do the right thing. We hope you enjoy Transmit iOS 1.1.2.


Transmit iOS 1.1.1 is out, fixing a few bugs in our surprisingly powerful file management app for your iPhone or iPad.

Also, at Apple’s request, we had to remove the ability to “Send” files to other services, including iCloud Drive.

In short, we’re told that while Transmit iOS can download content from iCloud Drive, we cannot upload content to iCloud Drive unless the content was created in the app itself. Apple says this use would violate 2.23 — “Apps must follow the iOS Data Storage Guidelines or they will be rejected” — but oddly that page says nothing about iCloud Drive or appropriate uses for iCloud Drive.

If the issue is just iCloud Drive, why did we remove the other destinations? We had no choice. iCloud Drive exists in this sheet:


The above sheet is 100% controlled by iOS — we can’t touch it. Since we can’t touch the sheet, we can’t remove just iCloud Drive from the sheet, so we have to remove the whole sheet.


Our seriously sincere apologies to everyone who used or purchased Transmit iOS with this feature.

The good news? Transmit iOS remains incredibly capable and useful app despite this omission — as further evidenced by this awesome five-mice review for Transmit iOS in MacUser UK.


There are good people working at Apple who will read this, be frustrated, and hopefully try to fix the situation. Hopefully, we can return this functionality to Transmit iOS in some form, someday. We’ll let you know.

UPDATE 12/11/14: After a considerate conversation with Apple, Transmit iOS 1.1.2 has been released with restored “Send To” functionality.

]]> 50