
# What a build contains

What a build of an application with `spring_boot_starter_flutter_cupertino` contains, and when something is not in it. A module that follows a key reads it when `build_runner` runs, from `application.yml` or `application.properties` without a profile (see [Modules left out of the build](../spring-core-dart-generator/optimizations/build-conditions.md)). The modules of the packages it depends on come with it: for `spring_boot_dart`, see [Auto-configuration](../spring-boot-dart/auto-configuration.md).

## Always in

No `build:` and no `platform:`: in every build of an application that depends on the starter.

| Module | What it holds |
|---|---|
| `springBootStarterFlutterCupertinoAutoConfiguration` | The Cupertino part of the themes (`CupertinoThemeDesign`), the themes as `CupertinoThemeData` (`cupertinoThemes`), the `CupertinoApp` of `spring.flutter.app.type: cupertino` (`cupertinoAppFactory`) and Cupertino's page route and hero flights for the navigation starter (`cupertinoPageRoutes`). |

## By key and by platform

Nothing is switched: no module of this starter follows a key or a platform, so all of it is in every build.

## What the generator writes for it

A part of the generator (see [Starter parts](../spring-core-dart-generator/how-it-works.md#starter-parts)) runs only when the application reaches its package.

| Part or builder | What it does |
|---|---|
| Through its dependencies | No part of its own. The parts and builders of [spring_boot_starter_flutter](../spring-boot-starter-flutter/optimizations.md) run, since the starter depends on it. |

## See also

- [Modules left out of the build](../spring-core-dart-generator/optimizations/build-conditions.md)
- [How the generation works: starter parts](../spring-core-dart-generator/how-it-works.md#starter-parts)
- [The builders](../spring-core-dart-generator/builders.md)
