On April 1, 2017 Ancestry discontinued support for TreeSync, rendering the software largely unusable for many FTM users. Software Mackiev was unready for that change, even though they had not only known it was coming, but they had gotten a 4 month extension from the original target date from Ancestry. Three-and-a half months later Jack is cheerfully trumpeting that we’re at the finish line…but for a large chunk of FTM users, we’re not closer to getting back to the basic functionality we enjoyed on March 30.
I keep seeing Jack (and his wife apparently) complain about how much “free” software they’ve “given away”, and how hard they are hawking $20 hats and other trinkets to recoup their expenses
That’s bad enough, but the kicker is this: once the software works as it once did, you’re likely to be disappointed about how it’s essentially the same software you’ve used for

years. This “update” is nothing more than restoring lost functionality, and a photo feature that has almost no controls and you’ll never use. We’ve waited all this time, paid our money and waited, suffered through not being able to effectively use the tool that is central to our work…for essentially nothing new.
It’s the same interface, with the colors reversed. The SUPER ugly/kludgy Ancestry Hint merge screens? Same. The People/Facts screen? Same. Places, Media, Sources? Same. It look EXACTLY the same. Maybe color coding will be helpful down the road…but I promise you I wouldn’t have taken my trees offline for 4 months for color coding. Or a photo tool that does next to nothing, and doesn’t do what it claims to do very well.
Going back several months, I said my worry was that this software company was over their head with this package (Mackiev’s latest update engenders even less confidence, puts 2017 release 3 weeks behind with no firm date for release). Mackiev is a company that has focused on smaller, offline, products. This was a huge step into a product that had a large, passionate, knowledgeable and that was connected to a 3rd-party, online vendor, and they clearly weren’t ready.
In my support sessions they have indicated that they are “overwhelmed” by the issues related to this “finish line” release, and they can’t deliver ETA’s for either resolution or even response. It’s clear to me that they overestimated how “done” this release was, so they are understaffed to deal with the volume of issues they’re facing.

This continues a long line of underestimations by this company, from thinking a handful of beta testers would suffice, then 1,000, then 25,000 to thinking they would release the first beta in November of 2016 when they couldn’t release it until well after April 1st.
I have no confidence this product will survive. Given my decades of software deployment and support, it seems likely they completed this release at GREAT cost to the company, sell the release as long as there is demand, and then sunset the product before they have to do another release. I keep seeing Jack (and his wife apparently) complain about how much “free” software they’ve “given away”, and how hard they are hawking $20 hats and other trinkets to recoup their expenses. Not a good sign…but there’s not a good sign anywhere with this company…
One thought on “Family Tree Maker 2017: 110 day (and counting) since we had working software”