Roboto appearing in Google Fonts to replace Google Sans Flex due to dummy Font API

The audacity of the dummy font API to replace Google Sans Flex with Roboto on Google Fonts.

When browsing typography platforms (such as the Google Fonts specimen page) or using apps that rely on dynamic font assets, text that should be rendered in Google Sans Flex completely defaults to Roboto. This total fallback alters the intended visual hierarchy, distorts the layout tracking, and strips away the variable font traits (such as custom weight and width adjustments).

Visual Evidence
As seen in the image, the Google Fonts specimen page for "Google Sans Flex" incorrectly renders the specimen text "Whereas disregard and" using standard Roboto instead of the actual geometric variable typeface.

Technical Cause
This behavior occurs because microG currently utilizes a dummy or incomplete implementation of the GMS Downloadable Fonts API (com.google.android.gms.fonts). Because the system font provider cannot dynamically fetch, cache, or map the requested font family, the system safely—but aggressively—falls back to the default system-wide typeface (Roboto).

Proposed Solution / Request
Since Google Sans and Google Sans Flex are distributed under the open-source SIL Open Font License (OFL), there are no proprietary licensing restrictions preventing their integration.

I would like to request either:

1. An enhancement to the dummy Font API to properly fetch and map open-source Google fonts dynamically.

2. The native bundling of common open-source system fallback fonts (like Google Sans Flex) within microG to prevent layout breaking across web views and GMS-dependent applications.

Start by tracing microG's dummy com.google.android.gms.fonts Downloadable Fonts API implementation and how it handles requested font families. Determine whether the work should support dynamic fetching and mapping or bundle Google Sans Flex, then verify that Google Fonts specimen text no longer falls back to Roboto.