Optimized for mobile
Foxit Software is probably best known for its small, fast and lightweight Foxit Reader app which matches Adobe Reader’s rendering quality, but beats it in speed. Some of the technique’s that Foxit’s products uses to get this superior experience are:
- Caching system for rendering large PDF files
- Strip rendering (iOS)
- Tiling rendering (Android)
- Multithread user interaction (separate UI thread and user interaction layer)
- Out Of Memory Management (critical for mobile platforms were memory is scarce)
Better rendering quality
Superior rendering quality is all about supporting the edge cases of PDF. Luckily we have a big team of engineers with a QA team to back them up, plus Fortune 500 customers that demand quality, so we have the resources and the need to provide best-in-league rendering quality.
Lets take a look at how Foxit compares to other players in the industry.
On the left you’ll see how one of our biggest competitors thinks this PDF with CMYK color should be rendered. On the right you can see how we think it should be rendered. Foxit’s color conversion engine is precise.
Competitor CMYK color
Foxit CMYK color
One the left our competitors rendering engine stumbles on this radial shading pattern function. On the right you can see that Foxit correctly renders all shading types.
Shading of competitor
Shading by Foxit
Annotating Vertical Text
On the left competing rendering engines, including Adobe Acrobat, fail to properly recognize the vertical text in this document and adjust the annotations accordingly. Foxit’s deep experience servicing different regions all around the world means that its technology has been refined to confidently handle vertical and right-to-left text.
Vertical text of competitor
Vertical text of Foxit
Out of memory management
OOM will be implemented in RDK level internal, the viewer control level. Users (developers) don’t need to do anything for OOM recover .
For V1.0, if OOM happen, the APP will not crash, our RDK will init the library again, and then reopen the document and go to the page before OOM happen, but the edit action of doc before OOM will be lose, for example the end user add a annotation before OOM, and the annotation will be lose after recover.
Also, RDK will notify the OOM happen and the recovery finished.
Suprior font handling
Foxit’s battle-tested font engine means that it can handle even the trickiest of font situations. In the examples below the PDF uses non-embedded fonts which can be a challenge when rendering the PDF. Foxit’s superior font matching algorithm is is able to accurately determine which substitute most closely resembles the original non-embedded font and uses that to display the text. On the left you can see how less mature font matching algorithm’s display the PDF and on the right you can see how Foxit and Adobe display the PDF.
Font rendering of competitor
Font rendering of Foxit
Better rendering speed
The speed of Foxit’s rendering engine is renowned and one of the reasons products such as Foxit Reader are so popular! In our testing using a repository of 1331 documents the Foxit rendering engine was able to process 1116 test files as fast or faster than one of our key competitors. In fact, our competitor couldn’t process 188 of those test files at all. Not only is Foxit technology; it’s faster, more accurate, … and it works.
Over the past 15 years Foxit has grown to have a world-wide presence spanning the US, China, Europe, Japan, Taiwan, South Korea and Australia. This means that Foxit can provide you with the local support that you need through email, online messaging and phone calls in real-time.