The Blog

Marching slowly but surely towards beta

by Linda Sharps on April 2, 2007

We were having a discussion this morning about OmniFocus and the work that remains to be done before we can post a beta. The opinion was put forth that a personal productivity app that is even so much as 90% completed might as well not work at all, since it would inevitably disrupt your workflow and ultimately reduce your productivity rather than improve it.

I can see how this might be so, but I'm interested in what you guys think. Would you rather start using an early, incomplete beta version of OmniFocus with—potentially—some missing features, or would you prefer to wait until the app is feature-complete and (mostly) guaranteed not to suck?

(DISCLAIMER: no such guarantee actually implied.)

At the moment, the question is sort of moot because the app is definitely not ready for beta, or sneaky peek, or even for posting screenshots. We've got a few big features to wrestle into place, and a lot of bug-crushing and UI-polishing, and only a small team of engineers to get it all done.

As we look ahead to the steps towards final release, though, it would be nice to get your opinion on the process. We know a lot of you have been waiting and WAITING to start using Focus, and I promise we are working really hard to get it in your hands.

 

Comments

Yes, definitely. I wouldn't use a beta app for my full productivity trial anyway, but I would certainly like to see what features are in the wings so I can make the decision on how much I should commit myself to another app. Right now, I've been tentative about my embracement of Thinking Rock. I'd love to see if OmniFocus is right now, so I can have some early data.

Chris Robb

04.02.07 7:17 AM

I'd definitely like to see it 90% complete if it gave an idea of what it would be like and if doing so meant that a) I could contribute to catching bugs, bad UI, counterintuitive behaviour etc and b) I could boast to one or two people while, erm, keeping to any NDAs you might impose.


Wouldn't the benefit of a closed-ish beta in terms of diversity of useage and feeback outweigh any negatives? I would suspect the people using it are the sorts who would forgive a few rough edges - after all, we're all project planning nerds!


Talking of which, are you eating your own dogfood? Have you used OmniFocus to plan what's got to be done next to OmniFocus?

Jonathan

04.02.07 7:22 AM

It's important to keep in mind (not that you guys aren't acutely aware of this, I'm sure you are) that software is never done.  It's probably important to consider who thinks it 90% done and who thinks it's ready for daily use.  That is, perhaps it may be missing that absolutely key feature for some people, but how many people are there with that need?  Personally, I'd rather try out the app when it's stable enough to work in even if some of its non-necessary features aren't yet enabled.  Not to name names, but some other GTD apps for the Mac have been released as betas long before they were halfway stable and that was something that certainly should've been handled in a private beta.


Long story short, I'd rather a public beta wait until it's stable enough to not be a headache but not necessarily until it's 100% 1.0 feature complete.

Phil Dokas

04.02.07 7:23 AM

I have auditioned a number of GTD applications in the past, and generally I never commit to anything until I am satisfied that it is stable and what I'm looking for. So I am used to running duplicates in multiple programs; not really trusting them yet, but just seeing how they work out and giving suggestions as I go.


I think as long as one takes the beta tag seriously, it isn't a bad thing, and having a public beta greatly increases the number of bugs you can kill by initial release. The only negatives are the few who just Don't Get It and post rampant angry opinions about something that isn't even finished.

Amber Vaesca

04.02.07 7:28 AM

The big question would be how stable is the underlying data format? If it is stable enough that we can export and import our data, then release away. If our data will become inaccessible, then hold off a bit.


But keep this in mind: 90% complete is likely more functional than most other productivity apps out there.

Anthony Harrison

04.02.07 7:37 AM

Hi,


I'd really like to get OF as fast as possible into my hands!


Right now I'm testing a bunch of apps as a replacement for my OmniOutliner-based GTD workflow.

[I work with 3 computers in different locations and would appreciate an online solution; copying Outliner files is somewhat cumbersome. I also tried kGTD.]

It drives me nuts that no app comes close to my needs (Tracks is almost perfect unless one is unable to change the order of actions within a project).


It would be really helpful to see more of OF to decide if it's worth the wait and risking my sanity.  :-)


You wrote “definitely not ready for beta, or sneaky peek, or even for posting screenshots.”

If it's even far away from screenshots, are you shure you can hold the 1st half of 2007 timeline for a public beta?


Regards,

Stefan

Stefan

04.02.07 7:41 AM

Phil, you make a good point on the challenge of agreeing on what constitutes a key feature.


Amber, that's something we're currently pondering—if we do make an early beta available, how best to ensure the salient points (May be Unstable and Untrustworthy, etc) are understood and accepted. (And forgiven?)

Linda

04.02.07 7:42 AM

I'd say yes, I'd give it a go. If you make sure the backup options are working :)

Tim

04.02.07 7:53 AM

Beta is just that, not done! You should get some good feedback on how things are going…. my vote is to release it for the pioneers and those interested.

Rick

04.02.07 7:58 AM

Like many others I'm sure, I've been trying out a range of other apps while I wait for OmniFocus to come along, so I don't have anything that I'm fully committed to right now (software-wise).


Perhaps a closed beta period for a while might be in order if there are still features to be finished and bugs to be squashed?

