1. The collections being returned are not ordered. We should be able to tell the user which collections they should search first, with priority given to collections that are easy to access and most likely to contain the info the user wants.
2. When doing genealogy, our target audience thinks in terms of people, not places. They are thinking, "I want a record for my great-grandmother." But our map interface expects them to be thinking, "I want a record for my great-grandmother who was born in Adliswil, Switzerland between 1813 and 1816 and most likely attended a church within 5 kilometers of that village."
We can solve both of those problems.
When a person is browsing their family tree and thinks, "I want to find a record for my great-grandmother", they should be able to just click a button and get results from Find-A-Record. The profile for their great-grandmother contains place information and dates. We can process that information and generate the necessary query without having to ask the user anything other than "What ancestor do you want to find records for?"
Above is the profile of Charlies Davies in the FamilySearch Family Tree. This has all of the information we need to generate a query. On the right, in the "Research Help" box there is a "Find-A-Record" link. When the user clicks that link it takes them straight to Find-A-Record and initiates a search.
The integration with the FamilySearch Family Tree is done with a Chrome Extension. We will eventually add integration for many more online family trees such as Ancestry.com, MyHeritage, WikiTree, and WeRelate. Integration with popular PC programs would be much more difficult and therefore isn't really on our radar yet.
We will keep the map interface as an advanced view. We can't throw it away; it's too fun to play with.