flex_seed_scheme 1.0.1
flex_seed_scheme: ^1.0.1 copied to clipboard
A more flexible version of Flutter's ColorScheme.fromSeed, use multiple seed colors, custom chroma and tone mapping.
FlexSeedScheme #
A more flexible version of Flutter's ColorScheme.fromSeed.
Use this package like ColorScheme.fromSeed
with the following additional capabilities:
- Use separate key colors to generate seed based tonal palettes for primary, secondary and tertiary
colors in
ColorScheme
. - Change the chroma limits and values used in the Material 3 default strategy for tonal palette generation in the Google HCT color space.
- Change which tones in the generated core tonal palettes are used by which
ColorScheme
color. Changes are limited to the tones from correct core palette for eachColorScheme
color, but any tone from it can be used. Going up or down one tone is often usable, in some cases even two. - Use two additional tonal palettes tones, 5 and tone 98. They can be used to offer more
fidelity in the dark and light end of the tonal palettes and mapped to
ColorScheme
colors when using custom tone mapping. Tone 98 is also available in web based Material 3 Theme Builder, but not included in Material 3 design guide, that explicitly mentions thirteen tones and excludes tone 98. With FlexSeedScheme you can use fifteen tones, including 98 and 5.
Background #
This package was extracted from the customizable color scheme seeding engine in the FlexColorScheme package to its own package.
This allows developers to use the same customizable ColorScheme
seeding algorithms used by
FlexColorScheme, without using the FlexColorScheme package. Starting with
FlexColorScheme version 6 and later, it depends on this package instead.
If you use FlexColorScheme version 6 or later, you do not need to add FlexSeedScheme to use its features, FlexColorScheme exports its API as well. If you use FlexColorScheme you typically do not need to use FlexSeedScheme directly, its usage is baked in and used based on how you configure FlexColorScheme.
Getting started #
Add the flex_seed_scheme
package to pubspec.yaml
:
dart pub add flex_seed_scheme
or flutter pub add flex_seed_scheme
Usage #
Import the package to use it:
import 'package:flex_seed_scheme/flex_seed_scheme.dart';
Define seed colors that will be used to generate your seed generated ColorScheme
.
// Define your seed colors.
const Color primarySeedColor = Color(0xFF6750A4);
const Color secondarySeedColor = Color(0xFF3871BB);
const Color tertiarySeedColor = Color(0xFF6CA450);
Make a more flexible seed generated ColorScheme
using SeedColorScheme.fromSeeds
. It works
like ColorScheme.fromSeed
, but instead of only accepting a single seed color, it can use
three key colors as seed colors, one for each main color group in ColorScheme
.
Chroma limits that differs from Material 3 defaults for its tonal palette generation
can also be defined. Additionally, tone mapping, that defines which tone is used by what
ColorScheme
color can be customized, both are done via FlexTones
passed in to tones
.
Typically, you should use the same key colors and tones setup to produce the ColorScheme
for
light and dark theme mode. This guarantees that the light and dark theme use identical generated
tonal palettes, and only vary based on which tones are used for what color in light and dark mode.
This results in matching light and dark theme colors. This is just the norm though, feel free
to experiment.
// Make a light ColorScheme from the seeds.
final ColorScheme schemeLight = SeedColorScheme.fromSeeds(
brightness: Brightness.light,
// Primary key color is required, like seed color ColorScheme.fromSeed.
primaryKey: primarySeedColor,
// You can add optional own seeds for secondary and tertiary key colors.
secondaryKey: secondarySeedColor,
tertiaryKey: tertiarySeedColor,
// Tone chroma config and tone mapping is optional, if you do not add it
// you get the config matching Flutter's Material 3 ColorScheme.fromSeed.
tones: FlexTones.vivid(Brightness.light),
);
// Make a dark ColorScheme from the seeds.
final ColorScheme schemeDark = SeedColorScheme.fromSeeds(
brightness: Brightness.dark,
primaryKey: primarySeedColor,
secondaryKey: secondarySeedColor,
tertiaryKey: tertiarySeedColor,
tones: FlexTones.vivid(Brightness.dark),
);
Separate key colors as seeds for the primary, secondary and tertiary colors in ColorScheme
can
be provided to seed them from different key colors. If no key color for secondaryKey
and/or
tertiaryKey
are provided, they use primaryKey
color as their seed color value.
If you only specify primaryKey
color as seed, and no custom tones
configuration, identical
ColorScheme
result to ColorScheme.fromSeed
is produced.
The default chroma limits in the HCT color space used for seed generated colors for secondary and
tertiary colors in ColorScheme.fromSeed
have quite low chroma values. This makes the colors fairly
muted or pastel like. This is especially the case with secondary colors. This is by design in the
standard Material 3 color palette. You can tune this behavior by passing in a custom FlexTones
configuration to tones
. There are pre-made configuration you can use, above
FlexTones.vivid
was used. It is also easy to make completely custom configuration. Look in
FlexTones
and use the pre-made definitions as inspiration for your own configs.
Using the above configuration the following core palettes are generated, in order from top to bottom:
- Primary tonal palette
- Secondary tonal palette
- Tertiary tonal palette
- Error tonal palette
- Neutral tonal palette
- Neutral variant tonal palette