dwlt

04.02.07 7:58 AM

I'd say yes as well! Do post the beta in whatever stage.

A. R.

04.02.07 7:59 AM

Personally I'd prefer to try an incomplete version at the risk of it not being stable. I've been testing out other solutions that are appearing and what I do is run it in parallel to kGTD. I can always fall back to it if something happens (or, if it's not the solution for me). I imagine it would be even easier with OmniFocus, unless the import feature (import from kGTD) isn't implemented yet. In any case, count me in the group that prefers to test it “at the risk of loosing data.”

Denis

04.02.07 8:04 AM

[...] OmniFocus News Die Arbeit der OmniGroup an OmniFocus, möglicherweise DEM GTD-Werkzeug, schreitet voran. Wann die Software fertig ist, steht noch in den Sternen: At the moment, the question is sort of moot because the app is definitely not ready for beta, or sneaky peek, or even for posting screenshots. [...]

OmniFocus News « Die Kritiker

04.02.07 8:07 AM

If I was in your situation I'd do a closed beta of 50 or so people (start with the most frequent commenters on the blog!) rather than letting it loose on the world if it's not stable.


I think that most people who are in the GTD-app purchasing game are aware that OmniFocus is coming and we aren't going to buy anything until we see if it works for us.


Phil and Amber make good points about the potential downsides, no matter how clearly you signal that it's Beta.


My heart says that I want to get a Beta of this app as soon as possible :), but I think the reality from a business pov is that there's more risk to be managed from something potentially buggy, than promotional upside from circulation and reviews. If you're thinking about the difference being about a month between “ready for early beta” and “pretty polished”, I'd wait the month if I were you and just play nicely with those of us saying we'll die without it :)

danny

04.02.07 8:16 AM

i'd use in. i've tried many gtd apps and am not satisfied with any. i suspect omni focus will be the best of the lot due to the fact you develop great software. there are no guarantees. i just don't want to invest loads of effort and time into a solution that i may abandon for omni focus, assuming the program is what i want. i'd rather get started with omni, learn along with the development, maybe give insight to users, and feel like i am moving forward rather than in a holding pattern.

dlangendorf

04.02.07 8:21 AM

Heck, I'd say you should maybe even officially call it ALPHA (or maybe use the fabled “sneakypeek” title) if it's not 100% feature-complete yet.  But I agree with the general sentiment: at this stage, I would dearly love to get my hands on whatever is ready, to offer more input.  Beta means beta!

Dan Carlson

04.02.07 8:31 AM

Bring it on. Let's see what you've got so far. Since we don't really know anything about it yet, and have no previous version (or any decent competitors for GTD apps), perhaps you should let us see it when it's still alpha, since you technically shouldn't be adding, removing, or significantly changing any features in the beta stage, and well, some of us might have some good ideas that shouldn't have to wait until version 2. Just a thought.

Jason Sims

04.02.07 8:45 AM

Prefer to wait until app is feature complete.

John

04.02.07 9:13 AM

Release early, release often!

Bill

04.02.07 9:13 AM

Remember: localizers don't even need a working application to get started…... ;-)

(honestly, a few half-baked .nib and .strings and we can get a much welcome head-start on localizing the app).


'Really looking forward to seeing the app though :-)

Corentin

04.02.07 9:25 AM

I would definitely try the beta and submit feedback. You could put directions in the read me that instruct the user to back up their iCal and other data before using it.

Jessi

04.02.07 9:26 AM

As so many of us are frothing at the mouth for this thing, I'd say an early beta is warranted.  But perhaps keep its announcement low key, such as only notifying those who subscribe to the beta announcement mailing list.


That should keep casual folks from encountering it and being disappointed if it lacks features, but will keep us rabid fans satisfied.

Darrell

04.02.07 9:27 AM

