Semiround watches - none of the provided fonts match the native field look and feel.

For my Peter's (Hi Vis) Pacer I'm offering the option to also load the data field in non-single field mode.
When working in this non single field mode (showing 2 - 3 or 4 fields) I would prefer that the datafield would have the same fontsize as what the native data fields have in this mode, but this is unfortunately not possible.... None of the fonts that are provided match with any of the fonts that we can use via Connect IQ.

(sorry for the quality of the pics, was getting pretty dark here.... but it should give a general idea )

2 fields:
FONT_NUMBER_THAI_HOT too big...
[IMG2=JSON]{"data-align":"none","data-size":"full","src":"https:\/\/s26.postimg.org\/i6kyldkax\/2fields_thaihot.jpg"}[/IMG2]

FONT_NUMBER_HOT too small...
[IMG2=JSON]{"data-align":"none","data-size":"full","src":"https:\/\/s26.postimg.org\/vwp551349\/2fields_hot.jpg"}[/IMG2]

(I also loaded a custom font with beba neue pixel size 90 and that nearly matches but as that requires +2k memory this is not an option to use that workaround - I have no memory to spare....)

4 fields:
FONT_NUMBER_HOT too big...
[IMG2=JSON]{"data-align":"none","data-size":"full","src":"https:\/\/s26.postimg.org\/iei8sqqyx\/4fields_hot.jpg"}[/IMG2]

FONT_NUMBER_MEDIUM too small...
[IMG2=JSON]{"data-align":"none","data-size":"full","src":"https:\/\/s26.postimg.org\/k7pqut1jd\/4fields_medium.jpg"}[/IMG2]

I can understand that it would be difficult to change the font sizes for these devices to match with the font sizes that are used in data field mode (as it would break existing connect iq apps), but could you make it one of the "checklist items" for the device teams that new devices do not have this issue? Designers should be provided with fonts that exactly match the fonts in the native datafield layout in order to allow them to replicate the same native look and feel...

<b>If memory allows...</b>
As the fonts must already be on the device and known by Connect IQ (the SimpleDataField layout does look fine) it might be an option to introduce a new set of constants (eg FONT_NUMBER_DF_1, FONT_NUMBER_DF_2, FONT_NUMBER_DF_3, FONT_NUMBER_DF_4 where the number can indicate in which layout-configuration the font is used).

This would allow to not break existing apps and still provide the option to custom datafields to look to be more in line with the native look and feel.