I've been mapping my DNA for about two years now. Part of the process is finding the common ancestors between three or more DNA donors that match a segment of shared DNA. I spend an enormous amount of time manually browsing through ancestral trees searching for a common name, when I would think that a computer could do this task for me. But I've searched for an application and haven't been able to find one that does this.
Let me explain the process in more detail. It isn't just getting an application to try and find the ancestor between person A and person B, which is a process that most family tree applications do.
First, the process starts with looking for matching surnames. But this must include looking for all variation of the surname -- so for instance, Schmidt and Smith, I've discovered can be the same surname. And there are many example of this situation that soundex doesn't seem to catch.
Secondly, once matching surnames are found, you need to look for matching given names. And if you find matching surnames that have the same given name, you need to verify this as a potential match by looking at birthdates, deathdates and place names.
But, I often come across surnames that match, but there may not be any given names -- then I have to look to see if any of the matching surnames may have resided in the same town/village/region.
Now let me bring you back to the math of this process. Most/many of my DNA matches have 256 or more end-of-line ancestors. If I have 5 matches with 256 EoL names, that's a lot of comparisons. This is not factoring in the variance of surnames and given names. In addition there is the importance of including the dates and place names as a factor that can lead to a matching common ancestor.
Thanks to lkessler's answer: the "Mirror Tree" concept is close to what I'd like to see in an application for finding common ancestors (but as I mention in the comments, the "Mirror Tree" method, using Ancestry's online service, has it's limitations and doesn't work for me). The algorithm that Ancestry uses for making this process possible is what I would hope to see in a localized application that uses one tree (or GEDCOM file).
All my data is kept in one family tree database (or GEDCOM), and I would like this "matching" software to work with a GEDCOM (either by reading it or importing it).