I had to abandon kGTD due to speed/usability.  went back to notecards.  Saw an article over the weekend on iGTD (http://bargiel.home.pl/iGTD/)


This is a pretty good product.  I have faith that OF will be an improvement upon this and I'm willing to pay for a professionally supported product.  But I will tell you that the iGTD app is a beta (with bugs) and I'm using it on a daily basis. 


This is a one guy shop… and I'm pretty impressed by what he's doing.  You should take a CLOSE look.  You may even want to hire him. 


He's got some great ideas… and aside from some bugs (smart folders not working, synch not up to par, no subprojects, etc.) it is a very usable solution.


So if you need to know if we are hungry… the answer is yes.  If we are ready to use pre-release software the answer is yes.  If you want to see a pretty good interface… look at iGTD.


waiting impatiently.

jimvas

04.02.07 9:34 AM

As a recent addict to this whole GTD gibberish, it seems people are finally starting to produce things that are both usable and affordable (erm…free…I'm poor). So, when I evaluate the apps, I look at one simple thing: is it better than the thing I can do for free?


If it's better than iCal tricks and paper, then I'm all in. I want to believe. The Beta-ness of it means little, you can tell if the house is worth a crap looking at the frame.

MacStansbury

04.02.07 9:41 AM

I'd like it to be released early.  I've given up on using Kinkless, and would like to be able to have early input on calendar issues, syncing with multiple computers, etc.

Tom Fort

04.02.07 9:51 AM

I agree with the earlier comment about data - a beta release would be harder to evaluate if we can't get data in and out of it.


I say that if I can't import my KGTD data (assuming that's a planned feature), then I won't be able to really evaluate the beta. If I know I can also export it back, I'd be able to spend some real time evaluating the app.

Mike

04.02.07 9:56 AM

I think we can trust you guys that some imperfections may exists ( eg kinkless), but its the workflow and logic we want to test. There are over 5 GTD apps out or in development which is great, but omnifocus is the one to watch. Because you listed to Merlin and evan etc…


Do not postpone perfection, it beta…cheesy peeps.


The sooner your out the sooner the validation or correction of your UI, features, worflow etc… Thus making it better.


Prevent procrastination, get beta out when ready, but 90% is ok….!

John L

04.02.07 9:56 AM

In the absence of a Beta, I would be satisfied just having the OF team's description of how they see themselves working with OF, so we can make our suggestions, and the doubters could be made to see why it's worth waiting.  Everyone feels a real attachment to this project, and really want it to work the way we think it will and more.  It won't be open-source, but it could be open-designed, which I think everyone would really embrace Omni for(I would, anyway).


Who knows?  Seeing Omni's ideas might just inspire a suggestion of pure, dynamite genius that would sell to people who didn't even know they needed organising. 


The question is surely:

What's the worst that could happen?


(Inspiring stuff, surely? K.)

 

Keith Bolshaw

04.02.07 10:08 AM

If the functions in there work reliably, and if (*required*) it doesn't lose data, then I'd love to see this out as a preview. If the beta-ness is related to data integrity, then please let it bake a bit longer.

Draphsor

04.02.07 10:19 AM

Get it in front of users as quickly as possible, even if it only has a few features. Definitely don't wait until it's 99.9% perfect.

Mark

04.02.07 10:58 AM

Let OmniFocus free!


Release a sneak peak so we can get our feedback in early. If it is missing features, just be clear what those are and people can make up their own eyes if they need to wait till they use it as a full time projection product.


BZ

BZ

04.02.07 11:07 AM

PLEASE release a beta (or alpha) asap!


I literally have STOPPED all of my GTD while I wait for your product.. so the result has been that ALL of my work progress has stopped! And if you don't release some kind of alpha/beta soon, I will probably starve!


I am absolutely serious, by the way!

Charles

04.02.07 11:31 AM

Definitely wait until it is finished. Half baked apps cause more trouble than they are worth. Wow us with your brilliance by serving up something wonderful and complete. :-D

Tim Jeffries

04.02.07 11:58 AM

[...] OmniFocus: Marching slowly but surely towards beta (tags: productivity gtd geek mac program unproductivity) [...]

Unproductivity » links for 2007-04-03

04.02.07 12:36 PM

I echo what Charles said. I have also stopped trying to make kGTD do what I want it to do while checking my RSS feeds several times each day, anxiously awaiting the “Come get the OF beta” post.


I also agree that something is better than nothing. I'm probably not going to spend hours and hours fine-tuning the information that I put into the very first pre-beta OF release, but I'm definitely hoping to be able to at least begin learning the UI, etc…


I think it's safe to say that most of us posting here have purchased other Omni products and are very satisfied with the quality of those products. There is no question in my mind that the v1.0 of OF will be of equally-high quality. Am I willing to deal with some bugs and missing features knowing that something great is coming? Absolutely!

Jason

04.02.07 12:38 PM

I'd love to use this in beta. As someone else said, applications are never 'done' and finsihed anyway.


I'm on the beta list for a couple of other apps, at least one of which has intensive developer interaction. New versions appear with great frequency and we beta testers provide a lot of input, that's actually listened to.


Let us have at OmniFocus!

Miraz Jordan

04.02.07 1:38 PM

Yes, I would use a beta. Let me put it another way: I need the OmniFocus beta. I downloaded iGTD, but then I decided not to use it because I figured I would just have to switch to OF when it was released and I didn't feel like taking that hit.


As good as kGTD is, it have obvious limitations—which is fine. It's not how well the dancing bear dances… and it's made a big difference me being able to do GTD on the Mac at all. Also, the great community that's sprung around kGTD has made using is much easier.


However, kGTD gave us a glimpse of what's possible. Now I need the full-on Spotlight enabled, Core Data powered, super scriptable and iCal compliant goodness that I'm assuming OmniFocus will be.


So yes, I'll test and I'll provide feedback. As long as I can easily backup my data, I'm ready. I just need to get started soon—I'm about to get really busy.

Al Willis

04.02.07 3:06 PM

A lot of people have been really gung-ho about seeing OmniFocus as soon as possible, giving various conditions / milestones as to what they believe the proper time is.


I feel it's important to note that releasing a Beta, despite calling it a Beta, will still require stability. Omni is a reputable company and it would not be in your best interests to release something that would sully your reputation. While there are a lot of people here who would love to see OmniFocus ASAP, I just ask that Omni releases a Beta when you're happy with the product.


People will always want to see things sooner. I'm sure your managers and engineers know when the time is actually right to release the product to hordes of hungry customers.

Colin

04.02.07 3:47 PM

I would want an acceptable level of functionality before spending time on evaluating a beta. At earlier stages I would be content seeing screenshots and feature descriptions.

Paul Holmstrom

04.02.07 4:14 PM

I would use a semi-complete OmniFocus full-time from day one for exactly the reasons you state: even if it's just partially complete and potentially buggy, it's surely less buggy than my aging, hacked-up kGTD install which I barely trust at all, anymore. And no other tool includes adequate fast manipulation/navigation sufficient for heavy GTD use. In short, OmniFocus even right now is guaranteed to be more complete and trustworthy than every other system I've tried, so yes, I'd use it alright.

jrk

04.02.07 4:33 PM

My vote for an early and uncomplete release

Obyor

04.02.07 5:53 PM

Hi,


using a beta is very useful to see whether I would actually agree that the features you are implementing fit my personal requirements. However, for me it would be great, if I could just use the date I got in kGTD transfert them to OmniFocus, test the beta and at any point take that same data back and inject it in kGTD. Like this my workflow would always be continued without a great risk.


Mario

Mario Batz

04.02.07 6:07 PM

I'll throw in my vote for getting a beta out early.

Mathias

04.02.07 6:29 PM

Releasing an early beta is a two sided sword. I for myself would love to get my hands on one! But since I did some software development myself, I perfectly know what early beta means. But I am sure there are many people out there who think that since it is Omni, their beta of OF will be as complete as any other beta from them was.


So my advise would be to only send such early betas to people that replied to this post and made clear they understand the nature of what they will get. This way you get valuable feedback and tell the world that you are making good progress, without

risking your reputation.


And just to be very clear, I'd love to see an early beta of OF in my mailbox soon :-).


Egon

Egon

04.02.07 7:48 PM

I've never used GTD, but I'm intrigued by the fact that you guys are creating an entire app around it.  I've bought many versions of several of your apps, and as a developer, fully appreciate the hard work you've done.


I know it makes you nervous to let things out the door early, but in today's world of sites that launch in beta, people are getting more and more used to the idea that something will evolve as they use it.


Plus… I really wanna see what the fuss is about. :)

