Are we at that point in history where we only need to deliver WOFF and WOFF2 web font kits to users? Can we fully abandon .EOT? .TTF? I do believe .SVG can be now ignored.
In part my dream is to also fully remove .TTF or .OTF files so we're only delivering WOFF and WOFF2 . . .
How could Android be just ~3% of web browsing?
With WOFF essentially just being a compression wrapper around .OTF .TFF I believe it's relatively easy to reverse engineer the file to retrieve the font inside.
And decompression. The format is tailored to a balance between file size and speed of decompression to get the webfont downloaded and displayed as quickly as possible.
It's possible to make smaller files than WOFF2 compression, but they take longer to decompress, and the overall download+decompression time ends up being longer, on average, than a slightly larger file that decompresses more quickly. Was very interesting watching the process of determining the appropriate balance, especially since the actual amount of compression varies quite widely across a large body of fonts, determined by a whole range of factors in how the fonts are made.
Your audience should be designers and companies paying for type, not people who will not pay for type in the first place out of principle.
Or at least it was until people with gobs and gobs of money wanted DRM in HTML video.
I, personally, don't feel in my gut that it's time to leave out EOT quite yet. Windows 10 has both IE and Edge and I don't know what the deal is with that yet. And there are still a measurable number of IE8 users out there.
EOT DOES NOBODY ANY HARM. It's a Hippocratic thing.
As a former network system engineer and network/desktop support person, I trust myself completely on this. My gut has always worked real good for stuff like this. Sorry to sound like Donald Trump.
However, I have been convinced that NOT including the ttf or otf file is best. Why torture users of old versions of Android with low bandwidth connections?
If the browser doesn't handle Woff, you might as well let the fallback system fonts do whatever it is they are going to do. In time, this problem should go away completely. Bandwidth is increasing all the time and the need to buy a new phone or tablet sooner or later, is an inevitability for any user.
Last thing - a WOFF2 wrapped version of the font should definitely be inserted in the stack, BEFORE the WOFF. Do it today.
Yes. Dump it. It was a workaround to accommodate Opera or somesuch and is long obsolete. Chris Lilley of the W3C mentioned exactly this in a video. If anybody's interested, if a search doesn't bring it up, I'll dig up the link.
Just do it and charge them whatever your minimum custom job rate is. If someone need to spend a thousand dollars for peace of mind just let them do it. In the context of a big marketing campaign this stuff is immaterial.