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!)
This is usually when we start making announcements about Macworld for next year. We have some different news this time, though: we’ve decided not to have a booth presence on the show floor in 2013.
This was a tough decision to make, as Macworld gave us our first real “meet and greet” with our customers. One of our first shows was back in 1998 when we shared OmniWeb for Rhapsody, alongside Bare Bones Software (they were showing off a pre-release of Mailsmith), to a new set of OS X-ready users. Our presence included a good chunk of the company, a few computers, and a shared booth.
We do software, and increasingly the Expo Hall at Macworld has been shifting toward hardware. To better serve our customers, we decided to pursue a more personal way to interact and talk software during the show.
(By the way, Macworld still has a full lineup of great talks, workshops, and special events.)
So it’s very important that we continue to make that happen. We’re stepping out and trying something different.
But we’ll still be around
This year we went to a new thing called Userconf. When we heard Chase from 37signals talk about their experimentation with showing off Basecamp, live and in-person to customers, we were intrigued. With OmniFocus (and all of our apps), introducing the app in a minute is difficult (You put things in completable projects after you do a brain dump and use contexts as places or things to do them!), so having 30 minutes to talk about specific features or concepts would be pretty cool.
So, we’re going to try it with The OmniFocus Setup! You can put your name and a question in for a session, and we’ll do the best that we can to see everyone. (With the caveat that, depending on interest, we might have to filter them a bit.)
What The OmniFocus Setup is
So, on January 31st, we’re going to schedule a full day’s worth of OmniFocus “learning sessions” — usually 1-on-1s, but we’re going to turn popular topics into group sessions, too. Someone that really knows how to use OmniFocus (an Omni person) will be there to talk through workflows, features, or whatever, on iPhone, iPad, or Mac.
We’re also going to be doing another thing that we’re waiting to announce until early January, so follow us on twitter if you’ll be around during Macworld. (Remember the get-together during Macworld 2007?)
And a Little Bit More (Update!)
We’ve had a pretty great response to our plan for 1-on-1 learning sessions. A few other people (you’ve probably heard of ‘em) were excited enough to volunteer their brains and know-how, so we’ve added a bit more to our day.
If you’ll be in the area this year, please join us for a set of talks on OmniFocus with Kourosh Dini, Sven Fechner, Dina Sanders, Tim Stringer, and Mike Vardy. Afterwards, we’ll have a panel discussion. All the details here, and check back later for even more!
Again, sorry for the inconvenience, we’ll be back to our normal office hours tomorrow morning.
Previously:
For reasons unknown to us, our incoming phone system is down. We’re working with our service provider to correct the issue and apologize for any inconvenience or confusion this may have caused anyone trying to reach us.
In the meantime, we can still be reached by our usual email addresses and we will get back to you as soon as possible.
For Omni Mac app related questions. Use the Send Feedback link inside of the Help menu.
For Omni iPad app related questions. Use the Contact Omni link insed the gear menu of the Document picker.
And finally for OmniFocus for iPhone. Use the Send Feedback link in the Settings screen which is accesable via the Gear toolbar item on the home screen.
Email addresses are also available here on this website, just visit the product page and select support.
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 omnioutliner-ipad@omnigroup.com.
In OmniFocus for iPhone 1.15, one of our most-requested features went live: TextExpander Touch support.
There are so many different ways to use TextExpander with OmniFocus so I won’t even begin to offer suggestions here, but there’s a lot of reference material out there to link to.
Kourosh Dini goes a bit further and performs some calculations inside action titles, especially for “waiting for” contexts.
Michael Schechter goes one step further, completely automating a clipped email by populating context and project fields, but it won’t work in OmniFocus for iPhone. Sorry!
Finally, a very useful rundown of TextExpander by Thanh Pham. Mac-centric, but nearly everything works with TextExpander Touch & OmniFocus.
You can find out more about TextExpander Touch (and the original Mac variant) at Smile Software.
Dan W., current holder of the newest Omni employee title, uses TextExpander extensively:
Everyone appreciates a timely response and sometimes it’s required. I can’t always reply to messages right away—when I need to research a topic or have a conversation with someone—but OmniFocus helps track this and doesn’t bug me to send that email until all the required tasks are done.
TextExpander snippets for me are most useful in creating template email skeletons. Each email draft is an OmniFocus task and the task’s “Notes” field is my scratchpad for composing my message. My basic template sets up a text based form that includes ‘To:’, ‘CC:’, ‘Subject:’ and ‘Message body:’ with some space to write the body, it even places my curser just after the message body so I can start typing in the right spot. TextExpander Touch can’t prompt for user input like the Mac application can (an iOS limitation), so I rely on these text based prompts.
‘To:’ and ‘CC:’ remind me to call out who I’m looking for a response from and who’s just listening in. Plus, they also work as a reminder when I think of someone else I’d like to bring into the thread. As I’m composing my draft I have snippets to create URL links from my clipboard, properly case Omni product names, or include my email signature.
When I’m ready to send, I’ll copy and paste the template fields into an email message and hit Send. I also remind myself in the email template to create a “Waiting for response” placeholder task once I’ve sent the email.
OmniGraffle’s drawing tools have changed! In a great, really-saves-you-time kind of way.
You’re no longer entering a “mode,” per se, but rather enabling an additional set of drawing tool buttons.
The big change here is that we’re moving back to a more desktop-esque experience and away from our first assumptions about touch. At least for the drawing tools.
Joel, OmniGraffle’s PM, wrote a post about this when it was first implemented:
The interaction model is very quickly moving towards the established behavior on the desktop despite being a touch interface — Mimicking the desktop behavior is proving to be a huge win most probably due to its familiarity. While some may say that thinking of finger touches and the like as if they were a mouse click is flat-out wrong on a touch device, maintaining expected results here is more important (emphasis added), in my opinion. It’s the same application on two different platforms, and should act in similar fashion to itself unless completely warranted by the features of the platform it’s running on.
It’s very easy to use, even if you’re unfamiliar with OmniGraffle for Mac:
You’ll see the new Draw button in the toolbar, far right; tap it.
Tap the tool you’d like to use; tap again if you’d like the tool to stay active.
The tool inspector button lets you style the tool you currently have selected, before you draw the next shape, line, or text.
You can collapse the Draw Toolbar whenever, or select the Selection Tool to modify objects without closing the toolbar.
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.0shipped—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!
This is the final post in a series on how students can use OmniFocus to reduce stress and improve results. Previous posts covered how to use OmniFocus to collect all your tasks in one central location, arrange those tasks, and pick the best task to do in the moment. This final post will talk about using OmniFocus to review your progress.
A Life Examined
In my previous post, I talked about using OmniFocus to look at just the next task that you need to move each project forward. Focusing on a particular context and viewing next actions is a great way to narrow your list down to just the most important items that you can work now. Today I’d like to talk about the tools OmniFocus provides for making sure that you’ve set up a useful next action for each of your projects.
For each of your projects, OmniFocus stores a next review date and a review frequency. OmniFocus for iPad and OmniFocus for Mac each provide a view where you can see just the projects that are due for review.
There are many different ways to use the review features of OmniFocus. I’ll talk here about an approach that works well for me, and that I think is great for students. You can also explore our forums to see what others are doing.
To review projects in OmniFocus for iPad, go to the Home sidebar and tap Reviews. OmniFocus will then show all your projects due for review in the sidebar. If this is the first time you’ve looked at the Review view, there might be a lot of them! Don’t worry about that. Let’s get comfortable first, then I’ll talk about some strategies for tackling reviews.
Tap on one of your projects in the Review sidebar. The main view will show just that project, similar to what you get when you focus on a project.
At the bottom of the main view are a few additional controls. The box toward the left of the main view shows when the project was last reviewed and the review frequency for the project. You can tap this box to change the review frequency.
A good guideline is to choose the initial review frequency for a project based on the amount of time you’re willing to go without taking action on it. For example, suppose you’re taking a challenging math class and are determined to stay on top of the assignments. You might set the review frequency on that project to every day. Or maybe you have a reading group that meets twice a week. It might make sense to review that project every three days. At the other extreme, you might have some partially developed ideas for projects that you want to be reminded of occasionally, but don’t care to make progress on right now, like Hike the Pacific Crest Trail. For a project like that you might set the review frequency to several weeks or months.
The next set of controls at the bottom of the view shows the project’s status. At first, most of your projects will probably be active. This means that tasks from the project appear when you show next or available actions. When reviewing a project, you might decide that it’s done. (Huzzah!) Tap the happy checkmark to mark the project as complete. Or perhaps you’ll decide that you’re no longer interested in your project to build the world’s tallest plastic cup pyramid. That’s OK, you can tap Dropped and remove the project and its tasks from your remaining actions. (It will still be listed under all actions, in case you decide you want it back.) Or maybe you’ll decide that you’re just too busy to work on some project right now. Tap On Hold; the project and its items will no longer appear when you show next or available actions. Unlike a dropped or completed project, the items in an on-hold project will be included in your remaining actions, and the project will show up for review based on its review frequency.
The final control in Review mode is the Mark Reviewed button in the lower-right corner. This button does what it says. So, when should you tap it?
For Your Consideration
Here are the questions that I ask myself before marking a project as reviewed:
Is this project done?
It seems kind of funny to include this question, but I’m serious about it. Sometimes I’ll catch myself with a project that has a next action, but on reflection, I’ve already accomplished what I set out to do. For example, suppose you have a project to “Form an Ultimate Frisbee team”. You’ve rounded up enough players, signed up with the Intramural Sports office, and you have your game schedule. The last task on your list is “Follow up with Adam again about being on the team”. Adam’s a big boy and can get back to you if he wants. Mark the project complete and move on!
Should this project be put on hold?
If you won’t work on it between now and the project’s next review date, then put it on hold. There’s no sense having its tasks cluttering up your view if you’ve already decided that there isn’t time for it.
What’s the next action?
Every project should have at least one task under it. To keep your project moving forward, make sure you have a clear next action.
Is this project still something that you care about?
Sometimes you might not care much about the particular project, but still care about the outcome. For example, we all take some classes that we don’t find particularly engaging, but if your goal is to earn a particular degree or get into a particularly advanced class, then you can use that as motivation for the current project. On the other hand, if the project isn’t something you care about anymore, and you’re OK with the consequences of that, then you might do well to make a conscious decision to drop the project.
When you decide to drop a project, consider whether there are any follow up actions you should take. Do you need to let anyone know that you’ve changed your mind, e.g., teammates, club members, instructors, your advisor? Are there course drop forms that need to be filled out? Project review time is when you have a chance to think of these things and add them to OmniFocus. You might even create a new project for dealing with the fallout from dropping the first one. For example, suppose you decide to resign the presidency of the chess club. You might drop your “Lead the Chess Club” project, while adding a project “Resign Chess Club Presidency”. That new project probably includes tasks like “Tell the VP that she’s in charge now” and “Turn in the club president binder”.
Is this project stuck?
Have you been unable to make progress on it? It’s easy to beat ourselves up when this happens, but try not to do that! Instead, notice when you’re stuck and consider this a message from yourself to adjust the project. Often that means coming up with a different next action. Make sure the first task in the project is something small and actionable. “Write first draft of term paper” might be too big or too vague to help you get started. Instead, try something like “Go to library and find two books related to term paper” or “Write very rough draft of first paragraph of term paper”. Coming up with a small but actionable tasks is a great way to get unstuck.
Does this project have the right review frequency?
Once you’ve thought about the other questions, consider whether you should review the project more or less often in the future. For example, you might want to start reviewing a project more often as you get closer to a deadline. Or maybe you have a project that you considered dropping, but decided to keep around. For a project like that you might consider increasing the time between reviews. I think of this as a “soft drop”; I’m not ready to give up on the project yet, but I’m leaning in that direction.
When to Review
Different people have different strategies for when to do project reviews. These days, I usually do a quick morning review over a cup of coffee. As a student, I was allergic to mornings and tended to do reviews in the evening.
Getting started doing regular reviews can be a bit daunting at first, especially if you already have a bunch of projects in OmniFocus. One good strategy is to do all of the project reviews that are scheduled for today, plus one or two of your past-due reviews. This will let you catch up without being overwhelmed. Another catch-up strategy some people try is to have a marathon review session. Don’t do that! Reviews should help you feel good about being on top of your projects. Trying to review too much at once is mind numbing. Personally, I can’t successfully review more than a handful of projects at once. Beyond six or seven I’m not really thinking about the projects anymore; I’m just checking them off.
Reviewing on the Mac
OmniFocus for Mac provides similar review features to the iPad edition, but they’re organized a bit differently. From the Perspectives menu, choose Review to view all of your projects sorted by next review date. To change the review frequency or project status, you can use the Project Inspector. Use the Show/Hide Inspectors toolbar button to reveal the inspectors.
Click on a project in the main window, and the inspector will switch to the Project Inspector with controls for changing the project status, review date, and review frequency. To mark the project as reviewed, go to the Edit menu and choose Mark Reviewed.
Advanced Features
At the Omni Group, we want OmniFocus to be approachable and provide useful basic features from day one. Beyond the basics, OmniFocus provides a powerful toolkit for graduate-level task management. I hope this series has helped you see how you might use OmniFocus as part of your efforts to achieve the results you want in school (and in life). We covered the basics and some intermediate level features like focusing on projects or contexts, adjusting the view settings, and reviewing your projects.
There’s still more to explore. To learn about more advanced features like hierarchical contexts, action groups, custom perspectives, on-hold contexts, and more, check out these resources:
OmniFocus is a great way to get a better handle on your projects and tasks. You can download the Mac app here for a free 14 day trial, read more about OmniFocus for Mac, or check out OmniFocus for iPad and iPhone. And be sure to contact our amazing support ninjas if you have any questions.
Last week, our friend Lotus came to the office one last time.
She was a cat, with a single-digit employee number, who neared 19 [years old] — that’s just shy of 100 in equivalent “human” years, according to the Cat Calculator.
She came to us via a friend of the company, Sonja, who relayed the “Origins” story:
Nearly 19 years ago I was walking home from the grocery store and this little black fluffy cat started walking with me and whining oh so pitifully. I petted her and gave her attention and she wandered off but in the next few days I saw her again and she followed me all the way home. She knew a sucker when she saw one. I took her upstairs and gave Sean plaintive eyes and so we made up some Found Cat posters. We already had two cats, so an online friend agreed to foster her for a while.
Lo and behold someone called saying this was her cat, her apartment had been broken into and some of her cats had gotten out. Hooray, she arranged with the foster person to get her cat back. Yet, within two weeks this same cat was out again and following me around again. I carried her upstairs and called the owner. She said something to the effect “oh she was acting differently so I didn’t think she was my cat so I let her out.” I was livid. She said something, I think, about how she could take her back if I wanted but there was no way I was going to let that happen.
While trying to find a permanent home for her we realized, oops, our youngest cat, Fnert, was an unfixed male and we better do something about that pronto. But that fluffy black kitty was on to us and, I kid you not, the night before his appointment she went into heat and I was woken up by screeching and howling and walked into my living room to find the deed being done.
Shortly after, the peeps at Omni agreed to take her in, knowing she was probably pregnant. Five adorable kittens arrived.
The rest of her history is with Omni but I have always been proud that this stray I rescued ended up having such a sweet deal. My thanks to all the Omni peeps who gave her such a great and long life.
A few months ago she went into a wonderful retirement home (courtesy of Andrew’s house—thanks Andrew!) and did some sunbathing, meowing, pétanque-playing, day-trading, and White-Russian-drinking. She was never really close to her offspring, so there weren’t grandkittens to spoil.
She had kittens during the 1994 Olympics, each named after a figure skater: Elvis, Surya, Bonaly, Viktor. She’s survived by Viktor, her firstborn, who lives with Ken.
A bit more about Lotus (and loss) at the personal space of Bill, our UX lead.
Thanks for helping with some of our company’s culture, Lotus, and for welcoming us to the office every morning for over 18 years.