With the example FlexTones.vivid
setup, the light ColorScheme
is mapped as shown below:

And the dark ColorScheme
as:

Define ThemeData #
In your MaterialApp
you then define you light and dark mode themes using the seed
generated ColorScheme
s just as you would with any other ColorScheme
. For example:
@override
Widget build(BuildContext context) {
return MaterialApp(
debugShowCheckedModeBanner: false,
title: 'SeedColorScheme.fromSeeds Demo',
themeMode: ThemeMode.system,
theme: ThemeData.from(
colorScheme: schemeLight,
useMaterial3: true,
),
darkTheme: ThemeData.from(
colorScheme: schemeDark,
useMaterial3: true,
),
home: HomePage(),
);
}
Override Color Values #
All colors in the seed produced ColorScheme
can be overridden by providing each ColorScheme
color property in SeedColorScheme.fromSeeds
a given color value. This feature is equivalent to
ColorScheme.fromSeed
.
This is typically used to assign a given color value to primary
color, which is often used as app
brand color. When the brand color is used as primaryKey
, and as a seed color, it typically does
not end up as the primary
color in the seed generated ColorScheme
. Having a given brand color as
primary
color is often desired. To get the seed color as your primary
brand color, assign the
color used as primaryKey
to primary
color as well.
// Make a light ColorScheme from the seeds.
final ColorScheme schemeLight = SeedColorScheme.fromSeeds(
brightness: Brightness.light,
// Use a "brand" seed color as primary color in the result.
primary: primarySeedColor,
primaryKey: primarySeedColor,
//
secondaryKey: secondarySeedColor,
tertiaryKey: tertiarySeedColor,
tones: FlexTones.vivid(Brightness.light),
);
This strategy works well for the light mode ColorScheme
, since the prominent brand color a company
has defined is typically intended to be printed on white paper. If you have secondary brand colors
that are to be used, using them as seeds for secondaryKey
and tertiaryKey
will work too.
How well they will fit and match the Material 3 color system needs, if assigned to
secondary
and tertiary
directly as colors in SeedColorScheme.fromSeeds
, will vary depending
on what colors they are.
Companies rarely have brand colors suited for good contrast in dark theme mode. In that case
prefer only using the same light mode brand colors as key colors to seed the dark mode
ColorScheme
. If they do have dark mode specifications, and the colors are of same hue as
light mode, consider still using the light mode colors as seed source and only applying the
appropriate dark mode colors to primary
, secondary
and tertiary
as needed.
If there is a spec that calls for completely different main colors in dark mode, using different
hues, then seeding from them and also setting primary
, secondary
and tertiary
to these
color values is appropriate.
Customize Tones and Chroma #
In the above example, we used a predefined tone mapping and chroma setup called FlexTones.vivid
.
There are currently seven predefined configurations available:
FlexTones.material
, default and same as Flutter SDK M3 setup.FlexTones.soft
, softer and earthier tones than M3 FlexTones.material.FlexTones.vivid
, more vivid colors, uses chroma as given from all key colors.FlexTones.vividSurfaces
, like vivid, but with more colors in surfaces.FlexTones.highContrast
, can be used for more color accessible themes.FlexTones.ultraContrast
, for a very high contrast theme version.FlexTones.jolly
, for a more "jolly" and colorful theme.
You can define custom tones mapping and chroma limitation setups with FlexTones
. Using
the FlexTones.light
and FlexTones.dark
constructors as base for custom definitions are
preferred. By using them you only need to override defaults that you want to change.
// Example definition of light custom tones config.
const FlexTones myLightTones = FlexTones.light(
primaryTone: 30, // Default is 40.
onPrimaryTone: 95, // Default is 100
onSecondaryTone: 95, // Default is 100
onTertiaryTone: 95, // Default is 100
onErrorTone: 95, // Default is 100
primaryMinChroma: 55, // Default is 48
secondaryChroma: 25, // Default is 16
tertiaryChroma: 40, // Default is 24
neutralChroma: 7, // Default is 4,
neutralVariantChroma: 14, // Default is 8
);
// Example definition of dark custom tones config.
const FlexTones myDarkTones = FlexTones.dark(
primaryTone: 70, // Default is 80.
onPrimaryTone: 10, // Default is 20
onSecondaryTone: 10, // Default is 20
onTertiaryTone: 10, // Default is 20
onErrorTone: 10, // Default is 20
primaryMinChroma: 55, // Default is 48
secondaryChroma: 25, // Default is 16
tertiaryChroma: 40, // Default is 24
neutralChroma: 7, // Default is 4,
neutralVariantChroma: 14, // Default is 8
);
Accessibility #
You can use FlexTones
to create a seed generated ColorScheme
, that is based on same colors
as your standard theme's light and dark scheme colors, but uses a chroma configuration and tone
mapping setup that increases contrast further from standard light and dark theme setup.
There are two high contrast FlexTones
configuration pre-made for this. They are called
FlexTones.highContrast
, a colorful high contrast version, and FlexTones.ultraContrast
, a less
colorful version with more pure dark on light in light theme mode, and light on dark in dark mode.
// Make a high contrast light ColorScheme from the seeds.
final ColorScheme schemeLightHc = SeedColorScheme.fromSeeds(
brightness: Brightness.light,
primaryKey: primarySeedColor,
secondaryKey: secondarySeedColor,
tertiaryKey: tertiarySeedColor,
tones: FlexTones.highContrast(Brightness.light),
);
// Make a ultra contrast dark ColorScheme from the seeds.
final ColorScheme schemeDarkHc = SeedColorScheme.fromSeeds(
brightness: Brightness.dark,
primaryKey: primarySeedColor,
secondaryKey: secondarySeedColor,
tertiaryKey: tertiarySeedColor,
tones: FlexTones.ultraContrast(Brightness.dark),
);
If you then define equivalent ThemeData
based on those schemes as your standard MaterialApp
,
theme
and darkTheme
definitions, but assign them to highContrastTheme
and
highContrastDarkTheme
, you get more accessible themed colors that are based on same colors,
but with higher contrast, that are activated when users select high contrast theme in device
accessibility system settings.
// Define accessibility high contrast versions using same color base.
//
highContrastTheme: ThemeData.from(
colorScheme: schemeLightHc,
useMaterial3: true,
),
highContrastDarkTheme: ThemeData.from(
colorScheme: schemeDarkHc,
useMaterial3: true,
),
Example App #
The included example app in light and dark theme mode using above color seeding and custom tone mapping.
Below also comparing it to only single color ColorScheme.fromSeed
generated default
Material 3 seed algorithm available in Flutter. Both are using same key color as primary
seed color, but as ColorScheme.fromSeed
can only use a single seed color, we cannot customize the
hues of its seed generated secondary and tertiary colors. The secondary and tertiary colors are
also more muted, earthy and pastel color tones.
Light from seeds - Custom tones | Dark from seeds - Custom tones |
---|---|
![]() |
![]() |
Light from seed - Material 3 tones | Dark from seed - Material 3 tones |
---|---|
![]() |
![]() |
You can try a web version of this example here.