Tom:
When I got the Navworx unit for my experimental Avid Flyer running a Jabiru engine I had WiFi issues.
I have worked with Navworx and my suspicions were that the electrical noise in my cockpit and many other rag and tube aircraft, may be too much and interfered with the WiFi.
I would get a "no Heartbeat" message on my Android pjhone or tablet.
I downloaded a WiFI analyzer appon my phone and could see I had a strong WiFi signal even though the IFLY said I had no connection. My Navworx unit was just under my seat only 12" from the tablet or phone.
It seemed to give me that error signal when I was descending over heavily populated areas to enter the pattern. I could see many WiFi signals popping up as I got lower in the pattern.
I discussed this with Bill at Navworx and he is working on allowing the Navworx unit to change channels when interference causes connection issues.
The navworx and IFLY staff have been very helpful with my issues.
Since then I have learned to make sure the phone and tablet are NOT connected to the Internet in any way.
I recently flew from SoCal to OSH and had very minor issues. We were a flight of 5. One other in the flight had ADS-B In/Out. When out of range of a tower i would loose everyone but the other aircraft with the In/out.
ADS-B has alerted me to two aircraft approaching head on in the last month. The aircraft had not seen me and when I would do a sharp evasive manuever I could see by the reaction that they had just now seen me.
By the way one of my wingmen uses a serial connection to his Garmin presentation AND uses WiFi on the IFLY application on his phone. He says he gets more info from IFLY as to position, altitude, climbing/descending speed, bearing, etc than he gets from Garmin.