search

dotnet / maui

.NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
https://dot.net/maui
MIT License
22.21k stars 1.75k forks source link

Remove OpenSans fonts from maui-mobile template #7313

Open dotMorten opened 2 years ago

dotMorten commented 2 years ago

Description

The default templates ship with two OpenSans fonts embedded. I'd suggest you remove these, since they require app publishers to include the Google license for these apache-licensed fonts. It seems like these are more there to show embedded fonts can be done, rather than actually being helpful as a starter template (in general I wish the template got slimmed more down and the dotnet bot svg and anything else you won't be shipping/replacing gets removed too).

Public API Changes

None

Intended Use-Case

Starter template shouldn't require user to understand licensing requirements for embedded content. It also seems like a bit much to include two fonts, just to be used by a few of the styles.

davidortinau commented 2 years ago

It's more for consistency of UI xplat. Would a non-Google font or with a different license be acceptable?

dotMorten commented 2 years ago

Something that doesn’t require you to include a license that you’re using it yes. Or avoid it - isn’t it better to use the platform fonts anyway and be consistent with the other apps on that same device? Perhaps with an easy way to change the default font used if you want it different

davidortinau commented 2 years ago

I hear you. My counter proposal is 2-fold:

  1. Add a maui-blank template option
  2. Swap the OpenSans for another with more agreeable licensing appeal. I'm looking at Segoe Variable and Segoe Fluent Icons.

isn’t it better to use the platform fonts anyway and be consistent with the other apps on that same device?

It's a choice. We hear most from developers that shipping a consistent design xplat is their goal, and that includes typography. I myself cannot remember shipping an app that didn't include custom fonts, even if some UI used the platform font.

dotMorten commented 2 years ago

It's a choice

My point exactly. Declare a resource for default font (which could/should be a built-in one). All the developer have to do is add the font and override that one resource.

Also don't all platforms contain a set of fonts available everywhere?

codeaphex commented 2 years ago

I hear you. My counter proposal is 2-fold:

  1. Add a maui-blank template option
  2. Swap the OpenSans for another with more agreeable licensing appeal. I'm looking at Segoe Variable and Segoe Fluent Icons.

isn’t it better to use the platform fonts anyway and be consistent with the other apps on that same device?

It's a choice. We hear most from developers that shipping a consistent design xplat is their goal, and that includes typography. I myself cannot remember shipping an app that didn't include custom fonts, even if some UI used the platform font.

Is using MAUI considered running on a Microsoft platform? Because that's required by the segoe license.

ghost commented 2 years ago

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.