Mobile component metrics
Figma status, repository implementation, and verified product use are shown separately · Snapshot 29 Oct 2026
All component findings
| Component | Figma status | Provisional priority | Shared design system | Android Driver | iOS Driver | Android Fleet | Product coverage | Owner / team | Pattern source | Details |
|---|
No entries match these filters.
Method and caveats
Design status: The 19 component entries, statuses, and provisional scores come from the supplied list. The Driver and Fleet screen sets are linked for context and were marked incomplete by the user; screen-level incompleteness is not assigned as a component-level status to newly discovered code rows.
Shared library: Counts come from the Motive Design System 1.0.0 inventories in each repository guide. We did not audit the package source. “Not listed” applies to release 1.0.0; a newer API may exist.
Implementation: Counts entries with a named local implementation or a shared API integrated in the app. It does not show product use.
Product use: Counts entries with source or guide evidence of a feature call site for a local, shared, or platform-native pattern. Each app count uses 19 entries; counts are not percentages and do not measure screen coverage. The combined header/bottom-sheet entry counts only when both patterns are verified. Otherwise, it is unknown.
Unknowns: “Not verified” means evidence is insufficient, not that a component is absent. The 15/57 total counts app-entry checks with unknown product use; 10/19 is the number of entries with at least one unknown.
Code-only rows: Each row represents an app-specific component definition or reusable UI pattern outside the supplied list. Rows are not merged across platforms, even when names or behaviors are similar. The audit prioritizes named reusable controls, list items, selection/search patterns, and common states; it does not count every screen or one-off layout. “Not in supplied Figma list” does not mean absent from Figma, incomplete, or unused.
Telemetry: Usage and outcome metrics must remain separate from Figma status, code existence, and code-based adoption. No Snowflake tables, time window, or app/platform coverage were verified in this session.
Telemetry: No Snowflake query or event schema was reviewed. Component-level use/outcomes are not assessed; events without explicit component or interaction identity must be labeled “not instrumented.” Telemetry remains separate from code existence, adoption, and Figma status.
Dates and checks: Android Driver and Fleet were searched at the linked local checkout commits; iOS Driver source was searched through GitHub at the linked commit because no local checkout was available. Migration-guide totals are date-bound and were not treated as fresh code census counts. No app build or tests were run.