Apple has a system in place to automatically remove applications and if they do
I am not aware of any such system, and it would be extremely controversial. However -
That SD forum thread is as I would expect it to be, unfortunately.
How about convincing Lufthansa or AirFrance-KLM to commercially release their proprietary unified worldwide plates database ?
It would create a European solution to challenge Boeing/Jeppesen’s monopoly.
gallois wrote:
What’s wrong with the French plates I use them all the time for both IFR and VFR, I like them and they are free.
The charts themselves are ok, but frequently non-standard abbreviations are used and/or the English text is not idiomatic. I find them somewhat difficult to use. Also, they’re incorrectly packaged when sent to the European AIS Database.
I agree that Italian charts are more difficult.
Nestor wrote:
How about convincing Lufthansa or AirFrance-KLM to commercially release their proprietary unified worldwide plates database ?
Lufthansa does this, actually. Their LIDO Charts are commercially available, but I have no idea about the T&C’s. Clearly it seems to be geared towards commercial operators, not private individuals.
tschnell wrote:
Lufthansa does this, actually. Their LIDO Charts are commercially available, but I have no idea about the T&C’s. Clearly it seems to be geared towards commercial operators, not private individuals.
It appears you have to use Windows-based tablets.
Not sure there are many windows tablets around today. Maybe the chinese make some? I used to fly with these years ago – see “old projects” here. Then I used a Lenovo win8 tablet2 2013-2018 which was ok and ran the drivers for Thuraya USB phones which was highly relevant before I got the Golze ADL. But while it was very versatile, as you would expect with windows, it was nothing special in terms of hardware and would shut down in heat just like almost all tablets do. On one memorable flight, Skiathos-Corfu, it shut down and I had to refer to the PDF IAP on my phone and scribble a copy of it onto my kneeboard 
And the touch screens on windows tablets are IME crap and only barely usable.
It is a real pity about Jepp terminating their old tablet products. I think they will continue the PC line because their Jetplanner is still a big product, but that only gives you PDFs. No georeferencing, although the data would still run on a windows platform running FliteMAP which gives you a moving map; I haven’t used it for years but doubt that Jepp removed the code for the GPS portion.
That’s good to know, I couldn’t understand the bleeding on the blacks as posted on here.
What will happen to the commercial operators who use an EFB – or do they get dedicate hardware running WIndows where they can still use JeppView?
Surely the “great plan” must be to move everybody from Flitedeck on the Ipad to Foreflight on the Ipad?
There is no real windoze tablet hardware around today – unless you want something quite specialised like the stuff I used to fly with, ~10 years ago, and windoze tablets (of a practical size) will always be crap because windoze is for “rich functionality” apps, and doesn’t work for “crippled functionality” apps which is the entire touch screen market. That is, unless somebody writes a new touch-screen front end (like the abortion called the Windows 10 Metro) but is there any sign that Jepp is going to spend money doing that, when they have a ready to roll platform called Foreflight?
At a given price level, all tablets have a similar performance / power draw, and my last windoze tablet (the Lenovo T2) worked fine, but the touch screen was crap; one had to use a stylus.
Peter wrote:
windoze tablets (of a practical size) will always be crap because windoze is for “rich functionality” apps, and doesn’t work for “crippled functionality” apps which is the entire touch screen market. That is, unless somebody writes a new touch-screen front end (like the abortion called the Windows 10 Metro)
What you are writing about has nothing to do with Windows proper, it’s the way most developers have been writing applications. Actually, most of those mouse-oriented applications can be somewhat adapted to touchscreen use by changing Windows interface default settings such as font size, scrollbar width, icon size and so on. The result is imperfect but usable.
Metro (MDL) interface design hasn’t gained a lot of traction, but I think it’s mostly because of perception inertia (people being too used to the classical interface), plus the scarcity of good Windows-compatible touchscreen hardware. From the ergonomic point of view, it is miles ahead of the classical pseudo-3D Windows widgets, and relies on the proven design principles of Swiss typography (which created most European typefaces, most importantly Helvetica). From the development point of view, it is also relatively convenient, with a much cleaner separation of design from function than the classical Windows interface. Everything for the touchscreen is already in there, one just needs to put it to proper use. By the way, simulating Android look and feel in MDL would be very easy.
By the way, Windows tablets aren’t dying out yet. After the first burst, the development slowed down, probably for lack of suitable Intel CPUs other than Atom Z373x and Z83x0, but it looks like something new is finally coming, including rugged tablets.