MacDork

04.02.07 9:49 PM

“not 100% done” doesn't bother me. As long as there is no blatant dataloss, I say bring it on :) Then the beta testers can give feedback on features as-well.

Frank Rosquin

04.02.07 10:00 PM

Beta now please !


Just like another poster above, I have almost stopped using KinklessGTD while waiting for OmniFocus.


Just give us a backup feature !


Besides, isnt MS Office 2004 still in beta ?

Matthew London

04.03.07 12:50 AM

I would prefer a early release with a description of the planned feature set. It would be great to have the ability to keep the data integrity or at least export/import to the final app but knowing that it is a beta I would not use it solely as my GTD resource. I have been using Tasks (and before that Thinking Rock) and I like Tasks a lot but it has limits that keep me from accepting it as my final solution.


I hope that OmniFocus is as excellent a solution as your other products as this is one area of software that there needs a good solid program available with support behind it.

Michael Klouda

04.03.07 1:16 AM

I'd love to be part of the last 10%. The frustration of beta testing a 100% product is not having any ability to influence the small changes that could make the product much more user friendly.


If you do release an alpha or 90% Beta, one suggestion is to have printing capabilities in place for “visualization” of bugs. For my peace of mind I keep very good daily backups, so, no worries if I find today's data doesn't match yesterday's printout. I just go back a day.


Lastly, I like many others are waiting to upgrade my “trusted system” in anticipation of OmniFocus. So the sooner we can start the better. I will probably be running parallel systems as I migrate from my old system to OmniFocus. The migration can take place as the last 10% progresses.

RandyChev

04.03.07 1:32 AM

I'd prefer to get my hands on it 90% complete.  As others have mentioned, it will take some time to migrate the system(s) we use (or don't use, in my case) into OmniFocus.

Zach

04.03.07 1:47 AM

Bring it on!  I'm a crazy beta tester.  Although, if I find I don't like the product I'll probably just drop out.


The important thing for the beta… make sure there is a way to keep the data safe.  As long as things screw up and I can revert back to data, I'm okay.  I won't risk the amount of time and 'valuable' ideas put into my data being corrupted.

SpiralOcean

04.03.07 1:50 AM

Let us at it!  Just let us know what stage the version we are testing is actually at - those who want to play with a really early alpha/beta version can do so, and those who'd rather have a feature complete version can wait.  Keeps everyone happy!

Victoria Bampton

04.03.07 2:17 AM

My only question is how Focus will be better than the increasing number of free GTD apps out there. Whether this will be better answered with an early sneak peek or with all features in place is for you to decide.

Shig

04.03.07 3:09 AM

I've been using KGTD for so long, and it's not even 90% effective for me.


The customer base can help prioritize features.


As long as a decent backup module is built in, crashes shouldn't interrupt us anymore than it does when our word processor crashes.

Eric Nentrup

