That said, their former developers will find work easily in the EFB space, hopefully with Garmin so their product becomes equally as good.
While they did allow remote work, ForeFlight's two biggest development offices were in Austin and Houston... And Garmin, from what I hear, is absolutely 100% against remote workers, so if you don't live within a reasonable commute of Olathe, KS, fuhgeddabout it. However, I think maybe the GP team is in Minnesota? I can't remember. I don't recall any Garmin offices in TX.
I disagree with it being among the most intuitive and easy to use. Many of my private through commercial students struggle to use it.
You should see private through commercial students with a paper sectional and chart supplement.
I’m working on adopting GP since we just added a plane that does two way push with flight plans and it’s been an easier transition, but I attribute it to being familiar with Garmin’s route input formate.
I've been a Garmin hardware guy for a looong time... Probably 23 years ago when I first used a GNS 430. I've got a GTN 750 in my plane. I've used GNS, GTN, G1000, G3000, and most of the other boxes Garmin offers... But I can't make any sense whatsoever of Garmin Pilot.
My primary reason for the swap was SmartCharts. Garmin just did it better for me than FF.
That is a very compelling feature.
None of that matters. What does matter is that in 15 years and probably 3000 hours of using FF, it has never crashed. Not once.
I'm on the alpha testing team, and even the alpha version is almost always rock solid. It's impressive.
Okay, I admit: I have zero clue how many coders there are at Foreflight. However, this whole thread began because someone who presumably worked at Foreflight reported that "40-50%" of the staff was let go, including "entire engineering teams", which implies that there were enough people involved that they could not be easily enumerated.
They said 40-50% of *development* staff. I don't have a list of who's gone, but it seems from what I've seen so far that maybe many of those who were let go were newer. However, their Director of Engineering was also let go, so that impression might be completely off.
Cutting off support for 7+ year old hardware seems like a prudent cost-saving measure.
Absolutely - And generally, ForeFlight's support lines up with Apple's support as well. After a certain point, older hardware can no longer run major new OS versions. Apple does tend to support two major OS versions behind with security updates, but that usually means that two years after you can't upgrade to the latest greatest OS, you can't even get security updates any more and it's a good idea to ditch that hardware.
At that point, it makes zero sense for ForeFlight to continue to support it. The number of people who are still on hardware that old is likely a fraction of a percent.
Don’t give Garmin any ideas. The GTN series is 15 years old. Let’s not even discuss the G1000.
Yabut, the GTN Xi series is only 9 years old (and even so, overdue for replacement). The G500 TXi is 9 years old as well. The G1000 was replaced by the G1000 NXi - hey look - 9 years ago too. I believe the replacement for the NXi is either already out or on the cusp of it though I can't recall where I heard that. The G3X Touch is getting really long in the tooth at 12 years old.
The only thing that's been replaced relatively recently is the G3000 (by the G3000 Prime). I expect we'll be seeing a lot more new hardware from Garmin in the next couple of years.
I really hope that Garmin continues with pushing features from the bigger, expensive birds down into the piston market, and then the piston retrofit market. I'd love to have a retrofit of the autoland system, and I think that'll happen once whatever exclusivity period Cirrus surely negotiated expires.