# Power Apps Component Checklist

Use this before adding a reusable component to the team library.

## Component Basics

- [ ] Component name explains its purpose.
- [ ] Input properties are typed and named clearly.
- [ ] Output properties or events are documented.
- [ ] Default values work without hidden setup.
- [ ] Component has one main job.

## Power Fx

- [ ] Formulas avoid repeated expensive lookups.
- [ ] Delegation warnings are reviewed.
- [ ] Variables and collections have clear names.
- [ ] Patch or submit logic is easy to trace.

## UX

- [ ] Loading state is visible.
- [ ] Empty state is useful.
- [ ] Error state tells the user what to do.
- [ ] Keyboard and screen reader labels are considered.
- [ ] Component works on small and large screens.

## Handoff

- [ ] Example usage is included.
- [ ] Known limits are listed.
- [ ] Owner and checked date are documented.