04.03.07 3:34 AM

I'd say that releasing multiple builds simultaneously (with varying degrees of wildness and more robust featuresets) and more frequently might also expedite the correct path for development.

Eric Nentrup

04.03.07 3:35 AM

GIMME IT!


Iteration is key; get our feedback, and improve, early.

Bruce Bullis

04.03.07 3:55 AM

As long as there's a way of backing up the data, and I can revert to an earlier version, then I'm fine.  I've been using Kinkless, which isn't perfect, and like another commenter, have ground to a halt waiting for Omnifocus.  Dying to see what you guys have been up to.  Saddo that I am, I'm constantly on the forum.  Please put me out of my misery.

Cate

04.03.07 4:08 AM

I would definitely use and comment on a beta OmniFocus; unlike many in this forum I'm only familiar with the GUI of applications but by the same token I do represent the general public, so my feedback might be useful. I'm a 20-year Mac user, I love to try out software, and I know enough not to make a beta app the only home for my stuff. I've been haunting this site and the forum for what seems like an eternity: throw us a crumb, oh OmniGod!

Alexandra

04.03.07 5:18 AM

It's not like I'm actually using something now which is working for me. Getting started down the road to something-that-will-work would be a huge boost.

Charles Albrecht

04.03.07 6:08 AM

Please, please, please release the beta…

Rishabh

04.03.07 6:09 AM

I say do it - There's a million devout and sincere OMNI / GTD fans here waiting to pitch in and do our part to help make this product successful. A good back and forth dialogue will help make the software the best it can be for it's users - obviously, us! Any reasonably aware beta user knows there will be problems. The pluses outweigh the minuses. We can get a feel for the UI, see if the inbox (input, whatever) is logical and natural, etc. I promise not to use it as a 1.0 release until it's a 1.0 release! :)

robert

04.03.07 6:13 AM

If it's a system I can trust, i'd be happy to try the beta. Features can be added later, stability comes first. Kinkless has been put aside here, it's not a system I can trust…

Jacco

04.03.07 6:25 AM

I got to this topic a little late, so most of what I would have said has already been said.


I can't begin to tell you how much I have been waiting for this software (check this site many times a day looking for a morsel of hope or news).  Using Omni's other products as a guide, I have very high hopes for OF.  I have high hopes in how it will handle my workflow, the features, etc., and if I have a chance to make suggestions before the software is “100%” complete, then I think you and the users are all that much further ahead.  Now that I know it is close, I think that it very important that the people that are VERY interested in it (probably everyone here and in the forum) have a chance to evaluate it before it released to the mainstream public.  Since we will probably be the hardest group to satisfy (I think that we are a knowledgeable group that knows what we need/ want), if you can make us happy you should be able to make the majority of the people happy.


With that being said, I think if you listened to what people were saying in the forums, then this is shaping up to be one of the most exciting software releases in a long time- the next one being OO 4.0.

Jason

04.03.07 6:39 AM

I would support using beta- none of the solutions out there satisfy me. I gave up Kgtd a long time ago, so importing is not an issue for me.  I also would really like to see some screenshots to see how it would work.


The one thing you would really want to warn people on in beta is ical syncing. Honestly, nothing, whether or not it's a getting things done application or not syncs well with ical (for god's sake, it doesn't even sync correctly with .mac or other computers frequently). But you should definitely warn people about the danger of their ical data being corrupted, and to use a separate profile if that's a concern.

Davey

04.03.07 7:46 AM

I'd love to get my hands on it, since I'm trying to find the best GTD tool.  Even if it was incomplete.  Or, if we knew what the cost was going to be or if there would be a cheaper upgrade cost from OmniOutliner, I would go ahead and get that and use it until OF was complete…  Any chance you could confirm the rumors of a $15 upgrade?

Adam

04.03.07 8:56 AM

I'd get it out. We know the risks, and I'm sure a larger group of testers would give you greater insight than keeping it in-house. Perhaps make the finished product better. Bring it on.

gary

04.03.07 9:29 AM

I think it's pretty much all been said above, but I wanted to throw my two cents in as well - I would definitely use a beta of this program.  The ability to start using the system and not have to switch over to it from another system is a big plus - I'm willing to put up with any headaches involved in a beta, because switching is no picnic either!

Michael

04.03.07 10:06 AM

I think you've got to risk it sooner or later. None of the competition is so strong that you can't sweep the boards if yours is really good.


And it's about time to get feedback from ahrcore GTD believers. Even if it's an initial disappointment, you'll have plenty of time to improve before public release to the general consumer.

Laurence Vittes

04.03.07 10:54 AM

I feel like I'm always beta testing my productivity apps, so whenever it's ready, whenever you put it out there, whenever you're done with some manifestation of the beast, just holler. You post, me download.

terry chouinard

04.03.07 10:55 AM

Although I personally would love to see a beta and provide any feedback that might help this application shine, a few things trouble me.


First, the fact you are not ready for sceenshots may simply reflect that the UI has not been nailed down yet, but suggests to me that you need more in-house development time.


