I’m very pleased to announce that OmniPresence document syncing will ship on May 22!
For the last several years we’ve been hard at work bringing automatic syncing to our Mac, iPad, and iPhone apps, so our customers always have their latest work available on all their devices. We started by adding automatic syncing to OmniFocus in 2008, then to OmniPlan in 2011—and this week, on May 22, we will round out support for automatic syncing in OmniGraffle, OmniOutliner, and OmniGraphSketcher by shipping “OmniPresence” document syncing.
Here is what OmniPresence looks like in action:
OmniPresence is designed to work well with any Mac app which supports OS X’s Auto Save and Versions. Using the same underlying document coordination as Versions, OmniPresence lets your app know when a document has been changed on another device, and double-checks to make sure it always syncs a current and complete copy of any documents currently being edited. OmniPresence can’t prevent conflicting edits from multiple devices—but when that happens it automatically saves both versions of conflicting edits so that no edits are lost.
OmniPresence is also designed to support document syncing within teams. By creating a shared sync account for your team, you can make sure that everyone on your team always has the latest copy of every document available on all their devices.
We believe in building solutions that will stand the test of time, and we believe that your data should be yours to control—whether you’re syncing your personal files or your company’s confidential information. So rather than use a proprietary syncing service which might not be available in five or ten years, OmniPresence is built on top of open web server technologies. This means you can sync documents using your own web server, such as the Apache server built into Mountain Lion Server. (We’ve posted instructions for setting up WebDAV file sharing on Mountain Lion Server on our support pages.)
We know that some customers would rather not have to set up their own service, so we’re currently scaling up our Omni Sync Server to support OmniPresence. We’re not quite sure how much additional traffic to expect from customers using OmniPresence, so we’re not opening the floodgates to all our customers just yet—but we are trying to make OmniPresence available to all accounts as quickly as possible. (Anyone who has checked the “I am brave” box at sync.omnigroup.com should already have access, and anyone else who checks that box will be given priority access.)
Finally, a quick note for any developers out there: we will be releasing the source code to OmniPresence as part of our open source frameworks on github, so you’ll be able to take our code and do whatever you want with it. OmniPresence is already compatible with other third party apps on Mac, but because of the sandbox on iOS it will require some integration work to support OmniPresence on iPad or iPhone apps. Our first goal was simply to use OmniPresence to sync documents in our own apps—but we’d love to see other apps start using it as well!
Thanks, everyone, for your patience as we’ve built automatic syncing into all of our apps. We hope you’ll enjoy OmniPresence as much as we do!
If you’re one of our many customers who want to always have your latest documents available on all your devices, I have good news! We’ve finished our limited private test of OmniPresence and are now beginning a wide-open public test of OmniPresence for Mac.
You can start using OmniPresence today, syncing documents using your own web server, such as the one built into Mountain Lion Server. (I’ve posted some instructions for setting up WebDAV file sharing on Mountain Lion Server over on our forums.)
If you would rather not manage your own server, you can sign up to help us test OmniPresence on the Omni Sync Server by checking the “I am brave” box at sync.omnigroup.com. This won’t enable OmniPresence right away, but it will let us know that you’re willing to move your account to a test system where we’re analyzing the load produced by OmniPresence. (Until we know how much load it produces, we’ve blocked it from accessing our production systems so that we won’t degrade their performance for people who are currently using them to sync OmniFocus and OmniPlan.)
I should note that OmniPresence requires Mountain Lion and iOS 6. We’ve tried to make it work with earlier operating systems, but we ran into issues which only Apple can fix (and which they did, in OS X v10.8.3 and iOS v6.0).
We would love to do a wide-open public test of our iPad apps as well, since sharing your documents between all your devices is what really makes OmniPresence valuable. But we’re only allowed to distribute final versions of our iPad apps through the App Store.
Until we do ship OmniPresence in our iPad apps, we’re not actually done. But we’re certainly getting close!
When we decided to bring all our apps to iPad, we immediately started hearing from our customers that it wasn’t enough to just bring desktop-class productivity apps to the best mobile platform: all of the documents in those apps needed to be mobile as well, so you’d always have the latest copies of your documents available on all of your devices.
As I shared in my January blog post, we’ve been hard at work on this problem for quite a while now and our solution to this is called “OmniPresence”: your documents, synced everywhere you want them to be.
What is OmniPresence?
- OmniPresence is a way to sync folders between your devices using a web server.
- On Mac, a separate OmniPresence app churns away silently in the background, syncing any documents placed in its folders—without requiring any special support from other apps. On iOS, the sandboxing environment requires that each app add its own support for OmniPresence—so we’ll be providing free updates for all our apps (and publishing code so other developers can add support if they wish).
- OmniPresence separates document syncing from any particular back end service provider. You can use it with your own compatible web server, or with the Omni Sync Server for documents created with your Omni apps.
Here is what OmniPresence looks like in action:
… and we’re finally at the point where it’s time to enlist your help in testing this code before we ship it!
The good news is that we’ve already heard from over a thousand of you who would be happy to help us test OmniPresence. The bad news is that we can’t open this up to all of you, because we have a very limited number of slots available for testing development versions of our iOS apps.
If you’re interested in helping us test OmniPresence, here are some questions we’ll need you to answer:
- Do you have a good strategy for backing up your documents in case something goes awry? You’re helping us test unreleased software, and one of the risks is that it might have bugs which delete or silently corrupt your data.
- Will you be able to use OmniPresence frequently over the next few weeks? If you don’t have time to help us this month, it would be better to give this slot to someone else.
- Are you willing to store your documents on the Omni Sync Server—or, alternatively, to patch, build, install, configure, and deploy your own copy of the Apache web server? We’ve submitted several updates to Apache which haven’t been integrated by their team yet, so if you’re uncomfortable storing data on our server you’ll need to set up your own server with those updates in place. (If you plan to use the Omni Sync Server, please tell us your account name so we can enable OmniPresence testing for it.)
And two bonus questions:
- Which of our apps do you use? We’re adding OmniPresence support to OmniGraffle, OmniOutliner, and OmniGraphSketcher, and an ideal tester would be someone who uses all three. (Note: OmniPresence provides no benefit to OmniFocus and OmniPlan, since they already have built-in support for syncing individual changes.)
- Are you a developer who is interested in adding OmniPresence support to your own app? We’re not quite ready to publish our source code yet, but we do plan to and it would be great to get feedback from other developers before we unleash this into the wild.
Please email your responses to firstname.lastname@example.org. We look forward to hearing from you!
As I said in my blog post announcing OmniFocus 2, our goals for version 2 are to bring back to the Mac all of the design and innovation that went into our iPad edition of OmniFocus: dedicated Forecast and Review modes, clearer navigation, and a fresh look and feel. And from the reaction from people I talked to at last night’s debut, it sounds like we’ve done just that!
As with the iPad app, all navigation is now done through a unified sidebar: there is a single sidebar that includes your Inbox, Projects, and Contexts, as well as your Forecast of upcoming scheduled work, a list of Flagged tasks, and list of projects that need Review. The main navigation headers stick to the top or bottom as you scroll, so they’re always visible and accessible with a single click no matter where you are in the list.
The new Forecast mode shows you a summary of your upcoming time-based commitments at a glance in the sidebar. You can leave the forecast collapsed to see the next several days (as in the screenshot), or expand the forecast to see an entire month in your sidebar. From the forecast, you can select any combination of days to see a detailed schedule that includes scheduled tasks from OmniFocus integrated with events from your calendar.
With version 1 of OmniFocus it was already easy to add new items into your system—using the built-in Quick Entry on Mac, or Siri on the iPhone and iPad, or by sending email to your Inbox. Perhaps a little too easy: after using OmniFocus for a few months, OmniFocus could easily become cluttered with cruft that seemed important at the time, but is no longer relevant to the work you need to get done today! This is the problem we aim to solve by bringing Review mode to OmniFocus 2 (which we originally pioneered in the iPad app). Review mode walks you through reviewing any projects which you haven’t reviewed recently, making it easy to update your projects to make sure they reflect your current priorities.
Now that information about OmniFocus 2 is public, we’re happy to answer any questions you might have about it! Some of the obvious questions are:
Will this require new versions of OmniFocus for iPad and iPhone?
No, we’re not updating OmniFocus for iPad or iPhone at this time: OmniFocus 2 for Mac is designed to sync with the current shipping versions.
How soon will OmniFocus 2 be shipping?
The simplest answer to that question is that I don’t really know! A more accurate answer is that the answer really depends on what feedback we receive from all of you. We use an iterative development process at Omni, so our next step is to ship a private test release so we can get feedback from customers on how well it’s working in practice. Based on that feedback, we’ll update our design and ship another private test release (and invite more people into the test pool), and the cycle begins again. How many times we repeat that cycle depends on how long it takes for us to feel like we’ve achieved our goals for the release.
Once we finish those rounds of private testing, we’ll post a wide-open public test release for anyone to download from our website, and finish up some of the other hard work of writing documentation, translating the app and documentation to other languages, and submitting the app to Apple for App Store review. Usually this final stage takes 4-6 weeks—at that time, it should be much easier to accurately project a ship date.
How much will OmniFocus 2 cost?
OmniFocus 1 has been very successful at its current price point of $79.99—and we think that’s been providing great value for its current target audience of professional customers. But with OmniFocus 2 being much more approachable, we think there’s also an opportunity to reach a wider audience who don’t need all of the Pro features from the current edition. So we’re going to offer two editions of OmniFocus 2:
The Standard edition of OmniFocus 2 will include all of the basic features which we’ve talked about above, and will cost $39.99.
The Pro edition of OmniFocus will offer the option of building custom workflows like OmniFocus 1 does today, with its support for Perspectives and AppleScript.
Will there be a discount for current owners of OmniFocus 1?
Yes, on our online store we’ll be offering a 50% discount to current customers of OmniFocus 1, whether you originally bought directly from us or through the App Store. This means that current customers will be able to upgrade to the Standard edition of OmniFocus 2 for $19.99, or to the Pro edition for $39.99.
We would love to offer the same deal to people who wish to purchase OmniFocus 2 from the App Store, but unfortunately the App Store has no mechanism for offering selective discounts to different customers based on their previous purchases.
Will volume or educational discounts be available?
Yes, we will continue to offer volume discounts through our standard online store, and educational discounts through our Education Store.
What if I don’t own OmniFocus already? What should I buy today, and where should I buy it?
From now on, anyone who purchases OmniFocus 1 from our online store will receive a free upgrade to the Professional edition of OmniFocus 2 when it ships.
If you’ve read my most recent blog post about Omni’s Plans for 2013, you already know that we’re just a few weeks away from the debut of OmniFocus 2 for Mac. I’m really looking forward to showing it to you all… but this post isn’t really about OmniFocus 2 itself, it’s about what to expect between now and when it ships.
The first thing I’d like to clarify is that we’re only talking about the Mac edition of OmniFocus! This release focuses on bringing back to the Mac all of the design and innovation that went into our iPad edition—and it will be fully compatible with the existing iPad and iPhone apps, so you’ll be able to sync with them without paying for upgrades to all three apps.
I also want to make sure everyone understands that the OmniFocus 2 debut on January 31st is not when OmniFocus 2 will be shipping! That’s just the first time the app will be shown in public. Following the debut, we’re planning a limited private test period (which you can sign up for), followed by a wide open public test—and then (finally!) when we’ve evaluated everyone’s testing feedback and think it’s ready, we’ll ship the app. If this sounds like it might take a while… yes, it probably will!
So, if you’re looking to purchase OmniFocus today, what should you do? Should you wait for OmniFocus 2?
Well, first of all, there’s no reason to wait on purchasing the iPad and iPhone apps—as I’ve noted above, they’re not the editions which are getting a major upgrade this year.
But if you’re looking at purchasing the Mac app, it would be quite reasonable to wait until after the OmniFocus 2 debut so you know what’s coming before you make a decision. To make that wait easier for everyone, we’ve decided to post a temporary license key so you can all use the app between now and then without having to make a purchase:
License Owner: Waiting for OmniFocus 2
License Key: [KEY HAS NOW EXPIRED]
(Just copy and paste both the License Owner and License Key into the appropriate fields.)
I hope you’re all looking forward to OmniFocus 2 as much as I am! And that this temporary license key makes the wait a little easier.
Update: We had a great time showing what we’ve been working on in OmniFocus 2, you can find more details and watch a video of the OmniFocus 2 debut to learn more. Please note that the license above has now expired, but if you purchase OmniFocus 1, you’ll get a free upgrade to the Professional edition of OmniFocus 2 when it ships.
In my last blog post, I reflected on all the things we accomplished in 2012 here at Omni—in particular, the completion of our huge “iPad or Bust!” initiative. But as Professor Hathaway said to Chris Knight, “That was yesterday. What have you done for me today?”
With “iPad or Bust!” out of the way, we’ve been able to move some of our projects off the back burner and here are some highlights of what’s coming: OmniFocus 2. OmniOutliner 4. Automatic document syncing. Sandboxing. Accessibility. Visio and Microsoft Project compatibility in our iPad apps. Upgrade pricing from Mac App Store apps.
Let’s start with OmniFocus 2! For OmniFocus 2, we’re bringing back to the Mac all of the design and innovation that went into our iPad edition of OmniFocus: dedicated Forecast and Review modes, clearer navigation, and a fresh look and feel. I’m looking forward to sharing it with you! At 6pm on January 31, you’re invited to join Merlin Mann, David Sparks, and me for the first public debut of OmniFocus 2. This will be a free event, hosted at the Cartoon Art Museum (a short walk from Macworld/iWorld), and anyone who attends will get early access to the OmniFocus 2 private beta. Space is limited, so if you plan to attend please let us know.
Next up: OmniOutliner 4! I know many of you have been waiting for this upgrade for a long time—I know I have been waiting for this for a long time! For those of you who might not know the history, OmniOutliner 3 shipped in January, 2005—one year before Macs transitioned to Intel processors. And OmniOutliner 3 certainly hasn’t sat still over the last eight years: we’ve ported to Intel processors and added support for Spotlight, dictionary lookups, LinkBack, Automator workflows, Quick Look, custom toolbars, Word 2008 export, Auto Save, and Versions. But other than a few tweaks to the inspectors and toolbars, its design has mostly stayed the same: it’s starting to feel a bit long in the tooth. So… it’s due.
What’s coming in OmniOutliner 4? We’ve completely rebuilt the outlining engine to support zooming text, showing and hiding columns, and we’ve improved link handling and attachments. We’ve designed a new style system which emphasizes named styles and simplifies the styles interface. And it’s built on a modern 64-bit architecture, with a fresh new look and feel. OmniOutliner 4 isn’t finished yet, but it’s getting close: it’s now at the point where I’m using it to edit all my outlines rather than OmniOutliner 3, so I anticipate we’ll be ready for public beta sometime in the first quarter.
Automatic document syncing is almost here! We call it “OmniPresence”: your documents, synced everywhere you want them to be.
We’ve designed OmniPresence around open web protocols, so you’re welcome to use our free Omni Sync Server or to host your own cloud server. We think that the option to host your own cloud is important—not just because of concerns with respect to privacy and security (though that’s key for many businesses), but because it means you can keep that cloud running as long as you want to keep using it. As we saw with MobileMe shutting down earlier this year, individual cloud services can easily disappear as business models change. Building a solution around open standards means that our customers have a choice of hosting providers rather than being tied to a single ephemeral cloud solution.
OmniPresence is not limited to syncing with a single cloud, either: you can choose which folders to sync with which clouds. This means that teams can set up separate folders in separate clouds, and you can access files from any of them on each of your devices.
Because it’s open and you can host your own cloud, OmniPresence is designed to sync any documents you want: it’s not limited to syncing documents created by our apps. In fact, on the desktop OmniPresence is completely independent of our other apps: if you wish, you can use it to sync TextEdit documents! (But when using OmniPresence with non-Omni apps, we’ll ask that you limit the amount of space you use on our Omni Sync Server since we can’t provide infinite storage to everyone for free. On your own cloud server, though, do whatever you want!)
On iOS, OmniPresence isn’t quite that independent: the sandboxing environment requires that each app embed the OmniPresence logic within its own codebase. We will be publishing our source code for free so other developers can add it to their apps.
OmniFocus 2, OmniOutliner 4, and OmniPresence. Three major upgrades, all coming your way in Q1, 2013.
But as I noted at the top, that’s not all! We’re also working on sandboxing to help keep your Mac safe; and accessibility (currently in private beta for OmniOutliner for iPad) to make our apps easier to use by those who are visually impaired. And we’ve been working on adding Visio and Microsoft Project compatibility to our iPad apps, so it will be easier than ever to go completely mobile with your work.
Finally, with OmniFocus 2 coming we’ve been thinking a lot about how to implement upgrade pricing from Mac App Store apps. As always, we plan to offer discounted upgrade pricing on our own online store, but unfortunately we don’t have the flexibility to offer selective discounts in the Mac App Store. We’ve decided to treat the Mac App Store the same way as we treat retail stores: it’s a great way to discover our software, and can give you confidence that it’s been vetted by a third party. And, just as you wouldn’t get a discount from a retail store if you purchase OmniGraffle 5 while owning OmniGraffle 4, you won’t get a discount if you purchase OmniFocus 2 from the Mac App Store. But we’re in the process of updating our store so that you’ll be able to register your Mac App Store apps to get a discounted upgrade price when you buy an update directly from us.
OmniFocus 2. OmniOutliner 4. OmniPresence. Sandboxing. Accessibility. Visio and Microsoft Project compatibility in our iPad apps. Upgrade pricing from Mac App Store apps. I hope you’re looking forward to 2013 as much as we are! (And don’t forget to let us know if you’re planning to come to the OmniFocus 2 debut!)
As we approach the end of 2012 (or the world, according to some), I’ve been reflecting on just how much we’ve accomplished this year here at Omni.
We celebrated 20 years of omnigroup.com, of course, and we moved to new offices. But, more importantly, we finished our two-and-a-half-year “iPad or Bust!” initiative by shipping the last of those five apps, OmniPlan for iPad! Version 1.0 doesn’t mark the end of all our work, of course—but it’s a great milestone and I’m incredibly proud of all our team has accomplished.
Finishing up our “iPad or Bust!” initiative has given us the opportunity to start working through a number of other projects on our “to do” lists, so there’s been a lot of news in 2012…
We rolled out our own Omni Sync Server, so you don’t have to become a sysadmin and run your own web server just to sync your devices. (But you can still run your own server if you like: our syncing engine is based on open web protocols.)
OmniFocus has been on speaking terms with Siri since late 2011, of course, but in 2012 we’ve made it more robust and brought support for Siri to the iPad app as well. We also added support for flexible weekly repeats and TextExpander—and just this month we’ve started beta testing our new Mail Drop which lets you email tasks directly to your OmniFocus database.
This year Apple introduced iPads with Retina displays, and we immediately shipped Retina updates for all of our iPad apps. Apple also introduced Retina displays to the Mac with the new MacBook Pro, and we’ve already shipped Retina updates for OmniGraffle and OmniPlan (and are busy working on Retina updates for the rest of our Mac apps).
Behind the scenes, we’ve also been updating all our Mac apps to leverage the latest fundamental advances in OS X: this year we shipped Developer ID-signed updates for all our apps, 64-bit updates for OmniGraffle, OmniDiskSweeper, and OmniDazzle—and we expect to ship 64-bit updates for the rest of our apps soon. We’ve also been hard at work adopting OS X’s new App Sandbox.
Even before we finished “iPad or Bust!” one of our top priorities has been to build automatic document syncing into OmniGraffle, OmniOutliner, and OmniGraphSketcher—we want it to be as easy to sync all our apps as it is to sync OmniFocus and OmniPlan. We’ve been working on this for over a year and a half now, and at the start we had very promising results: it felt like magic when it worked, and we thought we’d be ready to ship last year. But though our code was finished, we found the back end service we were trying to use wasn’t working reliably, and we felt it would be irresponsible to ship something so critical until we knew the full solution was solid. After a year of trying to help get that solution working, we went back to the drawing board and designed a new syncing solution based on open web protocols. Nobody was more disappointed about the delay this caused than we were—but we knew we needed to find some way to move forward, and I’m pleased to report that the redesign has gone very well (and our new syncing solution is now in internal testing).
Which, of course, leads right into the subject of my next blog post: what’s coming next from Omni? (Stay tuned!)
Accessibility is important to us here at Omni, and we have a long history of supporting accessibility in our apps. (In 2002, we added speech recognition to OmniWeb so you could surf the web using voice commands and ask it to read pages back to you using text-to-speech—even before the operating system itself was accessible.)
Unfortunately, we’ve fallen behind in our support for accessibility over the last few years—on both Mac and iOS, but particularly on iOS. Until our apps are fully accessible, we won’t consider them complete.
To that end, we’ve been working on making OmniOutliner for iPad accessible. As anyone who has used an accessible app knows, good accessibility design goes deeper than just slapping on some accessibility tags. Once we’re sure we’re on the right track with OmniOutliner, we’ll move on to making OmniFocus accessible.
Our internal QA team has reviewed the work we’ve done so far, and we think it’s ready for some external beta testing. We can’t post public beta builds of our iOS apps, but if you’re interested in joining our private beta-testing pool please contact us at email@example.com.
20 years ago today, omnigroup.com was born.
At that time, the five of us—Wil Shipley, Tim Wood, Len Case, Mose Wingert, and myself—were still working out of our homes (or sometimes in NeXT’s local sales office, before they exited the hardware business and closed its doors). We were collaborating together on several projects, but we were paid independently—and when those projects ended it seemed somewhat likely that we might scatter to the four winds, possibly joining NeXT’s DBKit team or Lighthouse Design when our current contracts were up.
Fortunately, Tim kept reminding us that we should really form a company. (He said later that he partly did this because he thought it was an excellent idea, and partly because he didn’t know the Lighthouse/NeXT people and didn’t want to get left behind while we worked for them.)
So on Wednesday, September 9, 1992—the day after NeXTSTEP 3.0 shipped—our omnigroup.com registration came back and I set up uucp and SLIP over 14.4Kbps modems to link our home workstations together. (They were all NeXTs, of course.) We started giving everyone our omnigroup.com email addresses, gave the “NeXT Programmers” mailing list (“next-prog”) a permanent home, and started establishing a common reputation and identity.
We’ve seen a lot of changes over the last 20 years, as we transitioned from working on consulting projects to shipping commercial products, from a team of 5 to one of 52—and trying our best to contribute to the platform as it evolved from its humble (but ambitious!) NeXT roots to the wildly successful platform that is now Mac OS X and iOS.
But in some ways, that first change was the biggest: the day we decided to stop investing in our individual identities and start building our collective identity. And after 20 years, I’m still privileged to be able to work each day with smart and talented people who are passionate about creating great software—while treating customers with respect, making a living, and having fun!
It’s been almost one year since we shipped OmniOutliner for iPad. Every day since we shipped we’ve received feedback along the lines of “This looks great! But when will it automatically sync with OmniOutliner for Mac?”—and each time we reply back “We’re working on it!” But it’s been almost a year now, and I know you all must be wondering: Why is it taking so long to add automatic syncing to OmniOutliner?
To make documents with large embedded attachments more efficient, OmniOutliner 3 stores its documents as “file wrappers”, which behind the scenes are simply directories holding separate files which represent different parts of the document. (The outline itself is one file, and each attachment is its own separate file.) Unfortunately, most sync services don’t support syncing a directory as an atomic operation.
Wait, hold on, what does “atomic operation” mean? Well, in computer speak, an atomic operation is something that gets done all at once. In this case, we want all of the parts of the document to get synchronized to or from the cloud at the same time, otherwise different parts of the document might not be in sync with itself: it might be missing some attachments, or perhaps some of them will be out of date, or maybe there will be some extra attachments that shouldn’t be there.
In other words, when syncing OmniOutliner, it’s not just important to have all the parts eventually arrive on the other end; we want all of the parts of the document to show up on the other end at the very same time (and we want to know when they’ve all finished arriving) so that we know it’s safe to open and you won’t end up with a corrupt document.
One way to solve this syncing challenge is to change our document format—to stop storing OmniOutliner documents as directories behind the scenes. This change would make it much less efficient for attachments, but would also make it much more compatible with many file servers, email, web forms, source control systems, and so on. We can do that—but such a big change to the OmniOutliner file format won’t work with the currently shipping apps, and doesn’t really make sense to do before shipping OmniOutliner 4. So taking this route to solving the problem means for us to try to ship OmniOutliner 4 as soon as possible (which we’re certainly working very hard to do).
Another way to solve this problem is to help syncing solution providers (such as DropBox and iCloud) improve their support for atomic directory operations so we can sync using their solutions. The most promising option here by far is iCloud, since iCloud’s engineers explicitly do want to support syncing of file wrappers. We’ve had some of our most experienced developers spend much of the past year working on this approach—but much of that time was spent blazing new territory, and most issues we encountered weren’t within our control to fix because we don’t control the technology and servers. Fortunately, we think we’ve pushed through most of the critical issues and we’re hoping this approach will bear fruit soon.
Of course, if it takes too long to change our document format or to get atomic directory syncing working with other people’s cloud servers, another approach would be for us to add syncing support for our own cloud servers. We recently brought our Omni Sync Server out of beta, and we’re using it now to automatically sync OmniFocus and OmniPlan.
One way or another, we’re working very hard to bring automatic syncing to OmniOutliner as soon as possible: we know it’s absolutely critical for anyone who wants to use OmniOutliner on more than one device. We’re very sorry it’s taking so long!
As always, we welcome your feedback! Please feel free to leave a comment here or on our forums, or by sending me a message on twitter (where you’ll find me at @kcase).