A font engine optimized for resource constrained environments.
The Monotype Spark™ solution is designed for devices with small memory size, low CPU speed—or devices that just want memory freed up for other exciting features. Lower memory doesn’t have to mean low-quality, bitmap type. Spark helps smart watches, wearables, medical devices and automotive dashboards display a wider range of text without bloating the memory footprint.
More languages. Larger character sets. Different font size. A lower-cost platform configuration.
Ditch the bitmap headaches and quickly expand to new markets with non-Latin character sets and advanced support.
Rapidly adapt to new market environments and user demands.
Maintain UI performance even on the most constrained devices.
Although bitmaps may have a perceived cost-benefit, Spark can reduce expensive memory hardware changes, overall QA budget and time.
With a code size on ARM of only 98 kb, and a runtime RAM footprint as low as 20 kb, nothing takes away from your other features.
Design high-quality dynamic user experiences for anything that has a screen, whether automotive, wearable, medical, or your innovative vision still on the drawing board.
In resource constrained environments, the first place to turn to for text is often bitmap type. With the help of Spark, you no longer need to sacrifice text quality as our solution lets you execute dynamic, fully scalable fonts within your devices. Scroll the slider above to see the quality impact or a dynamic font versus a bitmap solution.
If your device needs to carry multiple languages and font styles, we can help lighten the load. Monotype has a number of tried and tested compression technologies that can dramatically reduce the size of font files, including those of Asian fonts that take big bites out of disk space. For some Asian fonts with large character counts, the overall font load can be cut by several megabytes through compression.
Font linking gives you just one font file to manage. Unlike the Freetype offering, instead of loading multiple font files or lumping all your languages in one heavy file, we link several files and serve them dynamically from the cloud. Font linking points your application to a reader file prioritized according to the languages most in-use in the region where your product is shipping.
A car being shipped to Japan, for example, would first search and serve Japanese character sets, followed by Latin or Korean. If it was headed to Canada, it would first serve Latin characters followed by Arabic. With just one font file to manage, you can serve multiple languages with just a quarter of the memory space you’d need to load them individually.