Second, like most of the posts I have high expectations for this application. But, I would hate to be in your shoes if OF does not live up to public expectations. You are not going to please everybody no matter what you do, but I suggest you wait until you have a useable (aka reliable, stable, no data loss - or at least reliable backups) product before you let it out as a public beta.


Ethan can probably attest to how the most passionate fanbase can easily turn into a disgruntled mob when problems emerge. Take the time you need to get the functionality right. Ask for our input when you want it. If OF is any good when it finally goes public, then we will all still be here to give feedback on the small stuff and make suggestions on big stuff for the 2.0 release. Although it is hard for us to wait, we will thank you in the end.


Patrick

Patrick G

04.03.07 2:01 PM

Release it at 90%, as long as we can import our data from kGTD.  I'm really ready to give up on the whole thing if I don't see something soon.  The wait is killing me and my productivity.

dvand5

04.03.07 3:18 PM

Would we be willing to test out unfinished software?  You've got a large contingent of people here who are using kGTD, arguably rather unfinished software with no real prospect of being finished.  Given that, I think many people are looking to see what OF can do.


However, that's asking what we want.  You need to determine what you're looking for a in a beta test.  If you're looking for feedback about pipelines, options, capabilities, etc., I think you can probably get that from some blog postings with screenshots.


If you're looking for people to help shake out the last few bugs, you may be better served by choosing a small set of friendly users for your beta test.  I would probably not pre-release OF on the world until you're ready for the onslaught of feedback you're going to get.


My two cents.

Sean

04.03.07 8:00 PM

I prefer to wait until the software is â??supposedâ?? to be ready for prime time. Then I will be happy to try it, report bugs, and suggest features. I doubt that I will even use the first couple of beta versions.

While I agree with Amber, thereâ??s another side to â??The only negatives are the few who just Donâ??t Get It and post rampant angry opinions about something that isnâ??t even finished.â?? I find it annoying when I read so much praise and glowing reviews for software that is buggy, incomplete, and often unusable.

Iâ??ll skip the early releases unless theyâ??re reasonably full-featured and stable.

Eddie

04.03.07 9:43 PM

At this point in time, I'm more interested in what the UI is going to be like and how data is presented.  I use kGTD presently.  I've looked at some others, such as iGTD recently.


I do have several of your apps and like OMNI a great deal, so I'm leaning toward Focus, but I'd like just a preview of the UI.  From your previous blogs, I get the impression it will have the OmniOutliner type of UI, which I like.

Terry

04.03.07 11:52 PM

I am ready to test a beta as soon as the beta is ready —or sooner.


I am willing to put up with bugs, and even data loss, in a BETA.


I've participated in beta tests where I had to return a form stating I was aware the software was beta and the company was not responsible for lost data, etc. I would cheerfully sign a document like this for Omni Fu.


—Liz

Liz

04.04.07 12:57 AM

I'd like to test a beta sooner rather than later, even if that means it is not feature complete and still has some bugs and stability issues.

John Cradock

04.04.07 2:16 AM

Yes as others have already said. It's Beta OK. It's in our hands OK. We can give feed back OK. We can define “if” it's what we are looking for OK. It's a all around winner for everybody serious that wants and needs a GTD planning system. Come on guys, you're making us nuts waiting for Omnifocus, give us a break!!

Grant

04.04.07 2:50 AM

I too would welcome the chance to play around with a beta.

Zak Greant

04.04.07 3:26 AM

I'm pretty anxious myself. As long as you warn everyone that's it's a true beta (gamma?) and people should back everything up and expect crashes (and I'm sure you will), then go for it.


If you're REALLY paranoid, make it a selective beta rather than an open one—once the power users bang around with it a bit you can open it up as a more public beta.


Now as to how to determine who should be part of that private beta ... well you're on your own, kid.

joecab

04.04.07 3:28 AM

I would very much like to play with an alpha or a beta version but think that if you do release a public beta the target feature set should be very clearly defined so the community effort is focused on getting it working rather than on expanding capabilities. If you're not sure yet what should be in v1.0 then I would rather it be a private sneakypeak (with me on the list, of course).

Paul

04.04.07 4:04 AM

Release early, release often.


I think as long as you're clear about the state of the code, and warn off the faint of heart, you'll get much more benefit out of a beta test. I'm sure you're doing usability tests and getting feedback from at least a small group of external advisors, but there's nothing quite like exposing it to the world to help guide development and prioritization of features. And it's better to do that early…


I'd test it in a heartbeat…

Dale

04.04.07 4:07 AM

Yes, please!

Steve

04.04.07 5:17 AM

yes please yes please….we, as early adopters, do so with knowledge that you don't put LIVE data that is irreplaceable into a beta app….if you do, it's on your head.  Give it to us and let us run with it….you have a really receptive audience…we'll make it better for everyone, faster.

Stephen

04.04.07 6:54 AM

I'll echo the early and often release statement.  We're dyin' to give this sucker a spin!!


Seriously, open a closed beta for those of us willing to risk it and we'll report back what needs tweaking.

Anthony

04.04.07 7:52 AM

If you can make sure that data are not lost when the app crashes, and - crucially - if you are able to turn out fresh beta's at a high frequency, go for it.

The longer you put it off, the more people will start moving to the likes of Actiontastic and iGTD.  ThinkingRock is working on a new release also, so the market is maturing quickly.

Bushford

04.04.07 8:20 AM

As others have noted, the important things about releasing the app as beta seem to be:

• is it reasonbly stable? Enough so that users will be able to give useful feedback?

• Is the data secure enough so that users will not risk losing their information, and therfore valuable time, for being willing guinea pigs


That is my opinion in any case. If the two criteria can be met, release it!

Charles

04.04.07 8:25 AM

for the love of god, let this rabid crowd have a swing at it!


we've got things that need to get done!

benjamin

04.04.07 11:00 AM

Just took a position as a senior project manager with a large consulting firm and am getting back into hardcore GTD again.  I've been waiting since I heard about OF some months ago, tried everything out there on the Mac and still fall back to ShadowPlan (Palm and Mac), NoteStudio (Palm and Mac), MS Entourage (for integration of functions).  Would definitely like to see beta to test functionality and ability to integrate into my process.

Steve

04.04.07 12:26 PM

Benjamin said it best…“for the love of god, let this rabid crowd have a swing at it!”


Beta or alpha or whatever!

Babu

04.04.07 1:59 PM

I'd rather give it a go sooner rather than later. Over the years, I have tried most of the productivity apps.  My favorite remains Lotus Agenda; but I continue to long for something that'll work as well or better. All of us who play with beta software understand the risks we take, but our willing to live on the edge with them.  Go ahead and post the application as soon as possible.  Call it an alpha if you like, just get it in our hands.

Ernie

04.05.07 4:08 AM

It's *really* going to make people crazy when they find out the pre-alpha release is a picture of a pencil and a piece of paper.

Ron

04.05.07 7:39 AM

I think there are a bunch of us kGTD users.  Personally, I'd give OF a try in ALPHA/BETA/probably-blows-up mode.  (kGTD's slowness really bothers me sometimes)  I'd just back up frequently and probably run it in parallel with my current kGTD.


I agree with the release early and often sentiment expressed by some.  Get it out there and let us try all sorts of scenarios your testers didn't even think of.  :)

Dean

04.05.07 8:22 AM

As a Kinkless user, I *really* want to try this out regardless of stability.  I'm dying to see what's coming particularly since kGTD entered limbo as soon as OmniFocus development began.

Dino

04.05.07 8:29 AM

I'd vote for a closed beta of the incomplete product to get early feedback. For the public beta I would recommend waiting for the 'usable and doesn't suck' status.

Hendrik

04.05.07 9:42 AM

I would rather you work hard to use the Leopard iCal Events and Tasks API so it will integrate tightly with Mail.app, iCal (events & todos), and iCal Server.  Why release a 1.0 then 2.0 for Leopard?  Leopard ships in June.  Better to target Leopard only with a GTD application given it's new API's. 


Heck, if you released a video demo of all that in action, being used in a real life demonstration, you would have hordes of people buying OmniFocus & Leopard or even new Mac's just to be able to achieve that Zen GTD state of mind! Post it to YouTube/Google Video/vido.aol.com, etc.


I love OmniGraffle and OmniOutliner, I look forward to OmniFocus, but I will wait for it to be Leopard because the day Leopard ships I will be upgrading.  I know of many who are waiting for Leopard to buy their first Mac's as well.  These new switchers are going to want advanced calendar/todo/email integration that Leopard provides because they are all used to Outlook.  However, crappy Outlook is, it does do things that Tiger iCal & Mail cannot do. Integrate OMNIFocus into the Leopard API's and you've just kicked things up a notch.  Do it “right” and you have a killer application.


Add the Leopard iCal API's into OmniPlan and you make it even better.

James

04.06.07 12:19 AM

There are two things going on here:


1. The desire (on users' parts) and possible need (on your part) for feedback about workflow and feature set.


2. The need for bug-hunting and testing on a wide variety of setups, with a wide variety of data collections and workflows.


#2 is what “beta testing” normally accomplishes, which is why it's done at a fairly late stage, when features and interface are complete and everything's stable.


But in this case, #1 might be more what you're looking for. Workflow issues are so important to an application like this, and so personal, that getting a set of users involved in the design phase may be a very good idea.


However, #1 is not really a beta test; anyone who downloads something that's still being designed may get some very negative feelings if they were expecting a “normal” beta. So I guess I come down on the side of a “closed alpha” or “focus group” or something that's not called “beta” at this stage, assuming I am not completely off the mark and you do want design feedback. It could be completely open, for that matter, as long as it's not called a “public beta” and people are well aware of what to expect.

Jeanne DeVoto

04.07.07 12:06 PM

Of course James is right.  Everything will change when Leopard comes out, and the todo's in Mail will allow for interesting integration possibilities that cannot currently be done with 10.4 (and what many people cry out for).  Of course not everyone will want to upgrade, but i think most will.


Do things right and you'll be loved forever.

djc

04.08.07 7:36 PM

I'd love a beta now.


I think the market is heating up and some serious competitors have emerged…

Tommy Weir

04.09.07 2:29 AM

Regardless of whether you put it out for Beta, it would be nice to have some screenshots so we can see if the UI will work for us.  In particular:


- Main screen

- the work in any application (ala quicksilver) widget

- the projects screen

- the integration with email

- the integration with other Omni apps (mostly omniplan, but maybe others?)

- syncing screen


I will likely not participate in the early Beta program, but would like to comment on the basic design

Frank Lockhart

04.09.07 4:15 AM

While I understand that you gents and ladies are a probably a bit gun shy due to the spot light as well as some of the negative feedback when O.F was announced, I say put it out there now with strong caveats.


Like most of the commentors, I have been waiting for the right GTD solution and am anxious to test O.F - nothing out there now has satisfied me to date. Yes, a part of me prefers that it be baked longer. However, we are talking beta here, not Final Release.

Chenoa

04.09.07 1:53 PM

My 2¢: I will go against the grain, and say wait and go through the normal cycle. There are lots of good reasons to release early, but one great reason not to: if OF is bad, an early release will kill the project. As you can see from many posters, there are LOTS of GTD type apps for the Mac now, new ones seem to be released each week. But how many are worth it, and how many are just 'me to' apps or released way too early simply to ride on the wave of GTD popularity now. 90% are bad apps, you try them one time and immediately through it away. Omni is a big company, and this app has attracted a lot of attention, not all of it positive (daringfireball comes to mind). If you release a half baked alpha just to satisfy us Omni watchers, beware. Once you get fairly far along and OF is pretty stable, most features more or less in place, then put it out.


I would say to go a little slower then you did with OmniPlan (which I beta tested and now happily own) - it was pretty rough at the start, but the potential was pretty obvious and (for me, at least) worth the growing pains. But that is for a very specialized app that takes time to learn and understand how to use. OF is going much more mainstream, so I'd say to take it a bit slower, with a private first beta (or maybe two betas depending on the comments), then slowly widen the base.


I really look forward to this app, do a good job on it first and foremost. Oh, and for features ;) : based on CoreData, easy to sync (isync, ipod, palm, iphone whatever), oh yea…a pro version that is a hosted web solution :p.


Take care, and keep putting out the good stuff!


-SB

SB

04.10.07 5:21 PM

I've been waiting for OF since it was initially touted and as some of the other comments above denote - the market is heating up and it's all about traction.  I own most of the other Ox Products, but if OF doesn't hit my desktop soon - it'll be back to Rolling Rock or iGTD for me. 


If perfection was attainable, heaven would be a swamp.—Unknown (not me)

Paul

04.11.07 3:08 AM

To those who want perfection, again, we are talking about releasing beta software; not final candidate or GM.


I say, get it out into the wild before you lose your audience to something that may not be as good, but good enough. I think it is safe to say that the commentors to this blog are hard core, mature power users who understand this is beta - hopefully.

Chen

04.11.07 10:38 AM

Yes -  release beta sooner -  PLEASE!

Joel

04.12.07 11:53 AM

As much as I would love to get my hands on it now, I agree that there is a lot to be said for reputation - and be careful not to cause too much frustration out of those very high expectations. Most of us here presumably love the Omni products for one reason - they empower us to achieve high-quality outcomes very intuitively. I just recently did a rather complex graph and I didn't really have to learn anything to get it done so easily with OmniGraffle. You don't want to tarnish that reputation.


One option (rabies and all) would be to add some beef to the existing teaser campaign you have going on. Commit. Give us some of that UI. The main reason why so many of us cannot wait to get their hands on this is that more and more GTD stuff is coming out and it's getting better and better, but we all asume that it's not worth really committing to it if you guys come up with something really, really good. So why not make more concrete what it is exactly that we can expect? Work with a limited beta crowd, but keep the general interest high by sharing some of what's out there. Do the iPhone strategy - that way you hear from the crowd what's missing w/o having a product that then is obsolete and has caused a lot of anger.


Especially now that we have to wait for Leopard until OCTOBER!

JKR

04.13.07 1:52 AM

Don't release it in incomplete beta format unless this means that it is stable, but lacks some features. The stakes are too high with this kind of app. The first time it crashes and destroys someone's project or action list, it's on its way to trash.

Stephen Chakwin

04.13.07 1:40 PM

What Hendrik said. Of course you want whatever you let out to be reasonably solid, but the market really is heating up. I'm still loyally waiting for OF, but I must admit that every time someone mentions another new app, I do go check it out. I need *something* to use. I'd like it to be OF!

Duodecad

04.16.07 1:56 AM

Count me in. Release away, both parties would gain as being a beta there is an implicit understanding that the product will have bugs and issues. However Omni will gain much from user feedback and the user will have a good idea as to how the solution has been implemented.

N Shah

04.16.07 2:13 AM

[...] The last time I posted about OmniFocus, I mentioned we were thinking about potential early betas and the like—ways to share what we’ve built so far, without hosing your data or giving you a terrible first impression of our newest app. [...]

The Omni Mouth » OmniFocus screenshot and fe

04.20.07 5:38 AM
Commenting is not available in this channel entry.